createEnvironment
Arguments
Returns
Show EnvironmentResponse
Show EnvironmentResponse
Show Environment
Show Environment
modifyEnvironment
Arguments
Returns
Show EnvironmentResponse
Show EnvironmentResponse
Show Environment
Show Environment
deleteEnvironment
createDataPoolAccessPolicy
Arguments
Show CreateDataPoolAccessPolicyInput
Show CreateDataPoolAccessPolicyInput
["*"]
, all columns will be available for querying.Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show DataPoolAccessPolicyResponse
Show DataPoolAccessPolicyResponse
Show DataPoolAccessPolicy
Show DataPoolAccessPolicy
modifyDataPoolAccessPolicy
Arguments
Show ModifyDataPoolAccessPolicyInput
Show ModifyDataPoolAccessPolicyInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show DataPoolAccessPolicyResponse
Show DataPoolAccessPolicyResponse
Show DataPoolAccessPolicy
Show DataPoolAccessPolicy
deleteDataPoolAccessPolicy
assignDataPoolAccessPolicyToApplication
accessControlEnabled
set to true, the Application
must have a Data Pool Access Policy assigned in order to query the Data Pool.An Application can have at most one Data Pool Access Policy assigned for a given Data Pool. If
an Application already has a Data Pool Access Policy for a given Data Pool, and you call this
mutation with another Data Pool Access Policy for the same Data Pool, the Application’s Data Pool Access
Policy will be replaced.Arguments
unAssignDataPoolAccessPolicyFromApplication
accessControlEnabled
property. If
accessControlEnabled
is true, the Application will no longer be able to query the
Data Pool. If accessControlEnabled
is false, the Application will be able to query
all data in the Data Pool, unrestricted.Arguments
createApplication
- APPLICATION_ADMIN
mutation {
createApplication(
input: {
uniqueName: "example_sample_application"
description: "My dashboard app"
scopes: [DATA_POOL_QUERY]
propeller: P1_X_SMALL
}
) {
... on ApplicationResponse {
application {
id
uniqueName
}
}
... on FailureResponse {
error {
code
message
}
}
}
}
Arguments
Show createApplicationInput
Show createApplicationInput
P1_X_SMALL
.Show Propeller
Show Propeller
P1_X_SMALL
: Max records per second: 5,000,000 records per secondP1_SMALL
: Max records per second: 25,000,000 records per secondP1_MEDIUM
: Max records per second: 100,000,000 records per secondP1_LARGE
: Max records per second: 250,000,000 records per secondP1_X_LARGE
: Max records per second: 500,000,000 records per second
Show ApplicationScope
Show ApplicationScope
ADMIN
: Grant read/write access to Data Sources, Data Pools, Metrics and Policies.APPLICATION_ADMIN
: Grant read/write access to Applications.DATA_POOL_QUERY
: Grant read access to query Data Pools.DATA_POOL_READ
: Grant read access to read Data Pools.DATA_POOL_STATS
: Grant read access to fetch column statistics from Data Pools.ENVIRONMENT_ADMIN
: Grant read/write access to Environments.METRIC_QUERY
: Grant read access to query Metrics.METRIC_STATS
: Grant read access to fetch Dimension statistics from Metrics.METRIC_READ
: Grant read access to Metrics.
METRIC_QUERY
.Returns
Show ApplicationOrFailureResponse
Show ApplicationOrFailureResponse
ApplicationResponse
will be returned; otherwise, a
FailureResponse
will be returned.Show ApplicationResponse
Show ApplicationResponse
modifyApplication
Arguments
Show modifyApplicationInput
Show modifyApplicationInput
Show Propeller
Show Propeller
P1_X_SMALL
: Max records per second: 5,000,000 records per secondP1_SMALL
: Max records per second: 25,000,000 records per secondP1_MEDIUM
: Max records per second: 100,000,000 records per secondP1_LARGE
: Max records per second: 250,000,000 records per secondP1_X_LARGE
: Max records per second: 500,000,000 records per second
Show ApplicationScope
Show ApplicationScope
ADMIN
: Grant read/write access to Data Sources, Data Pools, Metrics and Policies.APPLICATION_ADMIN
: Grant read/write access to Applications.DATA_POOL_QUERY
: Grant read access to query Data Pools.DATA_POOL_READ
: Grant read access to read Data Pools.DATA_POOL_STATS
: Grant read access to fetch column statistics from Data Pools.ENVIRONMENT_ADMIN
: Grant read/write access to Environments.METRIC_QUERY
: Grant read access to query Metrics.METRIC_STATS
: Grant read access to fetch Dimension statistics from Metrics.METRIC_READ
: Grant read access to Metrics.
METRIC_QUERY
.Returns
Show ApplicationOrFailureResponse
Show ApplicationOrFailureResponse
ApplicationResponse
will be returned; otherwise, a
FailureResponse
will be returned.Show ApplicationResponse
Show ApplicationResponse
deleteApplication
deleteApplicationByName
createSnowflakeDataSource
Arguments
Show createSnowflakeDataSourceInput
Show createSnowflakeDataSourceInput
Show SnowflakeConnectionSettingsInput
Show SnowflakeConnectionSettingsInput
Returns
Show DataSourceOrFailureResponse
Show DataSourceOrFailureResponse
DataSourceResponse
will be returned; otherwise, a
FailureResponse
will be returned.Show DataSourceResponse
Show DataSourceResponse
modifySnowflakeDataSource
Arguments
Show modifySnowflakeDataSourceInput
Show modifySnowflakeDataSourceInput
Show PartialSnowflakeConnectionSettingsInput
Show PartialSnowflakeConnectionSettingsInput
Returns
Show DataSourceOrFailureResponse
Show DataSourceOrFailureResponse
DataSourceResponse
will be returned; otherwise, a
FailureResponse
will be returned.Show DataSourceResponse
Show DataSourceResponse
reconnectDataSource
Arguments
Returns
Show DataSource
Show DataSource
Show Account
Show Account
Show Environment
Show Environment
Show DataSourceType
Show DataSourceType
WEBHOOK
: Indicates a Webhook Data Source.TWILIO_SEGMENT
: Indicates a Twilio Segment Data Source.S3
: Indicates an Amazon S3 Data Source.Redshift
: Indicates a Redshift Data Source.POSTGRESQL
: Indicates a PostgreSQL Data Source.KAFKA
: Indicates a Kafka Data Source.Http
: Indicates an Http Data Source.CLICKHOUSE
: Indicates a ClickHouse Data Source.AMAZON_DYNAMODB
: Indicates an Amazon DynamoDB Data Source.AMAZON_DATA_FIREHOSE
: Indicates an Amazon Data Firehose Data Source.Snowflake
: Indicates a Snowflake Data Source.INTERNAL
: Indicates an internal Data Source.
Show DataSourceStatus
Show DataSourceStatus
CREATED
: The Data Source has been created, but it is not connected yet.CONNECTING
: Propel is attempting to connect the Data Source.CONNECTED
: The Data Source is connected.BROKEN
: The Data Source failed to connect.DELETING
: Propel is deleting the Data Source.
Show ConnectionSettings
Show ConnectionSettings
Show DataSourceCheck
Show DataSourceCheck
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
introspectTables
Arguments
Returns
Show TableIntrospection
Show TableIntrospection
Show TableIntrospectionStatus
Show TableIntrospectionStatus
NOT_STARTED
: The table introspection has not started.STARTED
: The table introspection has started.SUCCEEDED
: The table introspection succeeded.FAILED
: The table introspection failed.
testDataSource
Arguments
Returns
Show DataSourceOrFailureResponse
Show DataSourceOrFailureResponse
DataSourceResponse
will be returned; otherwise, a
FailureResponse
will be returned.Show DataSourceResponse
Show DataSourceResponse
deleteDataSource
deleteDataSourceByName
createDataPoolV2
mutation {
createDataPoolV2(input: {
dataSource: "DSOXXXXX"
table: "tacosoft_sales_analytics"
timestamp: { columnName: "timestamp" }
columns: [
{
columnName: "timestamp",
type: TIMESTAMP,
isNullable: true
},
{
columnName: "order_id",
type: STRING,
isNullable: true
},
{
columnName: "taco_name",
type: STRING,
isNullable: true
},
{
columnName: "toppings",
type: JSON,
isNullable: true
},
{
columnName: "quantity",
type: INT32,
isNullable: true
},
{
columnName: "taco_unit_price",
type: INT32,
isNullable: true
},
{
columnName: "taco_total_price",
type: INT32,
isNullable: true
}
]
}) {
dataPool {
id
uniqueName
tableSettings {
orderBy
engine {
... on MergeTreeTableEngine {
type
}
... on ReplacingMergeTreeTableEngine {
type
ver
}
... on SummingMergeTreeTableEngine {
type
columns
}
... on AggregatingMergeTreeTableEngine {
type
}
... on PostgreSqlTableEngine {
type
}
}
}
}
}
}
Arguments
Show CreateDataPoolInputV2
Show CreateDataPoolInputV2
Show TimestampInput
Show TimestampInput
Show DataPoolColumnInput
Show DataPoolColumnInput
type
is set to CLICKHOUSE
.Show DataPoolSyncingInput
Show DataPoolSyncingInput
timestamp
and uniqueId
values, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.Show TableSettingsInput
Show TableSettingsInput
timestamp
and uniqueId
values, if specified.See TableEngineInputtimestamp
and uniqueId
values, if specified.timestamp
and uniqueId
values, if specified.timestamp
and uniqueId
values, if specified.Show Deprecated Fields
Show Deprecated Fields
Show TenantInput
Show TenantInput
Show UniqueIdInput
Show UniqueIdInput
Returns
Show DataPoolResponse
Show DataPoolResponse
Show DataPool
Show DataPool
Arguments
Show Deprecated Fields
Show Deprecated Fields
modifyDataPool
Arguments
Show modifyDataPoolInput
Show modifyDataPoolInput
Show DataPoolSyncingInput
Show DataPoolSyncingInput
Show TimestampInput
Show TimestampInput
Returns
Show DataPoolOrFailureResponse
Show DataPoolOrFailureResponse
DataPoolResponse
will be returned; otherwise, a
FailureResponse
will be returned.retryDataPoolSetup
Arguments
Returns
Show DataPool
Show DataPool
Show Account
Show Account
Show Environment
Show Environment
Show DataPoolStatus
Show DataPoolStatus
CREATED
: The Data Pool has been created and will be set up soon.PENDING
: Propel is attempting to set up the Data Pool.LIVE
: The Data Pool is set up and serving data. Check its Syncs to monitor data ingestion.SETUP_FAILED
: The Data Pool setup failed. Check its Setup Tasks before re-attempting setup.CONNECTING
CONNECTED
BROKEN
PAUSING
PAUSED
DELETING
: Propel is deleting the Data Pool and all of its associated data.
Show Timestamp
Show Timestamp
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Show DataPoolSetupTask
Show DataPoolSetupTask
Show DataPoolSyncing
Show DataPoolSyncing
EVERY_1_HOUR
does not mean that syncing will occur exactly on the hour. Instead, the syncing interval starts relative to
when the Data Pool goes LIVE
, and Propel will attempt to sync approximately every hour. Additionally,
if you pause or resume syncing, this too can shift the syncing interval around.See DataPoolSyncIntervalArguments
Show SyncsFilter
Show SyncsFilter
EMPTY
: Returns only Syncs with empty records.NOT_EMPTY
: Returns only Syncs that contain one or more records.ALL
: Returns all Syncs, regardless of whether they contain records or not.
Arguments
Show ValidateExpressionResult
Show ValidateExpressionResult
Show TableSettings
Show TableSettings
Show DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow Deprecated Fields
Show Deprecated Fields
Show UniqueId
Show UniqueId
retryDataPoolSetupByName
Arguments
Returns
Show DataPool
Show DataPool
Show Account
Show Account
Show Environment
Show Environment
Show DataPoolStatus
Show DataPoolStatus
CREATED
: The Data Pool has been created and will be set up soon.PENDING
: Propel is attempting to set up the Data Pool.LIVE
: The Data Pool is set up and serving data. Check its Syncs to monitor data ingestion.SETUP_FAILED
: The Data Pool setup failed. Check its Setup Tasks before re-attempting setup.CONNECTING
CONNECTED
BROKEN
PAUSING
PAUSED
DELETING
: Propel is deleting the Data Pool and all of its associated data.
Show Timestamp
Show Timestamp
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Show DataPoolSetupTask
Show DataPoolSetupTask
Show DataPoolSyncing
Show DataPoolSyncing
EVERY_1_HOUR
does not mean that syncing will occur exactly on the hour. Instead, the syncing interval starts relative to
when the Data Pool goes LIVE
, and Propel will attempt to sync approximately every hour. Additionally,
if you pause or resume syncing, this too can shift the syncing interval around.See DataPoolSyncIntervalArguments
Show SyncsFilter
Show SyncsFilter
EMPTY
: Returns only Syncs with empty records.NOT_EMPTY
: Returns only Syncs that contain one or more records.ALL
: Returns all Syncs, regardless of whether they contain records or not.
Arguments
Show ValidateExpressionResult
Show ValidateExpressionResult
Show TableSettings
Show TableSettings
Show DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow Deprecated Fields
Show Deprecated Fields
Show UniqueId
Show UniqueId
inspectDataPoolSchema
Arguments
Returns
Show DataPoolOrFailureResponse
Show DataPoolOrFailureResponse
DataPoolResponse
will be returned; otherwise, a
FailureResponse
will be returned.testDataPool
Arguments
Returns
Show DataPoolOrFailureResponse
Show DataPoolOrFailureResponse
DataPoolResponse
will be returned; otherwise, a
FailureResponse
will be returned.deleteDataPool
deleteDataPoolByName
disableSyncing
Arguments
Returns
Show DataPool
Show DataPool
Show Account
Show Account
Show Environment
Show Environment
Show DataPoolStatus
Show DataPoolStatus
CREATED
: The Data Pool has been created and will be set up soon.PENDING
: Propel is attempting to set up the Data Pool.LIVE
: The Data Pool is set up and serving data. Check its Syncs to monitor data ingestion.SETUP_FAILED
: The Data Pool setup failed. Check its Setup Tasks before re-attempting setup.CONNECTING
CONNECTED
BROKEN
PAUSING
PAUSED
DELETING
: Propel is deleting the Data Pool and all of its associated data.
Show Timestamp
Show Timestamp
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Show DataPoolSetupTask
Show DataPoolSetupTask
Show DataPoolSyncing
Show DataPoolSyncing
EVERY_1_HOUR
does not mean that syncing will occur exactly on the hour. Instead, the syncing interval starts relative to
when the Data Pool goes LIVE
, and Propel will attempt to sync approximately every hour. Additionally,
if you pause or resume syncing, this too can shift the syncing interval around.See DataPoolSyncIntervalArguments
Show SyncsFilter
Show SyncsFilter
EMPTY
: Returns only Syncs with empty records.NOT_EMPTY
: Returns only Syncs that contain one or more records.ALL
: Returns all Syncs, regardless of whether they contain records or not.
Arguments
Show ValidateExpressionResult
Show ValidateExpressionResult
Show TableSettings
Show TableSettings
Show DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow Deprecated Fields
Show Deprecated Fields
Show UniqueId
Show UniqueId
enableSyncing
Arguments
Returns
Show DataPool
Show DataPool
Show Account
Show Account
Show Environment
Show Environment
Show DataPoolStatus
Show DataPoolStatus
CREATED
: The Data Pool has been created and will be set up soon.PENDING
: Propel is attempting to set up the Data Pool.LIVE
: The Data Pool is set up and serving data. Check its Syncs to monitor data ingestion.SETUP_FAILED
: The Data Pool setup failed. Check its Setup Tasks before re-attempting setup.CONNECTING
CONNECTED
BROKEN
PAUSING
PAUSED
DELETING
: Propel is deleting the Data Pool and all of its associated data.
Show Timestamp
Show Timestamp
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Show DataPoolSetupTask
Show DataPoolSetupTask
Show DataPoolSyncing
Show DataPoolSyncing
EVERY_1_HOUR
does not mean that syncing will occur exactly on the hour. Instead, the syncing interval starts relative to
when the Data Pool goes LIVE
, and Propel will attempt to sync approximately every hour. Additionally,
if you pause or resume syncing, this too can shift the syncing interval around.See DataPoolSyncIntervalArguments
Show SyncsFilter
Show SyncsFilter
EMPTY
: Returns only Syncs with empty records.NOT_EMPTY
: Returns only Syncs that contain one or more records.ALL
: Returns all Syncs, regardless of whether they contain records or not.
Arguments
Show ValidateExpressionResult
Show ValidateExpressionResult
Show TableSettings
Show TableSettings
Show DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow Deprecated Fields
Show Deprecated Fields
Show UniqueId
Show UniqueId
createCountMetric
Arguments
Show CreateCountMetricInput
Show CreateCountMetricInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createCountDistinctMetric
Arguments
Show CreateCountDistinctMetricInput
Show CreateCountDistinctMetricInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createSumMetric
Arguments
Show CreateSumMetricInput
Show CreateSumMetricInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createAverageMetric
Arguments
Show CreateAverageMetricInput
Show CreateAverageMetricInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createMinMetric
Arguments
Show CreateMinMetricInput
Show CreateMinMetricInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createMaxMetric
Arguments
Show CreateMaxMetricInput
Show CreateMaxMetricInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
createCustomMetric
Arguments
Show CreateCustomMetricInput
Show CreateCustomMetricInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
modifyMetric
Arguments
Show ModifyMetricInput
Show ModifyMetricInput
Show DimensionInput
Show DimensionInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show MetricResponse
Show MetricResponse
Show Metric
Show Metric
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.See Dimensioncounter
query insteadArguments
timeSeries
query insteadArguments
leaderboard
query insteadArguments
migrateMetric
Arguments
Returns
Show Metric
Show Metric
Show Account
Show Account
Show Environment
Show Environment
Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show MetricType
Show MetricType
COUNT
: Counts the number of records that matches the Metric Filters. For time series, it will count the values for each time granularity.SUM
: Sums the values of the specified column for every record that matches the Metric Filters. For time series, it will sum the values for each time granularity.COUNT_DISTINCT
: Counts the number of distinct values in the specified column for every record that matches the Metric Filters. For time series, it will count the distinct values for each time granularity.AVERAGE
: Averages the values of the specified column for every record that matches the Metric Filters. For time series, it will average the values for each time granularity.MIN
: Selects the minimum value of the specified column for every record that matches the Metric Filters. For time series, it will select the minimum value for each time granularity.MAX
: Selects the maximum value of the specified column for every record that matches the Metric Filters. For time series, it will select the maximum value for each time granularity.CUSTOM
: Aggregates values based on the provided custom expression.
Show MetricSettings
Show MetricSettings
Show Deprecated Fields
Show Deprecated Fields
settings
object instead.deprecated: Use the Metric settings
object instead.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
counter
query insteadArguments
Show CounterInput
Show CounterInput
Show Deprecated Fields
Show Deprecated Fields
metricName
is not specified.deprecated: Use metric
metricId
is not specified.deprecated: Use metric
filterSql
insteadSee FilterInputtimeSeries
query insteadArguments
Show TimeSeriesInput
Show TimeSeriesInput
Show Deprecated Fields
Show Deprecated Fields
metricName
is not specified.deprecated: Use metric
metricId
is not specified.deprecated: Use metric
filterSql
insteadSee FilterInputShow TimeSeriesResponse
Show TimeSeriesResponse
groupBy
, if specified.See TimeSeriesResponseGroupleaderboard
query insteadArguments
Show LeaderboardInput
Show LeaderboardInput
ASC
) or descending (DESC
) order. Defaults to descending (DESC
) order when not provided.See SortShow Deprecated Fields
Show Deprecated Fields
metricName
is not specified.deprecated: Use metric
metricId
is not specified.deprecated: Use metric
filterSql
insteadSee FilterInputShow LeaderboardResponse
Show LeaderboardResponse
deleteMetric
deleteMetricByName
createBooster
Arguments
Show CreateBoosterInput
Show CreateBoosterInput
- The Data Pool’s Tenant ID column (if present)
- Metric Filter columns (if present)
- Query Filter Dimensions (see
dimensions
) - The Data Pool’s timestamp column
- Specify Dimensions in descending order of importance for filtering and in ascending order of cardinality.
- Take into consideration hierarchical relationships as well (for example, a “country” Dimension should appear before a “state” Dimension).
Show DimensionInput
Show DimensionInput
Returns
Show BoosterResponse
Show BoosterResponse
Show Booster
Show Booster
- The Data Pool’s Tenant ID column (if present)
- Metric Filter columns (if present)
- Query Filter Dimensions (see
dimensions
) - The Data Pool’s timestamp column
deleteBooster
createDeletionJob
Arguments
Show CreateDeletionJobInput
Show CreateDeletionJobInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show DeletionJobResponse
Show DeletionJobResponse
Show DeletionJob
Show DeletionJob
createAddColumnToDataPoolJob
Arguments
Show CreateAddColumnToDataPoolJobInput
Show CreateAddColumnToDataPoolJobInput
Show ColumnType
Show ColumnType
BOOLEAN
: True or false.STRING
: A variable-length string.FLOAT
: A 32-bit signed double-precision floating point number.DOUBLE
: A 64-bit signed double-precision floating point number.INT8
: An 8-bit signed integer, with a minimum value of -2⁷ and a maximum value of 2⁷-1.INT16
: A 16-bit signed integer, with a minimum value of -2¹⁵ and a maximum value of 2¹⁵-1.INT32
: A 32-bit signed integer, with a minimum value of -2³¹ and a maximum value of 2³¹-1.INT64
: A 64-bit signed integer, with a minimum value of -2⁶³ and a maximum value of 2⁶³-1.DATE
: A date without a timestamp. For example, “YYYY-MM-DD”.TIMESTAMP
: A date with a timestamp. For example, “yyy-MM-dd HH:mm:ss”.JSON
: A JavaScript Object Notation (JSON) document.CLICKHOUSE
: A ClickHouse-specific type.
columnType
is set to CLICKHOUSE
.Returns
Show AddColumnToDataPoolJobResponse
Show AddColumnToDataPoolJobResponse
Show AddColumnToDataPoolJob
Show AddColumnToDataPoolJob
columnType
is set to CLICKHOUSE
.createUpdateDataPoolRecordsJob
Arguments
Show CreateUpdateDataPoolRecordsJobInput
Show CreateUpdateDataPoolRecordsJobInput
Show UpdateDataPoolRecordsJobSetColumnInput
Show UpdateDataPoolRecordsJobSetColumnInput
{
"column": "status",
"expression": "'completed'"
}
{
"column": "counter",
"expression": "counter + 1"
}
{
"column": "full_name",
"expression": "concat(first_name, ' ', last_name)"
}
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show UpdateDataPoolRecordsJobResponse
Show UpdateDataPoolRecordsJobResponse
Show UpdateDataPoolRecordsJob
Show UpdateDataPoolRecordsJob
syncDataPool
Arguments
Returns
Show Sync
Show Sync
Show Account
Show Account
Show Environment
Show Environment
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
Show SyncStatus
Show SyncStatus
SYNCING
: Propel is actively syncing records contained within the Sync.SUCCEEDED
: The Sync succeeded. Propel successfully synced all records contained within the Sync.FAILED
: The Sync failed. Propel failed to sync some or all records contained within the Sync.DELETING
: Propel is deleting the Sync.
Show Deprecated Fields
Show Deprecated Fields
processedRecords
insteadprocessedRecords
insteadprocessedRecords
insteadprocessedRecords
insteadresyncDataPool
Arguments
Returns
Show Sync
Show Sync
Show Account
Show Account
Show Environment
Show Environment
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
Show SyncStatus
Show SyncStatus
SYNCING
: Propel is actively syncing records contained within the Sync.SUCCEEDED
: The Sync succeeded. Propel successfully synced all records contained within the Sync.FAILED
: The Sync failed. Propel failed to sync some or all records contained within the Sync.DELETING
: Propel is deleting the Sync.
Show Deprecated Fields
Show Deprecated Fields
processedRecords
insteadprocessedRecords
insteadprocessedRecords
insteadprocessedRecords
insteadcreateMaterializedView
Arguments
Show CreateMaterializedViewInput
Show CreateMaterializedViewInput
Show CreateMaterializedViewDestinationInput
Show CreateMaterializedViewDestinationInput
Show BackfillOptionsInput
Show BackfillOptionsInput
OLDEST_FIRST
if not specified.See PartitionOrderReturns
Show MaterializedViewResponse
Show MaterializedViewResponse
Show MaterializedView
Show MaterializedView
modifyMaterializedView
Arguments
Returns
Show MaterializedViewResponse
Show MaterializedViewResponse
Show MaterializedView
Show MaterializedView
deleteMaterializedView
createAmazonDataFirehoseDataSource
Arguments
Show CreateAmazonDataFirehoseDataSourceInput
Show CreateAmazonDataFirehoseDataSourceInput
Show AmazonDataFirehoseConnectionSettingsInput
Show AmazonDataFirehoseConnectionSettingsInput
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose issues requests to its custom HTTP endpoint.See HttpBasicAuthInputtimestamp
value, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.See TableSettingsInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyAmazonDataFirehoseDataSource
Arguments
Show ModifyAmazonDataFirehoseDataSourceInput
Show ModifyAmazonDataFirehoseDataSourceInput
Show PartialAmazonDataFirehoseConnectionSettingsInput
Show PartialAmazonDataFirehoseConnectionSettingsInput
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose issues requests to its custom HTTP endpoint. If not provided this property will not be modified.See HttpBasicAuthInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createAmazonDynamoDBDataSource
Arguments
Show CreateAmazonDynamoDBDataSourceInput
Show CreateAmazonDynamoDBDataSourceInput
Show AmazonDynamoDBConnectionSettingsInput
Show AmazonDynamoDBConnectionSettingsInput
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose transmits records from your DynamoDB table to its
custom HTTP endpoint.See HttpBasicAuthInputtimestamp
value, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.See TableSettingsInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyAmazonDynamoDBDataSource
Arguments
Show ModifyAmazonDynamoDBDataSourceInput
Show ModifyAmazonDynamoDBDataSourceInput
Show PartialAmazonDynamoDBConnectionSettingsInput
Show PartialAmazonDynamoDBConnectionSettingsInput
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose transmits records from your DynamoDB table to its
custom HTTP endpoint. If not provided this property will not be modified.See HttpBasicAuthInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createClickHouseDataSource
Arguments
Show CreateClickHouseDataSourceInput
Show CreateClickHouseDataSourceInput
Show ClickHouseConnectionSettingsInput
Show ClickHouseConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyClickHouseDataSource
Arguments
Show ModifyClickHouseDataSourceInput
Show ModifyClickHouseDataSourceInput
Show PartialClickHouseConnectionSettingsInput
Show PartialClickHouseConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createHttpDataSource
Arguments
Show CreateHttpDataSourceInput
Show CreateHttpDataSourceInput
Show HttpConnectionSettingsInput
Show HttpConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyHttpDataSource
Arguments
Show ModifyHttpDataSourceInput
Show ModifyHttpDataSourceInput
Show PartialHttpConnectionSettingsInput
Show PartialHttpConnectionSettingsInput
false
to disable HTTP Basic authentication. Any previously stored HTTP Basic authentication settings will be cleared out. If not provided this property will not be modified.Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createKafkaDataSource
Arguments
Show CreateKafkaDataSourceInput
Show CreateKafkaDataSourceInput
Show KafkaConnectionSettingsInput
Show KafkaConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyKafkaDataSource
Arguments
Show ModifyKafkaDataSourceInput
Show ModifyKafkaDataSourceInput
Show PartialKafkaConnectionSettingsInput
Show PartialKafkaConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createPostgreSqlDataSource
mutation {
createPostgreSqlDataSource(input: {
uniqueName: "example_postgresql_data_source"
description: "My PostgreSQL Data Source"
connectionSettings: {
database: "example_database"
schema: "public"
host: "postgresql.example.com"
port: 5432
user: "user"
password: "password"
}
}) {
dataSource {
id
uniqueName
}
}
}
Arguments
Show CreatePostgreSqlDataSourceInput
Show CreatePostgreSqlDataSourceInput
Show PostgreSqlConnectionSettingsInput
Show PostgreSqlConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyPostgreSqlDataSource
Arguments
Show ModifyPostgreSqlDataSourceInput
Show ModifyPostgreSqlDataSourceInput
Show PartialPostgreSqlConnectionSettingsInput
Show PartialPostgreSqlConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createS3DataSource
Arguments
Show CreateS3DataSourceInput
Show CreateS3DataSourceInput
Show S3ConnectionSettingsInput
Show S3ConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyS3DataSource
Arguments
Show ModifyS3DataSourceInput
Show ModifyS3DataSourceInput
Show PartialS3ConnectionSettingsInput
Show PartialS3ConnectionSettingsInput
Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createTwilioSegmentDataSource
Arguments
Show CreateTwilioSegmentDataSourceInput
Show CreateTwilioSegmentDataSourceInput
Show TwilioSegmentConnectionSettingsInput
Show TwilioSegmentConnectionSettingsInput
timestamp
and uniqueId
values, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.See TableSettingsInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyTwilioSegmentDataSource
Arguments
Show ModifyTwilioSegmentDataSourceInput
Show ModifyTwilioSegmentDataSourceInput
Show PartialTwilioSegmentConnectionSettingsInput
Show PartialTwilioSegmentConnectionSettingsInput
false
to disable HTTP Basic authentication. Any previously stored HTTP Basic authentication settings will be cleared out. If not provided this property will not be modified.Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
createWebhookDataSource
Arguments
Show CreateWebhookDataSourceInput
Show CreateWebhookDataSourceInput
Show WebhookConnectionSettingsInput
Show WebhookConnectionSettingsInput
timestamp
and uniqueId
values, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.See TableSettingsInputReturns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
modifyWebhookDataSource
Arguments
Show ModifyWebhookDataSourceInput
Show ModifyWebhookDataSourceInput
Show PartialWebhookConnectionSettingsInput
Show PartialWebhookConnectionSettingsInput
false
to disable HTTP Basic authentication. Any previously stored HTTP Basic authentication settings will be cleared out. If not provided this property will not be modified.Returns
Show DataSourceResponse
Show DataSourceResponse
Show DataSource
Show DataSource
dataPools
field on a Data Source, you will get Data Pools for the Data Source.The dataPools
field uses cursor-based pagination typical of GraphQL APIs. You can use the pairs of parameters first
and after
or last
and before
to page forward or backward through the results, respectively.For forward pagination, the first
parameter defines the number of results to return, and the after
parameter defines the cursor to continue from. You should pass the cursor for the last result of the current page to after
.For backward pagination, the last
parameter defines the number of results to return, and the before
parameter defines the cursor to continue from. You should pass the cursor for the first result of the current page to before
.Arguments
Show Deprecated Fields
Show Deprecated Fields
reconnectDataPool
retryDataPoolSetup
instead.deprecated: Use retryDataPoolSetup
insteadArguments
Returns
Show DataPool
Show DataPool
Show Account
Show Account
Show Environment
Show Environment
Show DataPoolStatus
Show DataPoolStatus
CREATED
: The Data Pool has been created and will be set up soon.PENDING
: Propel is attempting to set up the Data Pool.LIVE
: The Data Pool is set up and serving data. Check its Syncs to monitor data ingestion.SETUP_FAILED
: The Data Pool setup failed. Check its Setup Tasks before re-attempting setup.CONNECTING
CONNECTED
BROKEN
PAUSING
PAUSED
DELETING
: Propel is deleting the Data Pool and all of its associated data.
Show Timestamp
Show Timestamp
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Arguments
Show DataPoolColumnConnection
Show DataPoolColumnConnection
Show DataPoolSetupTask
Show DataPoolSetupTask
Show DataPoolSyncing
Show DataPoolSyncing
EVERY_1_HOUR
does not mean that syncing will occur exactly on the hour. Instead, the syncing interval starts relative to
when the Data Pool goes LIVE
, and Propel will attempt to sync approximately every hour. Additionally,
if you pause or resume syncing, this too can shift the syncing interval around.See DataPoolSyncIntervalArguments
Show SyncsFilter
Show SyncsFilter
EMPTY
: Returns only Syncs with empty records.NOT_EMPTY
: Returns only Syncs that contain one or more records.ALL
: Returns all Syncs, regardless of whether they contain records or not.
Arguments
Show ValidateExpressionResult
Show ValidateExpressionResult
Show TableSettings
Show TableSettings
Show DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow DataPoolColumn
Show DataPoolColumn
Show Deprecated Fields
Show Deprecated Fields
columnName
insteadShow Deprecated Fields
Show Deprecated Fields
Show UniqueId
Show UniqueId
createPolicy
Arguments
Show CreatePolicyInput
Show CreatePolicyInput
Show PolicyType
Show PolicyType
ALL_ACCESS
: Grants access to all Metric data.TENANT_ACCESS
: Grants access to a specified tenant’s Metric data.
Returns
Show PolicyResponse
Show PolicyResponse
Show Policy
Show Policy
modifyPolicy
Arguments
Show ModifyPolicyInput
Show ModifyPolicyInput
Returns
Show PolicyResponse
Show PolicyResponse
Show Policy
Show Policy
deletePolicy
requestDelete
createDeletionJob
Arguments
Show DeletionRequestInput
Show DeletionRequestInput
Show Deprecated Fields
Show Deprecated Fields
filterSql
insteadShow FilterInput
Show FilterInput
and
and or
. For example, to construct a filter equivalent to(value > 0 AND value <= 100) OR status = "confirmed"
{
"column": "value",
"operator": "GREATER_THAN",
"value": "0",
"and": [{
"column": "value",
"operator": "LESS_THAN_OR_EQUAL_TO",
"value": "0"
}],
"or": [{
"column": "status",
"operator": "EQUALS",
"value": "confirmed"
}]
}
and
takes precedence over or
.Returns
Show RequestDeleteResponse
Show RequestDeleteResponse
Show DeletionJob
Show DeletionJob