Skip to main content
Source

​
pub async fn insert_records_from_payload( &self, table_name: String, data_text: String, data_bytes: ByteBuf, modify_columns: HashMap<String, HashMap<String, String>>, create_table_options: HashMap<String, String>, ) -> Result<InsertRecordsFromPayloadResponse, KineticaError>

Insert records from a text-based or binary payload into the specified target table

Reads from the given text-based or binary payload and inserts the data into a new or existing table. The table will be created if it doesn’t already exist.

Returns once all records are processed.

  • table_name - Name of the table into which the data will be inserted, in [schema_name.]table_name format, using standard name resolution rules. If the table does not exist, the table will be created using either an existing type_id or the type inferred from the payload, and the new table name will have to meet standard table naming criteria.
  • data_text - Records formatted as delimited text.
  • data_bytes - Records formatted as binary data.
  • modify_columns - Not implemented yet.
  • create_table_options - Options used when creating the target table. Includes type to use. The other options match those in /create/table.
Source

​
pub async fn insert_records_from_payload_with_opts( &self, table_name: String, data_text: String, data_bytes: ByteBuf, modify_columns: HashMap<String, HashMap<String, String>>, create_table_options: HashMap<String, String>, options: InsertRecordsFromPayloadRequestOptions, ) -> Result<InsertRecordsFromPayloadResponse, KineticaError>

Insert records from a text-based or binary payload into the specified target table

Reads from the given text-based or binary payload and inserts the data into a new or existing table. The table will be created if it doesn’t already exist.

Returns once all records are processed.

  • table_name - Name of the table into which the data will be inserted, in [schema_name.]table_name format, using standard name resolution rules. If the table does not exist, the table will be created using either an existing type_id or the type inferred from the payload, and the new table name will have to meet standard table naming criteria.
  • data_text - Records formatted as delimited text.
  • data_bytes - Records formatted as binary data.
  • modify_columns - Not implemented yet.
  • create_table_options - Options used when creating the target table. Includes type to use. The other options match those in /create/table.
  • options - The optional parameters; any left unset take the server’s defaults.

Sends a pre-built InsertRecordsFromPayloadRequest to the /insert/records/frompayload endpoint.

Sends a pre-built InsertRecordsFromPayloadRequest to a specific worker URL, bypassing HA head-node selection. Used for multi-head access.