Hi Following the discussion on LUCENE-5121 I want to propose that we make DiskDVFormat not experimental. The reason is that the way things are now, we're basically telling everyone that if you're using DV, you have to have all of them in-memory. If you can't, you're on your own -- either use the experimental DiskDV which we don't guarantee backwards support for, or write your own DVFormat, which is uber expert.
I'm not sure if it's good that we force high-memory consumption when using Lucene. We don't enforce that in other places (e.g. users can tweak IW.ramBuffer, termIndexInterval etc.), and DV should be no exception, especially as it will likely be big. I don't advocate for making DiskDV the default, just to allow a supported disk-based one. Some apps may not be able to load DV entirely into memory, and the alternatives aren't great IMO. I guess I see in-memory DVFormat as an optimization of DiskDV, and not another way to encode DVs (as opposed to custom PostingsFormats). What would it take to make it not experimental? Is it just the removal of @lucene.experimental or do we need to name it otherwise? Fix outstanding issues? Shai
