{{< label “Sink: Batch” >}} {{< label “Sink: Streaming Append & Upsert Mode” >}}
The Opensearch connector allows for writing into an index of the Opensearch engine. This document describes how to setup the Opensearch Connector to run SQL queries against Opensearch.
The connector can operate in upsert mode for exchanging UPDATE/DELETE messages with the external system using the primary key defined on the DDL.
If no primary key is defined on the DDL, the connector can only operate in append mode for exchanging INSERT only messages with external system.
{{< sql_connector_download_table “opensearch” >}}
The Opensearch connector is not part of the binary distribution. See how to link with it for cluster execution [here]({{< ref “docs/dev/configuration/overview” >}}).
The example below shows how to create an Opensearch sink table:
CREATE TABLE myUserTable ( user_id STRING, user_name STRING, uv BIGINT, pv BIGINT, PRIMARY KEY (user_id) NOT ENFORCED ) WITH ( 'connector' = 'opensearch', 'hosts' = 'http://localhost:9200', 'index' = 'users' );
The Opensearch sink can work in either upsert mode or append mode, depending on whether a primary key is defined. If a primary key is defined, the Opensearch sink works in upsert mode which can consume queries containing UPDATE/DELETE messages. If a primary key is not defined, the Opensearch sink works in append mode which can only consume queries containing INSERT only messages.
In the Opensearch connector, the primary key is used to calculate the Opensearch document id, which is a string of up to 512 bytes. It cannot have whitespaces. The Opensearch connector generates a document ID string for every row by concatenating all primary key fields in the order defined in the DDL using a key delimiter specified by document-id.key-delimiter. Certain types are not allowed as a primary key field as they do not have a good string representation, e.g. BYTES, ROW, ARRAY, MAP, etc. If no primary key is specified, Opensearch will generate a document id automatically.
See [CREATE TABLE DDL]({{< ref “docs/dev/table/sql/create” >}}#create-table) for more details about the PRIMARY KEY syntax.
The Opensearch sink supports both static index and dynamic index.
If you want to have a static index, the index option value should be a plain string, e.g. 'myusers', all the records will be consistently written into “myusers” index.
If you want to have a dynamic index, you can use {field_name} to reference a field value in the record to dynamically generate a target index. You can also use '{field_name|date_format_string}' to convert a field value of TIMESTAMP/DATE/TIME type into the format specified by the date_format_string. The date_format_string is compatible with Java's DateTimeFormatter. For example, if the option value is 'myusers-{log_ts|yyyy-MM-dd}', then a record with log_ts field value 2020-03-27 12:25:55 will be written into “myusers-2020-03-27” index.
You can also use '{now()|date_format_string}' to convert the current system time to the format specified by date_format_string. The corresponding time type of now() is TIMESTAMP_WITH_LTZ. When formatting the system time as a string, the time zone configured in the session through table.local-time-zone will be used. You can use NOW(), now(), CURRENT_TIMESTAMP, current_timestamp.
NOTE: When using the dynamic index generated by the current system time, for changelog stream, there is no guarantee that the records with the same primary key can generate the same index name. Therefore, the dynamic index based on the system time can only support append only stream.
Opensearch stores document in a JSON string. So the data type mapping is between Flink data type and JSON data type. Flink uses built-in 'json' format for Opensearch connector. Please refer to [JSON Format]({{< ref “docs/connectors/table/formats/json” >}}) page for more type mapping details.
{{< top >}}