◆ getRecordsFromCollection() [1/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecordsFromCollection() [2/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
◆ getRecordsFromCollection() [3/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecordsFromCollection() [4/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | schema_ | Avro schema object used for decoding returned objects. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecordsFromCollection() [5/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecordsFromCollection() [6/20]
| GetRecordsFromCollectionResponse< boost::any > gpudb::GPUdb::getRecordsFromCollection | ( | const GetRecordsFromCollectionRequest & | request_ | ) | const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecordsFromCollection() [7/20]
| GetRecordsFromCollectionResponse< boost::any > gpudb::GPUdb::getRecordsFromCollection | ( | const GetRecordsFromCollectionRequest & | request_ | ) | const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | request_ | Request object containing the parameters for the operation. |
◆ getRecordsFromCollection() [8/20]
| GetRecordsFromCollectionResponse< boost::any > & gpudb::GPUdb::getRecordsFromCollection | ( | const GetRecordsFromCollectionRequest & | request_, |
| GetRecordsFromCollectionResponse< boost::any > & | response_ ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
◆ getRecordsFromCollection() [9/20]
| GetRecordsFromCollectionResponse< boost::any > & gpudb::GPUdb::getRecordsFromCollection | ( | const GetRecordsFromCollectionRequest & | request_, |
| GetRecordsFromCollectionResponse< boost::any > & | response_ ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
◆ getRecordsFromCollection() [10/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
◆ getRecordsFromCollection() [11/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecordsFromCollection() [12/20]
| GetRecordsFromCollectionResponse< boost::any > gpudb::GPUdb::getRecordsFromCollection | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecordsFromCollection() [13/20]
| GetRecordsFromCollectionResponse< boost::any > gpudb::GPUdb::getRecordsFromCollection | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecordsFromCollection() [14/20]
| GetRecordsFromCollectionResponse< boost::any > & gpudb::GPUdb::getRecordsFromCollection | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options, | ||
| GetRecordsFromCollectionResponse< boost::any > & | response_ ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecordsFromCollection() [15/20]
| GetRecordsFromCollectionResponse< boost::any > & gpudb::GPUdb::getRecordsFromCollection | ( | const std::string & | tableName, |
| const int64_t | offset, | ||
| const int64_t | limit, | ||
| const std::map< std::string, std::string > & | options, | ||
| GetRecordsFromCollectionResponse< boost::any > & | response_ ) const |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecordsFromCollection() [16/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |
◆ getRecordsFromCollection() [17/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
◆ getRecordsFromCollection() [18/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
◆ getRecordsFromCollection() [19/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | type_ | Type object used for decoding returned objects. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
◆ getRecordsFromCollection() [20/20]
| inline |
Retrieves records from a collection.
The operation can optionally return the record IDs which can be used in certain queries such as deleteRecords.
This operation supports paging through the data via the offset and limit parameters.
Note that when using the Java API, it is not possible to retrieve records from join views using this operation. (DEPRECATED)
| TResponse | The type of object being retrieved. |
| [in] | type_ | Type object used for decoding returned objects. |
| [in] | tableName | Name of the collection or table from which records are to be retrieved, in [schema_name.]table_name format, using standard name resolution rules. Must be an existing collection or table. |
| [in] | offset | A positive integer indicating the number of initial results to skip (this can be useful for paging through the results). The default value is 0. The minimum allowed value is 0. The maximum allowed value is MAX_INT. |
| [in] | limit | A positive integer indicating the maximum number of results to be returned, or END_OF_SET (-9999) to indicate that the maximum number of results allowed by the server should be returned. The number of records returned will never exceed the server’s own limit, defined by the max_get_records_size parameter in the server configuration. Use offset and limit to request subsequent pages of results. The default value is -9999. |
| [in] | options |
|
| [out] | response_ | Response object containing the results of the operation. |