uschindler commented on issue #12302:
URL: https://github.com/apache/lucene/issues/12302#issuecomment-1551698369

   > > 2. Java is dying and becoming the next COBOL
   > 
   > 😆
   > 
   > > let's carve out a path where we use the vector api IFF the user opts in 
via the command-line.
   > 
   > YES!!! This is timely and the [heart of my comment on the proposal to 
increase KNN dimensionality 
](https://github.com/apache/lucene/issues/11507#issuecomment-1548612414) (_is 
it time we explore a new optional Lucene Vector module that supports cutting 
edge JDK features through gradle tooling for optimizing the vector use case?_).
   > 
   > > Actually the system @uschindler developed I think is the correct design 
for this, .... we need more build system support, it could require more stuff 
to be downloaded or build to be slower. But I think its the right decision?
   > 
   > 💯 agree @uschindler low friction to enable preview is exactly the 
mechanism I was thinking about in my post. I'm not a gradle expert (ping 
@markrmiller ) but I think gradle's java toolchain allows for this type of 
scenario? We did it for enabling preview features on OpenSearch, as did 
Elasticsearch so why can't we use this path in the upstream lucene project? 
Thank you for raising this proposal @rmuir
   > 
   > > ...and lucene is faster and uses correct incubating vector api
   > 
   > One quick question, though. What does this look like in practice? Do we 
create separate classes in `sandbox` to keep this isolated? Are you suggesting 
introducing a new experimental `vector` module w/ vector encapsulated logic? Or 
are you suggesting sprinkling `if (runtimeVersion >= 19 && runtimeVersion <= 
21) {` logic around the existing vector implemenations (e.g., `VectorUtil` and 
KNNVector stuff)? Or a mix of the above? Or is that what we're here to 
brainstorm?
   
   The compilation problem is already solved. No need for toolchains. We tried 
that already, it's a mess especially because it does not support ea releases. 
Read the code referred above for memory mapping. Works identical for vectors 
and incubator. We compile against stubs.


-- 
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

Reply via email to