Calculates which objects from a table have a column that is within the given
bounds. An object from the table identified by input parameter table_name is
added to the view input parameter view_name if its column is within [input
parameter lower_bound, input parameter upper_bound] (inclusive). The
operation is synchronous. The response provides a count of the number of
objects which passed the bound filter. Although this functionality can also be
accomplished with the standard filter function, it is more efficient.For track objects, the count reflects how many points fall within the given
bounds (which may not include all the track points of any given track).
Name of the table on which the filter by range operation will be performed, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing table.
If provided, then this will be the name of the view containing the results, in [schema_name.]view_name format, using standard name resolution rules and meeting table naming criteria. Must not be an already existing table or view.The default value is ”.
If true, a unique temporary table name will be generated in the sys_temp schema and used in place of input parameter view_name. This is always allowed even if the caller does not have permission to create tables. The generated name is returned in qualified_view_name.The default value is false.The supported values are:
[DEPRECATED—please specify the containing schema for the view as part of input parameter view_name and use /create/schema to create the schema if non-existent] Name of a schema for the newly created view. If the schema is non-existent, it will be automatically created.
The Kinetica server embeds the endpoint response inside a standard response structure which contains status information and the actual response to the query. Here is a description of the various fields of the wrapper:
