Skip to content

Change on the ignore_above default value. #27991

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Conversation

AlJuan
Copy link

@AlJuan AlJuan commented Dec 26, 2017

I think the ignore_above default value is wrong on the documentation.
I tried a little example:

  • First create an index:
    curl -XPUT 'localhost:9200/test?pretty' -H 'Content-Type: application/json' -d' { "settings" : { "index" : { } } }'
  • Then insert some value:
    curl -XPUT 'localhost:9200/test/testType/1?pretty' -H 'Content-Type: application/json' -d' { "user" : "kimchy", "post_date" : "2009-11-15T14:12:12", "message" : "trying out Elasticsearch" } '

When I get the mapping info for that index (curl -XGET 'localhost:9200/test/_mapping/testType?pretty') it returns:

{
  "test" : {
    "mappings" : {
      "testType" : {
        "properties" : {
          "message" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          },
          "post_date" : {
            "type" : "date"
          },
          "user" : {
            "type" : "text",
            "fields" : {
              "keyword" : {
                "type" : "keyword",
                "ignore_above" : 256
              }
            }
          }
        }
      }
    }
  }
}

In addition to this, there is a blog post by Adrien Grand saying that the default ignore_above value is 256.

I also tried inserting data with a keyword field value longer than 256. Elastic will store it, but i am not able to search on it.

@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

1 similar comment
@elasticmachine
Copy link
Collaborator

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants