i have 2 indices being used by an app which is in production. Now, i need to merge these 2 indices so that there is minimal code change or activity to be done from my end. The activity should also not break the existing one in production. Post merge, the app in production should use the newly merged index.
Please suggest a way to do the merge with less hassles.
i have many such kind of fields where structure differs. in that case, will reindex work (because mapping changes after i normalise the representation those collided fields with new mapping) ?
there are 2 features in the app which were developed in parallel. each has its own index. Also, one index is a subset of another. which means, i can use only one index for both the features after making changes to fields / object representation in unison. 1 index is always redundant so thought of merging both of them into one.
Could you illustrate with a concrete example? I don't understand why you would need to do that.
Either data is not useful and you can drop one of the index or the documents need to be merged as a single one coming from both indices in which case you need to reindex by reading the sources, making "joins", then indexing the result.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.