post
https://{app-url}{}/api/v2/bc/data-streams
Create a single data stream
Request Arguments
The request is a complete data stream object.
See below a partial list of stream components.
Context: Where is the information taken from.
- All types: Data Source Id, Data stream name, type
- S3: Path in the bucket, file prefix and suffix, filename pattern
- RDB : Schema name, Table name
Schedule: Data stream timing properties
- Collection interval
- Timezone
- Delay
- History span to collect
- Backfill policy
Schema: The measures and dimensions collected by the stream
- Measures: name, aggregation type, unit
- Dimensions: name
| Field | Description & Values |
|---|---|
| pollingInterval | Supported data collection frequencies: m1, m5, m10, m15, m30, hourly, h2, h3, h4, h6, h8, h12, daily. [m= minutes, h= hours] |
| historicalDateRange | Supported historical collection ranges: h1, h4, d1, d3, w1, m1, m3, m6, y1. [h= last hour, d = last day, w = last week, m = last month, y = last year] |
Polling interval restrictions per type:
- Google Analytics:
- polling interval: hourly, daily
- polling Resolution: hours, days
- Allowed combinations hourly&hours OR daily&days
- BigQuery: hourly, daily
- Salesforce: hourly, daily
- Adobe Analytics: hourly, daily
- Kinesis: m1, m5, m10, m15, m30, hourly
- SQL typed: m1, m5, m15, hourly, h2, h3, h4, h6, h8, h12, daily
- S3, GCS: Also consider the fileDataPattern
Historical time span restrictions per type:
- Kinesis: no history
Polling interval and Historical span Allowed combinations:
| PollingInterval | HistoricalSpansAllowed |
|---|---|
| m1 | h1, h4, d1, d3, w1 |
| m5, m10, m15, m30 | h1, h4, d1, d3, w1, m1 |
| hourly, h2, h3, h4, h6, h8, h12 | d1, d3, w1, m1, m3, m6 ,y1 |
| daily | d1, d3, w1, m1, m3, m6, y1 ,y2, y5, y10, y15 ,y20 |