Exists filter broken on 1.5.0 with restored index?

Elastic Stack Elasticsearch
1

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a restore of
a snapshot made with es-1.4.1. All documents are there, but the exists
filter seems broken. The query that used to return all documents matching,
now return 0 documents, even though the field exists when reading the
documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://carter:9200/skyfish_v2/document/_search" -d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4d7d4080-c997-412e-85cd-04d7aeda0e27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Hi Mads Martin,

Could you check the version that is returned when you run curl
"localhost:9200/my_own_index/_settings?pretty". The version will be in

    "version" : {
      "created" : "XXXXXXX"
    }

Could you compare it to the version that is returned by the same index in
the pre-1.5.0 cluster?

Igor

On Wednesday, 25 March 2015 09:27:03 UTC-4, Mads Martin Jørgensen wrote:

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a restore
of a snapshot made with es-1.4.1. All documents are there, but the exists
filter seems broken. The query that used to return all documents matching,
now return 0 documents, even though the field exists when reading the
documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://www.google.com/url?q=http%3A%2F%2Fcarter%3A9200%2Fskyfish_v2%2Fdocument%2F_search&sa=D&sntz=1&usg=AFQjCNHx9tllVr6Ip2n5zS9uz9FNweGcWg"
-d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3937725f-6381-442b-9e2b-638913514d3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

They're similar. The 1.5.0 cluster has "created" : "1000199", and the 1.4.1
cluster also has "created" : "1000199"

On Wednesday, March 25, 2015 at 4:45:30 PM UTC+1, Igor Motov wrote:

Hi Mads Martin,

Could you check the version that is returned when you run curl
"localhost:9200/my_own_index/_settings?pretty". The version will be in

    "version" : {
      "created" : "XXXXXXX"
    }

Could you compare it to the version that is returned by the same index in
the pre-1.5.0 cluster?

Igor

On Wednesday, 25 March 2015 09:27:03 UTC-4, Mads Martin Jørgensen wrote:

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a restore
of a snapshot made with es-1.4.1. All documents are there, but the exists
filter seems broken. The query that used to return all documents matching,
now return 0 documents, even though the field exists when reading the
documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://www.google.com/url?q=http%3A%2F%2Fcarter%3A9200%2Fskyfish_v2%2Fdocument%2F_search&sa=D&sntz=1&usg=AFQjCNHx9tllVr6Ip2n5zS9uz9FNweGcWg"
-d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/ff38b5a8-ebab-4061-a963-5e74a807de3e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Thanks for checking. It's a bug, which should be fixed in
1.5.1 https://github.com/elastic/elasticsearch/pull/10268

On Wednesday, 25 March 2015 13:43:28 UTC-4, Mads Martin Jørgensen wrote:

They're similar. The 1.5.0 cluster has "created" : "1000199", and the
1.4.1 cluster also has "created" : "1000199"

On Wednesday, March 25, 2015 at 4:45:30 PM UTC+1, Igor Motov wrote:

Hi Mads Martin,

Could you check the version that is returned when you run curl
"localhost:9200/my_own_index/_settings?pretty". The version will be in

    "version" : {
      "created" : "XXXXXXX"
    }

Could you compare it to the version that is returned by the same index in
the pre-1.5.0 cluster?

Igor

On Wednesday, 25 March 2015 09:27:03 UTC-4, Mads Martin Jørgensen wrote:

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a restore
of a snapshot made with es-1.4.1. All documents are there, but the exists
filter seems broken. The query that used to return all documents matching,
now return 0 documents, even though the field exists when reading the
documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://www.google.com/url?q=http%3A%2F%2Fcarter%3A9200%2Fskyfish_v2%2Fdocument%2F_search&sa=D&sntz=1&usg=AFQjCNHx9tllVr6Ip2n5zS9uz9FNweGcWg"
-d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/531c6e3c-5697-4fc0-b037-d8fbc438c5dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

5

Thanks for fixing!

On Thursday, March 26, 2015 at 3:29:17 PM UTC+1, Igor Motov wrote:

Thanks for checking. It's a bug, which should be fixed in 1.5.1
https://github.com/elastic/elasticsearch/pull/10268

On Wednesday, 25 March 2015 13:43:28 UTC-4, Mads Martin Jørgensen wrote:

They're similar. The 1.5.0 cluster has "created" : "1000199", and the
1.4.1 cluster also has "created" : "1000199"

On Wednesday, March 25, 2015 at 4:45:30 PM UTC+1, Igor Motov wrote:

Hi Mads Martin,

Could you check the version that is returned when you run curl
"localhost:9200/my_own_index/_settings?pretty". The version will be in

    "version" : {
      "created" : "XXXXXXX"
    }

Could you compare it to the version that is returned by the same index
in the pre-1.5.0 cluster?

Igor

On Wednesday, 25 March 2015 09:27:03 UTC-4, Mads Martin Jørgensen wrote:

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a
restore of a snapshot made with es-1.4.1. All documents are there, but the
exists filter seems broken. The query that used to return all documents
matching, now return 0 documents, even though the field exists when reading
the documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://www.google.com/url?q=http%3A%2F%2Fcarter%3A9200%2Fskyfish_v2%2Fdocument%2F_search&sa=D&sntz=1&usg=AFQjCNHx9tllVr6Ip2n5zS9uz9FNweGcWg"
-d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/5ef4c402-3609-4780-bc64-049ea5c76751%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

6

Seems like it also impacts "missing". Just checking that the patch will
address that too? Looks like it will from the file changes in the patch
code, but thought I'd better mention it, just in case! :slight_smile:

On Thursday, 26 March 2015 18:31:44 UTC, Mads Martin Jørgensen wrote:

Thanks for fixing!

On Thursday, March 26, 2015 at 3:29:17 PM UTC+1, Igor Motov wrote:

Thanks for checking. It's a bug, which should be fixed in 1.5.1
https://github.com/elastic/elasticsearch/pull/10268

On Wednesday, 25 March 2015 13:43:28 UTC-4, Mads Martin Jørgensen wrote:

They're similar. The 1.5.0 cluster has "created" : "1000199", and the
1.4.1 cluster also has "created" : "1000199"

On Wednesday, March 25, 2015 at 4:45:30 PM UTC+1, Igor Motov wrote:

Hi Mads Martin,

Could you check the version that is returned when you run curl
"localhost:9200/my_own_index/_settings?pretty". The version will be in

    "version" : {
      "created" : "XXXXXXX"
    }

Could you compare it to the version that is returned by the same index
in the pre-1.5.0 cluster?

Igor

On Wednesday, 25 March 2015 09:27:03 UTC-4, Mads Martin Jørgensen wrote:

Hello all,

Just installed es-1.5.0 with cloud-aws-2.5.0 on a machine. Did a
restore of a snapshot made with es-1.4.1. All documents are there, but the
exists filter seems broken. The query that used to return all documents
matching, now return 0 documents, even though the field exists when reading
the documents.

curl -XGET "http://localhost:9200/my_own_index/document/_search
http://www.google.com/url?q=http%3A%2F%2Fcarter%3A9200%2Fskyfish_v2%2Fdocument%2F_search&sa=D&sntz=1&usg=AFQjCNHx9tllVr6Ip2n5zS9uz9FNweGcWg"
-d'

{

"query": {

  "constant_score": {

     "filter": {

        "exists": {

           "field": "history"

        }

     }

  }

}

}'

If we populate new documents, then the exists filter works just fine.

Regards,

Mads Martin

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4f4e4538-37e0-4da5-8761-1a65fbd74957%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.