nknize commented on PR #749: URL: https://github.com/apache/lucene/pull/749#issuecomment-1087891213
> I missed that you wanted to discuss this before merging. Not a problem! > Could you explain the open question you'd like to resolve? From my comment above: `"I'm trying to understand if we are planning to eliminate the ability for folks to index just doc values or just points when they are willing to sacrifice performance to save disk storage." ` Feel free to merge this PR so it's not held up and we can continue the discussion on [LUCENE-10162](https://issues.apache.org/jira/browse/LUCENE-10162) as it's more related to that issue. I only raised it here since @jpountz brought it up in [response to the comment above](https://github.com/apache/lucene/pull/749#issuecomment-1083384716) (i.e., `I was phasing out FLOAT / DOUBLE support, as per your comment, but the implementation we will end up with becomes very inconsistent and confusing, for example SortedNumericSortField happily deals with FLOAT / DOUBLE` -- 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
