[pulsar-site] branch main updated: Docs sync done from apache/pulsar(#de9928a)

[ur...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

urfree pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pulsar-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 22604033a87 Docs sync done from apache/pulsar(#de9928a)
22604033a87 is described below

commit 22604033a8719887b1ef19a06234ca943949d41f
Author: Pulsar Site Updater <de...@pulsar.apache.org>
AuthorDate: Fri Jun 10 18:05:26 2022 +0000

    Docs sync done from apache/pulsar(#de9928a)
---
 site2/website-next/docs/io-elasticsearch-sink.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/site2/website-next/docs/io-elasticsearch-sink.md b/site2/website-next/docs/io-elasticsearch-sink.md
index 7decfc96552..1b4449daef7 100644
--- a/site2/website-next/docs/io-elasticsearch-sink.md
+++ b/site2/website-next/docs/io-elasticsearch-sink.md
@@ -88,6 +88,7 @@ The configuration of the Elasticsearch sink connector has the following properti
 | `apiKey` | String| false | " " (empty string)|The apiKey used by the connector to connect to the ElasticSearch cluster. Only one between basic/token/apiKey authentication mode must be configured. |
 | `canonicalKeyFields` | Boolean | false | false | Whether to sort the key fields for JSON and Avro or not. If it is set to `true` and the record key schema is `JSON` or `AVRO`, the serialized object does not consider the order of properties. |
 | `stripNonPrintableCharacters` | Boolean| false | true| Whether to remove all non-printable characters from the document or not. If it is set to true, all non-printable characters are removed from the document. |
+| `idHashingAlgorithm` | enum(NONE,SHA256,SHA512)| false | NONE|Hashing algorithm to use for the document id. This is useful in order to be compliant with the ElasticSearch _id hard limit of 512 bytes. |
 
 ### Definition of ElasticSearchSslConfig structure: