Skip to content
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

Percolating an item of a type that has a default _ttl mapping configured throws an error #2975

Closed
MrSnark opened this Issue May 2, 2013 · 0 comments

Comments

Projects
None yet
1 participant
@MrSnark
Copy link

commented May 2, 2013

Using elasticsearch version 0.90 - windows binaries.

When I try to percolate an item for an index/type that has a default _ttl defined, I get the following error:

{
  "error":
  "MapperParsingException[failed to parse [_ttl]]; nested: AlreadyExpiredException[already expired [test]/[type1]/[null] due to expire at [5184000000] and was processed at [1367509482308]]; ",
  "status":400
}

Here are the steps to recreate the error:

curl -XPUT localhost:9200/test

curl -XPUT localhost:9200/test/type1/_mapping -d '{ 
        "type1": { 
             "_ttl": { 
               "enabled": true,
               "default": "60d"
             },
             "_timestamp": { "enabled": true } 
        }
      }'

curl -XPUT localhost:9200/_percolator/test/kuku -d '{ 
          "query" : { 
              "term" : { 
                "field1" : "value1" 
              } 
            }
        }'

curl -XGET localhost:9200/test/type1/_percolate -d '{ "doc" : { "field1" : "value1" }}'

spinscale added a commit to spinscale/elasticsearch that referenced this issue May 21, 2013

Fixing percolation of documents with TTL set
When a type is configured with a TTL, percolation of documents of this type
was not possible. This fix ignores the TTL for percolation instead of
throwing an exception that the document is already expired.

Closes elastic#2975

@spinscale spinscale closed this in 2e4d18b May 24, 2013

spinscale added a commit that referenced this issue May 24, 2013

Fixing percolation of documents with TTL set
When a type is configured with a TTL, percolation of documents of this type
was not possible. This fix ignores the TTL for percolation instead of
throwing an exception that the document is already expired.

Closes #2975

mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015

Fixing percolation of documents with TTL set
When a type is configured with a TTL, percolation of documents of this type
was not possible. This fix ignores the TTL for percolation instead of
throwing an exception that the document is already expired.

Closes elastic#2975
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.