ApplicationOrFailureResponse
The result of a mutation which creates or modifies an Application. If successful, anApplicationResponse
will be returned; otherwise, a
FailureResponse
will be returned.
Show ApplicationResponse
Show ApplicationResponse
Show Application
Show Application
ConnectionSettings
Show SnowflakeConnectionSettings
Show SnowflakeConnectionSettings
Show InternalConnectionSettings
Show InternalConnectionSettings
Show AmazonDataFirehoseConnectionSettings
Show AmazonDataFirehoseConnectionSettings
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose issues requests to its custom HTTP endpoint.Show HttpBasicAuthSettings
Show HttpBasicAuthSettings
Show AmazonDataFirehoseDataSourceColumn
Show AmazonDataFirehoseDataSourceColumn
{ "greeting": { "message": "hello, world" } }
timestamp
value, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.Show TableSettings
Show TableSettings
X-Amz-Firehose-Access-Key
header when configuring your Amazon Data Firehose to deliver to a custom HTTP endpoint.Show AmazonDynamoDBConnectionSettings
Show AmazonDynamoDBConnectionSettings
X-Amz-Firehose-Access-Key
header when Amazon Data Firehose transmits records from your DynamoDB table to its
custom HTTP endpoint.Show HttpBasicAuthSettings
Show HttpBasicAuthSettings
Show AmazonDynamoDBDataSourceColumn
Show AmazonDynamoDBDataSourceColumn
{ "greeting": { "message": "hello, world" } }
timestamp
value, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.Show TableSettings
Show TableSettings
X-Amz-Firehose-Access-Key
header when configuring your Amazon Data Firehose to
transmit records from your DynamoDB table to its custom HTTP endpoint.Show ClickHouseConnectionSettings
Show ClickHouseConnectionSettings
Show HttpConnectionSettings
Show HttpConnectionSettings
Show HttpBasicAuthSettings
Show HttpBasicAuthSettings
Show HttpDataSourceTable
Show HttpDataSourceTable
Show KafkaConnectionSettings
Show KafkaConnectionSettings
Show PostgreSqlConnectionSettings
Show PostgreSqlConnectionSettings
Show S3ConnectionSettings
Show S3ConnectionSettings
Show S3DataSourceTable
Show S3DataSourceTable
Show TwilioSegmentConnectionSettings
Show TwilioSegmentConnectionSettings
Show HttpBasicAuthSettings
Show HttpBasicAuthSettings
Show TwilioSegmentDataSourceColumn
Show TwilioSegmentDataSourceColumn
{ "greeting": { "message": "hello, world" } }
timestamp
and uniqueId
values, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.Show TableSettings
Show TableSettings
Show WebhookConnectionSettings
Show WebhookConnectionSettings
Show HttpBasicAuthSettings
Show HttpBasicAuthSettings
Show WebhookDataSourceColumn
Show WebhookDataSourceColumn
{ "greeting": { "message": "hello, world" } }
timestamp
and uniqueId
values, if any. You can override these
defaults in order to specify a custom table engine, custom ORDER BY, etc.Show TableSettings
Show TableSettings
Show Deprecated Fields
Show Deprecated Fields
DataSourceOrFailureResponse
The result of a mutation which creates or modifies a DataSource. If successful, anDataSourceResponse
will be returned; otherwise, a
FailureResponse
will be returned.
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
TableEngine
A Data Pool’s table engine.Show MergeTreeTableEngine
Show MergeTreeTableEngine
MERGE_TREE
.Show TableEngineType
Show TableEngineType
MERGE_TREE
: The MergeTree table engine.REPLACING_MERGE_TREE
: The ReplacingMergeTree table engine.SUMMING_MERGE_TREE
: The SummingMergeTree table engine.AGGREGATING_MERGE_TREE
: The AggregatingMergeTree table engine.POSTGRESQL
: The PostgreSQL table engine.
Show ReplacingMergeTreeTableEngine
Show ReplacingMergeTreeTableEngine
REPLACING_MERGE_TREE
.Show TableEngineType
Show TableEngineType
MERGE_TREE
: The MergeTree table engine.REPLACING_MERGE_TREE
: The ReplacingMergeTree table engine.SUMMING_MERGE_TREE
: The SummingMergeTree table engine.AGGREGATING_MERGE_TREE
: The AggregatingMergeTree table engine.POSTGRESQL
: The PostgreSQL table engine.
ver
parameter to the ReplacingMergeTree engine.Show SummingMergeTreeTableEngine
Show SummingMergeTreeTableEngine
SUMMING_MERGE_TREE
.Show TableEngineType
Show TableEngineType
MERGE_TREE
: The MergeTree table engine.REPLACING_MERGE_TREE
: The ReplacingMergeTree table engine.SUMMING_MERGE_TREE
: The SummingMergeTree table engine.AGGREGATING_MERGE_TREE
: The AggregatingMergeTree table engine.POSTGRESQL
: The PostgreSQL table engine.
Show AggregatingMergeTreeTableEngine
Show AggregatingMergeTreeTableEngine
AGGREGATING_MERGE_TREE
.Show TableEngineType
Show TableEngineType
MERGE_TREE
: The MergeTree table engine.REPLACING_MERGE_TREE
: The ReplacingMergeTree table engine.SUMMING_MERGE_TREE
: The SummingMergeTree table engine.AGGREGATING_MERGE_TREE
: The AggregatingMergeTree table engine.POSTGRESQL
: The PostgreSQL table engine.
Show PostgreSqlTableEngine
Show PostgreSqlTableEngine
POSTGRESQL
.Show TableEngineType
Show TableEngineType
MERGE_TREE
: The MergeTree table engine.REPLACING_MERGE_TREE
: The ReplacingMergeTree table engine.SUMMING_MERGE_TREE
: The SummingMergeTree table engine.AGGREGATING_MERGE_TREE
: The AggregatingMergeTree table engine.POSTGRESQL
: The PostgreSQL table engine.
DataPoolOrFailureResponse
The result of a mutation which creates or modifies a Data Pool. If successful, anDataPoolResponse
will be returned; otherwise, a
FailureResponse
will be returned.
Show DataPoolResponse
Show DataPoolResponse
Show DataPool
Show DataPool
Arguments
Show Deprecated Fields
Show Deprecated Fields
MetricSettings
A Metric’s settings, depending on its type.Show CountMetricSettings
Show CountMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show SumMetricSettings
Show SumMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show CountDistinctMetricSettings
Show CountDistinctMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show AverageMetricSettings
Show AverageMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show MinMetricSettings
Show MinMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show MaxMetricSettings
Show MaxMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Dimension
Show Dimension
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.Show CustomMetricSettings
Show CustomMetricSettings
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.You can provide the filters in the form of SQL.Show Deprecated Fields
Show Deprecated Fields
filters
property on the timeSeriesInput
, counterInput
, or leaderboardInput
objects. There is no need to add filters
to be able to filter at query time.deprecated: Use filterSql
insteadShow Filter
Show Filter
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
.