jpountz commented on PR #1017: URL: https://github.com/apache/lucene/pull/1017#issuecomment-1196903627
I chatted a bit with @iverase (we work together at Elastic) about this change. Like Ignacio wrote, we are interested in it since it maps to similar functionality that we have in Elasticsearch, but if Lucene gets the same functionality it would make more sense for Elasticsearch to move to it rather than keep a duplicate implementation. We suggested reusing the Elasticsearch implementation because it's been through many rounds of testing and performance benchmarks already, which we thought would help avoid duplicating work, and we'd be happy to do the small changes that would make it more naturally fit Lucene such as changing the encoding frob BE to LE. But we don't want to force it either and if this suggestion is not getting traction, then let's go iteratively as you suggest. -- 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. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org 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
