BETWEEN
operator like the following:
BETWEEN $START AND $END
must exist somewhere in the query.
Joins in the templatized SQL are not supported at the moment.yyyy-MM-dd
).Property Name | Required | Description |
---|---|---|
sql.snowflake.user | Yes | Snowflake username |
sql.snowflake.password | Yes | Snowflake password |
sql.snowflake.account | Yes | Snowflake account name |
sql.snowflake.db | Yes | Snowflake database |
sql.snowflake.schema | Yes | Snowflake schema (collection of tables/views) |
Property Name | Required | Description |
---|---|---|
sql.bigquery.projectid | Yes | BigQuery project ID |
Property Name | Required | Description |
---|---|---|
sql.queryTemplate | Yes | Templatized query to pull data from Snowflake and pull into Pinot |
sql.timeColumnFormat | Yes | The format of the time column in their templatized query. This is needed to understand how to break the query into batches. |
sql.timeColumnName | Yes | The time column name provided in the templatized query. |
sql.startTime | Yes | Marks the beginning time of the Snowflake table for which to ingest. This is used to identify time buckets. Should be in the format of their Snowflake table time column. |
sql.endTime | No | Provide if a one time bootstrap job is desired. Continuous ingestion up to the current time will be disabled if provided. |
sql.bucketTimePeriod | No | If you want to override the segment time periods in case you are noticing that the segments created are too small or too large. This parameter will determine the time buckets for the Pinot segments in relation to the sql.startTime value. All segments will be bucketed by this length. E.g. A 5 day bucket period would be expressed as “5d”. A 1 hour bucket period would be expressed as “1h”. Valid period units are d (days), (h) hours, (m) minutes, and (s) seconds. |
sql.delayTimeLength | No | This will be a time value that will determine the latest time value for which data is ingested from Snowflake. $END = CURRENT_TIME - DELAY. If omitted, defaults to 1. E.g. A 5 day delay from the current time of execution would be expressed as “5d”. A 1 hour delay would be expressed as “1h”. Valid time delay length units are d (days), (h) hours, (m) minutes, and (s) seconds. |
schedule | No | CRON expression for when the job will be routinely triggered. Scheduling support is natively built into Minion jobs (see PinotTaskManager). If not provided, the ingestion task can be manually triggered via the Pinot task API |