Upgrade from 1.7 to 2.4 conflicting field mappings

I understand that in 2.4, all fields with the same name in the same index, in different types must of the same mapping. In our 1.7 instance, we have fields with the same name in different types with different mappings. This is because even though these fields represent the same values, we want to index and search differently based upon the type. If we want to continue using this approach, what is the recommended way for us upgrade to 2.4?

A couple of things we are considering are:

  1. Rename the fields such that every field have a unique name.
  2. Create an index for each type.

Anyone else run into this problem?


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.