Information schema
InfluxDB 3 Enterprise is in public beta and available for testing and feedback,
but is not meant for production use yet.
Both the product and this documentation are works in progress.
We welcome and encourage your input about your experience with the beta and
invite you to join our public channels for updates and to
share feedback.
Beta expectations and recommendations
- No more breaking changes
While in beta, we will no longer make breaking changes to the
InfluxDB 3 Enterprise API. Any updates to file formats or organization
will have in-place upgrade paths for beta builds. Use the Beta
for testing and validation purposes, knowing that when you upgrade,
your data will come with it, and your APIs will all work the same. - Weekly releases
While in beta, we’ll be making weekly InfluxDB 3 Enterprise releases
and providing release notes to make it easy to track updates. - Processing engine is still in alpha
The embedded Python VM that is the processing engine should still
be considered alpha software. It is fully functional and allows
users to create and share plugins that trigger off of writes, a
schedule, or requests to an HTTP endpoint. However, we want to
continue iterating on user feedback and making changes where they
make sense. While we don't anticipate any breaking changes,
we're not yet committed to the current API as the long term
support target. Feedback we get during this phase will be important
to fine-tune the API for our users' needs. - Object store file organization and format
InfluxDB 3 Enterprise supports a "diskless" architecture, keeping all
state in object storage. The specific file organization and format
are not part of a stable API. Only the HTTP and Apache
Arrow Flight APIs are considered stable.
The underlying query engine for the InfluxDB SQL implementation,
DataFusion, provides commands
that return metadata related to your data schema.
To access this information, use the SHOW TABLES, SHOW COLUMNS, and
SHOW ALL commands or query views in the ISO SQL
information_schema schema.
In the context of InfluxDB, a measurement
is represented as a table. Time, tags,
and fields are each represented
by columns in a table.
Returns information about tables (measurements) in an InfluxDB bucket.
You can also query the information_schema.tables view:
SELECT * FROM information_schema.tables
Measurements are those that use the iox table schema.
| table_catalog | table_schema | table_name | table_type |
|---|
| public | iox | home | BASE TABLE |
| public | system | queries | BASE TABLE |
| public | information_schema | tables | VIEW |
| public | information_schema | views | VIEW |
| public | information_schema | columns | VIEW |
| public | information_schema | df_settings | VIEW |
Returns information about the schema of a table (measurement) in an InfluxDB bucket.
SHOW COLUMNS FROM example_table
You can also query the information_schema.columns view:
SELECT
table_catalog,
table_schema,
table_name,
column_name,
data_type,
is_nullable
FROM information_schema.columns
WHERE table_name = 'example_table'
| table_catalog | table_schema | table_name | column_name | data_type | is_nullable |
|---|
| public | iox | home | co | Int64 | YES |
| public | iox | home | hum | Float64 | YES |
| public | iox | home | room | Dictionary(Int32, Utf8) | YES |
| public | iox | home | temp | Float64 | YES |
| public | iox | home | time | Timestamp(Nanosecond, None) | NO |
Returns the configuration options of the current session.
You can also query the information_schema.df_settings view:
SELECT * FROM information_schema.df_settings
View SHOW ALL example output
| name | setting |
|---|
| datafusion.catalog.create_default_catalog_and_schema | true |
| datafusion.catalog.default_catalog | public |
| datafusion.catalog.default_schema | iox |
| datafusion.catalog.format | |
| datafusion.catalog.has_header | false |
| datafusion.catalog.information_schema | true |
| datafusion.catalog.location | |
| datafusion.execution.batch_size | 8192 |
| datafusion.execution.coalesce_batches | true |
| datafusion.execution.collect_statistics | false |
| datafusion.execution.parquet.enable_page_index | false |
| datafusion.execution.parquet.metadata_size_hint | |
| datafusion.execution.parquet.pruning | true |
| datafusion.execution.parquet.pushdown_filters | true |
| datafusion.execution.parquet.reorder_filters | true |
| datafusion.execution.parquet.skip_metadata | true |
| datafusion.execution.target_partitions | 4 |
| datafusion.execution.time_zone | +00:00 |
| datafusion.explain.logical_plan_only | false |
| datafusion.explain.physical_plan_only | false |
| datafusion.optimizer.enable_round_robin_repartition | true |
| datafusion.optimizer.filter_null_join_keys | false |
| datafusion.optimizer.hash_join_single_partition_threshold | 1048576 |
| datafusion.optimizer.max_passes | 3 |
| datafusion.optimizer.prefer_hash_join | true |
| datafusion.optimizer.repartition_aggregations | true |
| datafusion.optimizer.repartition_file_min_size | 10485760 |
| datafusion.optimizer.repartition_file_scans | true |
| datafusion.optimizer.repartition_joins | true |
| datafusion.optimizer.repartition_sorts | false |
| datafusion.optimizer.repartition_windows | true |
| datafusion.optimizer.skip_failed_rules | true |
| datafusion.optimizer.top_down_join_key_reordering | true |
| datafusion.sql_parser.enable_ident_normalization | true |
| datafusion.sql_parser.parse_float_as_decimal | false |
Was this page helpful?
Thank you for your feedback!
Thank you for being part of our community!
We welcome and encourage your feedback and bug reports for InfluxDB 3 Enterprise and this documentation.
To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.
