On Tue, Apr 1, 2014 at 2:41 AM, Paul Smith <tallpsm...@gmail.com> wrote: > > Thanks Robert for the reply, all of that sounds fairly hairy. I did try a > full optimize of the shard index using Luke, but the residual über-segment > still has the filed definitions in it. Are saying in (1) that the creating > of a new Shard index through a custom call to IndexWriter.addIndexes(..) > would produce a _fully_ optimized index without the fields, and that is > different than what an Optimize operation through ES would call? More a > technical question now on what the differences is between the Optimize call > and a manual create-new-index-from-multiple-readers. (I actually though > that's what the Optimize does in practical terms, but there's obviously more > or less going on under the hood under these different code paths). > > We're going the reindex route for now, was just hoping there was some > special trick we could do a little easier than the above. :) >
Optimize and normal merging don't "garbage collect" unused fields from fieldinfos: https://issues.apache.org/jira/browse/LUCENE-1761 The addindexes trick is also a forced merge, but it decorates the readers-to-be-merged: lying and hiding the fields as if they don't exist. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAMUKNZW2-FEjA6CChSR3%2Br0GQYAfJ9ZOOhyU565V79QMTrPFWQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
