Details

    • Type: Sub-task
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.0
    • Component/s: ElasticSearch
    • Labels:

      Description

      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in types: authorization, issue.
      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in types: activeRule, rule.
      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in type: activity.
      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in type: test.
      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in type: user.
      The _id field can no longer be configured in new indices. Importantly, it will not be possible to extract the _id value from a path, in type: view.

      https://www.elastic.co/guide/en/elasticsearch/reference/2.0/breaking_20_mapping_changes.html#migration-meta-fields
      https://www.elastic.co/guide/en/elasticsearch/reference/2.3/mapping-uid-field.html

      The _id field is not indexed as its value can be derived automatically from the _uid field.

      The value of the _id field is accessible in queries and scripts, but not in aggregations or when sorting, where the _uid field should be used instead

        Attachments

          Activity

            People

            • Assignee:
              simon.brandhof Simon Brandhof
              Reporter:
              eric.duquesnoy Eric Duquesnoy (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Due:
                Created:
                Updated:
                Resolved: