Batch deployment input details for AutoAI models

Follow these rules when you are specifying input details for batch deployments of AutoAI models.

Data type summary table:

Data	Description
Type	inline, data references
File formats	CSV, Parquet, xslx

Data Sources

Note:

Data sources used with AutoAI batch deployments can use masked credentials. For more information, refer to Connecting to data sources.

Input data references

watsonx.data

Input/output data references:

Local/managed assets from the space
Connected (remote) assets from these sources:
- Exasol
- Generic JDBC
- Snowflake
- Db2
- MySQL
- Microsoft SQL Server
- PostgreSQL
- Netezza Performance Server
- Amazon S3
- Oracle
- Google BigQuery
- Teradata
- SingleStore
- DataStax Enterprise connection
- Files in IBM Cloud Object Storage
- Files in IBM Cloud Object Storage (infrastructure)
- Files in a Storage Volume Connection
- Virtualized data tables created with Watson Query(input only)

Notes:

The connection option is available for all supported data source types. While creating a batch deployment you can select any connection in your space, and then search for the assets within that connection directly from the UI.
For connections of type Cloud Object Storage or Cloud Object Storage (infrastructure), you must configure Access key and Secret key, also known as HMAC credentials.
Your training data source can differ from your deployment data source, but the schema of the data must match or the deployment will fail. For example, you can train an experiment by using data from a Snowflake database and deploy by using input data from a Db2 database if the schema is an exact match.
The environment variables parameter of deployment jobs is not applicable.

If you are specifying input/output data references programmatically:

Data source reference type depends on the asset type. Refer to the Data source reference types section in Adding data assets to a deployment space.
For AutoAI assets, if the input or output data reference is of type connection_asset and the remote data source is a database then location.table_name and location.schema_name are required parameters. For example:

 "input_data_references": [{
                    "type": "connection_asset",
                    "connection": {
                            "id": <connection_guid>
                    },
                    "location": {
                            "table_name": <table name>,
                            "schema_name": <schema name>
                            <other wdp-properties supported by runtimes>
                    }
            }]

Parent topic: Batch deployment input details by framework