Restarting ES breaks nested term mapping


#1

I have Couchdb_changes in logstash feeding ES. I've got 242 docs being indexed currently in my dev environment.

I restarted my ES docker container, and my searches stopped working as they had been.

Prior to restarting (and again after I trashed and rebuilt my index from scratch)
curl http://localhost:9200/hx/logs/_search?pretty=true&q=: gives me 242 hits
curl http://localhost:9200/hx/_search?q=class:section returns the expected document as a hit.
curl http://localhost:9200/hx/_search?q=_id:s1 returns the expected document as a hit.

After a restart of the docker container:
curl http://localhost:9200/hx/logs/_search?pretty=true&q=: gives me 242 hits
curl http://localhost:9200/hx/_search?q=class:section returns zero hits.
curl http://localhost:9200/hx/_search?q=doc.class:section returns the expected document as a hit. (note the inclusion of "doc" in the term)

Full results are at https://gist.github.com/Grokling/b37a145c73156199cec1

I'd love to hear how I can retain this functionality through a restart, or get it back after a restart without destroying and reloading the index.


#2

This issue has now been confirmed on a different machine.


(David Pilato) #3

Can you get the mapping before and after the restart?

That's super strange.

Also could you try the same with 1.6.0


#5

I've just tried with ES 1.6.0, and have not been able to reproduce the issue.

Guess I just upgraded versions. Good suggestion, thanks.


(system) #6