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 AWS 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.

Contents

• Updating an existing Neptune full-text search stack to support non-string indexing

• Filtering what fields are indexed in Neptune full-text search

  • Filter by property or predicate name

  • Filter by property or predicate value type

• Mapping of SPARQL and Gremlin datatypes to OpenSearch

• Validation of data mappings

• Sample non-string OpenSearch queries in Neptune

  • Get all vertices with age greater than 30 and name starting with "Si"

  • Get all nodes with age between 10 and 50 and a name with a fuzzy match with "Ronka"

  • Get all nodes with a timestamp that falls within the last 25 days

  • Get all nodes with a timestamp that falls within a given year and month