# V0.16 upgrade: search now broken

**URL:** <https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405>\
**Category:** Elasticsearch\
**Created:** [May 14, 2011, 8:01pm UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405 "2011-05-14T20:01:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![searchersteve](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchersteve/32/3008_2.png) [@searchersteve](https://discuss.elastic.co/u/searchersteve)\
**Post date:** [May 14, 2011, 8:01pm UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405/1 "2011-05-14T20:01:05Z")

</div>

My upgrade to 0.16 has not gone smoothly, I'm afraid.

I had a set of mappings and bulk indexing operations that worked. After the upgrade, I got a few errors. So I stripped everything down to a very simple example that had no errors. Cool... But now, when I search on a document that I know should have been indexed -- in the same way I've always searched before -- I get 0 results.

I've recreated the issue here:

[https://gist.github.com/27038d6bdc3f72e29b67](https://gist.github.com/27038d6bdc3f72e29b67)

I am anticipating someone who sees the gist might ask: Why do you have a

{query: {"wildcard": { "\_id": "\*"}}}

It's a bit clunky, but I've structured it this way because my application is building query terms on the fly. This is a case where no query terms were specified -- only filter terms.

Anyway, I don't think that has anything to do with my problem. But you may have a better answer.

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![Paul\_Loy](https://avatars.discourse-cdn.com/v4/letter/p/ad7895/32.png) [@Paul\_Loy](https://discuss.elastic.co/u/Paul_Loy)\
**Post date:** [May 14, 2011, 8:12pm UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405/2 "2011-05-14T20:12:56Z")

</div>

Look at the very top change here:

> **[Elastic — The Search AI Company](https://www.elastic.co)**
>
> Power insights and outcomes with The Elastic Search AI Platform. See into your data and find answers that matter with enterprise solutions designed to help you accelerate time to insight. Try Elastic ...

If you want to match all, why not do:

{query: "match\_all"}

Cheers,

On Sat, May 14, 2011 at 9:01 PM, searchersteve [stevesuo@gmail.com](mailto:stevesuo@gmail.com) wrote:

> My upgrade to 0.16 has not gone smoothly, I'm afraid.
> 
> I had a set of mappings and bulk indexing operations that worked. After the  
> upgrade, I got a few errors. So I stripped everything down to a very simple  
> example that had no errors. Cool... But now, when I search on a document  
> that I know should have been indexed -- in the same way I've always  
> searched  
> before -- I get 0 results.
> 
> I've recreated the issue here:
> 
> [ElasticSearch mapping problem · GitHub](https://gist.github.com/27038d6bdc3f72e29b67)  
> [ElasticSearch mapping problem · GitHub](https://gist.github.com/27038d6bdc3f72e29b67)
> 
> I am anticipating someone who sees the gist might ask: Why do you have a
> 
> {query: {"wildcard": { "\_id": "\*"}}}
> 
> It's a bit clunky, but I've structured it this way because my application  
> is  
> building query terms on the fly. This is a case where no query terms were  
> specified -- only filter terms.
> 
> Anyway, I don't think that has anything to do with my problem. But you may  
> have a better answer.
> 
> Thanks in advance.
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/v0-16-upgrade-search-now-broken-tp2941118p2941118.html](http://elasticsearch-users.115913.n3.nabble.com/v0-16-upgrade-search-now-broken-tp2941118p2941118.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

## --

Paul Loy  
[paul@keteracel.com](mailto:paul@keteracel.com)  
[http://uk.linkedin.com/in/paulloy](http://uk.linkedin.com/in/paulloy)

---

<div class="post-metadata">

**Author:** ![searchersteve](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/searchersteve/32/3008_2.png) [@searchersteve](https://discuss.elastic.co/u/searchersteve)\
**Post date:** [May 14, 2011, 8:42pm UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405/3 "2011-05-14T20:42:48Z")

</div>

Oh boy. I feel really dumb now. I read the breaking changes, but somehow it didn't enter my brain.

It works for me now when I do this:

```
        "query" : {
            "match_all" : {}
        },

```

For completeness sake, I've created a new gist with the corrected code:

[https://gist.github.com/c86ae9e406cbb0c51279](https://gist.github.com/c86ae9e406cbb0c51279)

Thanks Paul!!

Look at the very top change here: http://www.elasticsearch.org/download/2011/04/23/0.16.0.html

If you want to match all, why not do:

{query: "match\_all"}

Cheers,

On Sat, May 14, 2011 at 9:01 PM, searchersteve \<[stevesuo@gmail.com](mailto:stevesuo@gmail.com)\> wrote:

> My upgrade to 0.16 has not gone smoothly, I'm afraid.
> 
> I had a set of mappings and bulk indexing operations that worked. After the  
> upgrade, I got a few errors. So I stripped everything down to a very simple  
> example that had no errors. Cool... But now, when I search on a document  
> that I know should have been indexed -- in the same way I've always  
> searched  
> before -- I get 0 results.
> 
> I've recreated the issue here:
> 
> [ElasticSearch mapping problem · GitHub](https://gist.github.com/27038d6bdc3f72e29b67)  
> [ElasticSearch mapping problem · GitHub](https://gist.github.com/27038d6bdc3f72e29b67)
> 
> I am anticipating someone who sees the gist might ask: Why do you have a
> 
> {query: {"wildcard": { "\_id": "\*"}}}
> 
> It's a bit clunky, but I've structured it this way because my application  
> is  
> building query terms on the fly. This is a case where no query terms were  
> specified -- only filter terms.
> 
> Anyway, I don't think that has anything to do with my problem. But you may  
> have a better answer.
> 
> Thanks in advance.
> 
> --  
> View this message in context:  
> [http://elasticsearch-users.115913.n3.nabble.com/v0-16-upgrade-search-now-broken-tp2941118p2941118.html](http://elasticsearch-users.115913.n3.nabble.com/v0-16-upgrade-search-now-broken-tp2941118p2941118.html)  
> Sent from the Elasticsearch Users mailing list archive at [Nabble.com](http://Nabble.com).

## --

Paul Loy  
[paul@keteracel.com](mailto:paul@keteracel.com)  
[Paul Loy - Amihan Entertainment | LinkedIn](http://uk.linkedin.com/in/paulloy)

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [May 15, 2011, 8:38am UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405/4 "2011-05-15T08:38:55Z")

</div>

On Sat, 2011-05-14 at 21:12 +0100, Paul Loy wrote:

> Look at the very top change here:  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/download/2011/04/23/0.16.0.html)
> 
> If you want to match all, why not do:
> 
> {query: "match\_all"}

Or more efficient than that, use a constant\_score query:

curl -XGET '[http://localhost:9200/\_search](http://localhost:9200/_search)' -d '  
{  
"from": 0,  
"size" : 50,  
"query" : {  
"constant\_score" : {  
"filter" : {  
"bool" : {  
"must" : [  
{  
"term" : {  
"category" : "tweets"  
}  
}  
]  
}  
}  
}  
}  
}'

> 

clint

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 4:06am UTC](https://discuss.elastic.co/t/v0-16-upgrade-search-now-broken/4405/5 "2017-07-06T04:06:13Z")

</div>