>I tried to merge the 15 indexes again, and I found out that the new merged >index (without opitmization) size was about 351 GB , but when I optimize it >the size return back to 411 GB, Why?
Just as a sample, IOT in Oracle... Ok, just in a kids-lang, what 'optimization' means? It means that Map is physically sorted by Key... For Lucene, 'map' is 'term -> documentIDs'. Ok, still no any problem... but what if KEY is compressed? (or, for instance, 'normalized' if you are still with RDBMS) And we need to decompress it for uniting 15 maps? -Fuad
