Non-string OpenSearch indexing in Amazon Neptune - Amazon Neptune
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Non-string OpenSearch indexing in Amazon Neptune

Non-string OpenSearch indexing in Amazon Neptune allows replicating non-string values for predicates to OpenSearch using the stream poller. All predicate values that can safely be converted to a corresponding OpenSearch mapping or datatype is then replicated to OpenSearch.

For non-string indexing to be enabled on a new stack, the Enable Non-String Indexing flag in the Amazon CloudFormation template must be set to true. This is the default setting. To update an existing stack to support non-string indexing, see Updating an existing stack below.

Note
  • It is best not to enable non-string indexing on engine versions earlier than 1.0.4.2.

  • OpenSearch queries using regular expressions for field names that match multiple fields, some of which contain string values and others of which contain non-string values, fail with an error. The same thing happens if full-text search queries in Neptune are of that type.

  • When sorting by a non-string field, append ".value" to the field name to differentiate it from a string field.