pub async fn filter_by_value( &self, table_name: String, view_name: String, is_string: bool, value: f64, value_str: String, column_name: String, ) -> Result<FilterByValueResponse, KineticaError>
Filter a dataset for records matching a specific value
Calculates which objects from a table has a particular value for a particular column. The input parameters provide a way to specify either a String or a Double valued column and a desired value for the column on which the filter is performed. The operation is synchronous, meaning that a response will not be returned until all the objects are fully available. The response payload provides the count of the resulting set. A new result view which satisfies the input filter restriction specification is also created with a view name passed in as part of the input payload. Although this functionality can also be accomplished with the standard filter function, it is more efficient.
table_name- Name of an existing table on which to perform the calculation, in [schema_name.]table_name format, using standard name resolution rules.view_name- 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.is_string- Indicates whether the value being searched for is string or numeric.value- The value to search for.value_str- The string value to search for.column_name- Name of a column on which the filter by value would be applied.
pub async fn filter_by_value_with_opts( &self, table_name: String, view_name: String, is_string: bool, value: f64, value_str: String, column_name: String, options: FilterByValueRequestOptions, ) -> Result<FilterByValueResponse, KineticaError>
Filter a dataset for records matching a specific value
Calculates which objects from a table has a particular value for a particular column. The input parameters provide a way to specify either a String or a Double valued column and a desired value for the column on which the filter is performed. The operation is synchronous, meaning that a response will not be returned until all the objects are fully available. The response payload provides the count of the resulting set. A new result view which satisfies the input filter restriction specification is also created with a view name passed in as part of the input payload. Although this functionality can also be accomplished with the standard filter function, it is more efficient.
table_name- Name of an existing table on which to perform the calculation, in [schema_name.]table_name format, using standard name resolution rules.view_name- 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.is_string- Indicates whether the value being searched for is string or numeric.value- The value to search for.value_str- The string value to search for.column_name- Name of a column on which the filter by value would be applied.options- The optional parameters; any left unset take the server’s defaults.
pub async fn filter_by_value_raw( &self, request: &FilterByValueRequest, ) -> Result<FilterByValueResponse, KineticaError>
Sends a pre-built FilterByValueRequest to the /filter/byvalue endpoint.
pub async fn filter_by_value_from_url( &self, url: &str, request: &FilterByValueRequest, ) -> Result<FilterByValueResponse, KineticaError>
Sends a pre-built FilterByValueRequest to a specific worker URL, bypassing HA head-node selection. Used for multi-head access.