Trouble with Delete Mapping

Elastic Stack Elasticsearch
1

I am having some trouble with Delete Mapping leaving behind a "ghost" of itself. Here is the scenario:

  1. Field affiliate_network_id is an unanalyzed string in /dffs/mer type.
  2. DELETE /dffs/mer type mapping.
  3. Check to confirm that all docs in /dffs/mer are gone.
  4. PUT /dffs/mer with field affiliate_network_id as an integer.
  5. Re-import /dffs/mer data.

Afterwards, when I facet on affiliate_network_id, it gives a type mismatch error. We have tried Flush, Clear Cache, Refresh, Optimize after step 2) but none of it can get rid of the mapping "ghost" that the previous incarnation of the mapping left behind. When we create the /dffs/mer mapping in a new index /dffn as /dffn/mer everything works just fine.

Does anybody know how I can fully wipe/change a field in a mapping without leaving behind the mapping "ghost" or wiping out the whole /dffs index? We are currently running 0.15.2.

2

Can you gist a recreation? In general, delete mapping uses also delete by query to delete all the docs matching that mapping, and in most times, it makes more sense to index data into a new index.
On Wednesday, May 4, 2011 at 5:34 PM, Sorostaran wrote:

I am having some trouble with Delete Mapping leaving behind a "ghost" of
itself. Here is the scenario:

  1. Field affiliate_network_id is an unanalyzed string in /dffs/mer type.
  2. DELETE /dffs/mer type mapping.
  3. Check to confirm that all docs in /dffs/mer are gone.
  4. PUT /dffs/mer with field affiliate_network_id as an integer.
  5. Re-import /dffs/mer data.

Afterwards, when I facet on affiliate_network_id, it gives a type mismatch
error. We have tried Flush, Clear Cache, Refresh, Optimize after step 2) but
none of it can get rid of the mapping "ghost" that the previous incarnation
of the mapping left behind. When we create the /dffs/mer mapping in a new
index /dffn as /dffn/mer everything works just fine.

Does anybody know how I can fully wipe/change a field in a mapping without
leaving behind the mapping "ghost" or wiping out the whole /dffs index? We
are currently running 0.15.2.

--
View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Trouble-with-Delete-Mapping-tp2899088p2899088.html
Sent from the Elasticsearch Users mailing list archive at Nabble.com.