You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OpenSearch does not allow sending documents with an _id field. So using the docdb_id will allow saving all the data from a DocumentDb object while also using a valid OpenSearch Id.
Examples
For example, say we have the following DocumentDb documents:
Every DocumentDb object must have an
_id
field. The Data Prepperdocumentdb
source should do two things with this value:primary_key
which is a string representation of that value.docdb_id
with matches the data from_id
. This should use the same mappings as found in DocumentDb simple representations of BSON types #4458.OpenSearch does not allow sending documents with an
_id
field. So using thedocdb_id
will allow saving all the data from a DocumentDb object while also using a valid OpenSearch Id.Examples
For example, say we have the following DocumentDb documents:
and
We'd like to retain the original data inside the OpenSearch index.
So the
documentdb
source should output the following:and
Say the user has the following sink configuration:
Then, in OpenSearch, this will look like:
Configuration
Also, we should allow users to configure the value used in the source.
The text was updated successfully, but these errors were encountered: