Use case
Some common uses for Table Input include:- Extracting source data for transformation. Table Input reads data directly from the specified table and acts as the starting point of your transformation pipeline.
- Joining data from multiple tables. Multiple Table Input components can feed into a Join component to combine the data into a single output. Note that in some scenarios it may be more efficient to do this with a Multi Table Input component rather than multiple Table Input components.
Properties
- Snowflake
- Databricks
- Amazon Redshift
- Google BigQuery
string
required
A human-readable name for the component.
drop-down
required
The Snowflake database. The special value
[Environment Default] uses the database defined in the environment. Read Databases, Tables and Views - Overview to learn more.drop-down
required
The Snowflake schema. The special value
[Environment Default] uses the schema defined in the environment. Read Database, Schema, and Share DDL to learn more.drop-down
required
The name of the input table or view. The tables and views found in the currently selected environment are provided to select from.
object selector
required
Select the columns to include in the input. If you wish to rename any columns, you can do this using the Rename component.
integer
Offsets the table contents by the number of specified seconds. This is a function of Snowflake’s Time Travel feature, allowing you to see a table as it was X seconds ago.
Troubleshooting: Table Input is missing column names field
TheTable Input is missing column names field error message appears if the Column Names property of your Table Input component hasn’t been configured correctly. As a result, the component can’t determine which columns to load. This error can occur if you haven’t selected any columns, if the pipeline is configured incorrectly, or if your table schema has changed since the component was configured. To resolve this issue:
- Check that you have selected the correct columns to load in the Column Names property of your Table Input component.
-
If the correct columns are selected, validate the pipeline to make sure that all components before the Table Input component are configured correctly.
We recommend checking the configuration of any pipelines that write to the table that the Table Input is loading from, to make sure that your data is loaded into the table correctly.
- Check the schema of the table you’re loading data from. If the table schema has changed, update the Table Input component to match.
