uschindler edited a comment on pull request #2052: URL: https://github.com/apache/lucene-solr/pull/2052#issuecomment-729037126
> Second, it is extremely experimental and not clear when it provides benefits / what risks there are / etc. We need to learn much more about it, in diverse usage, to help here. I'd love to hear from Elasticsearch or Solr users if this helps, since those applications do simultaneous indexing (merging) and searching on the same box. I am sure, you at amazon will test it extensively. But I agree: I would not make this any default, I am still in favour of using plain MMAPDirectory. The risks of making it worse by using direct io is too heavy. > Third, users are able to choose to use this when they instantiate the Directory implementation for their search application, so it is straightforward to adopt and play with, even if Lucene's core does not do so by default. +1 Elasticsearch may play with it and may also improve the parts where it is actually used. We do not know yet if it is a good idea to use it when you merge stuff that needs heavy random access to index (like you have a FilterCodecReader during merging, transform an index, resort it,...). Also it depends on codecs and how they are implemented. Unless we know that it works well for merging all partsof Lucene's core codecs, we may do a recommendation. If we decide to make it part of Lucene core, we can just move it. It will compile and work out of box with current Java versions and most file systems. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
