[ 
https://issues.apache.org/jira/browse/SOLR-17938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18034467#comment-18034467
 ] 

Vivek Narang commented on SOLR-17938:
-------------------------------------

Hey [~hossman], I wanted to let you know that Nvidia is working on releasing 
the dependencies on Maven Central, and the artifacts are expected to be 
published by the 7th of November.

As soon as the artifacts are published, we will create a PR to revert 
[this|https://github.com/apache/solr/blob/branch_10_0/gradle/globals.gradle#L28-L32].
 Otherwise, if the artifacts are not published by the 7th, we will revert the 
changes associated to adding the cuvs module in Solr.

Thanks

> Switch to maven central for getting the cuVS artifacts
> ------------------------------------------------------
>
>                 Key: SOLR-17938
>                 URL: https://issues.apache.org/jira/browse/SOLR-17938
>             Project: Solr
>          Issue Type: Task
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Puneet Ahuja
>            Assignee: Ishan Chattopadhyaya
>            Priority: Blocker
>             Fix For: 10.0
>
>
> As mentioned in SOLR-17892  
> [cuVS-Lucene|https://github.com/rapidsai/cuvs-lucene] is a new NVIDIA project 
> that integrates GPU acceleration into Lucene for vector search. At present, 
> artifacts are not yet published on Maven Central, and use Searchscale's Maven 
> repository.
> This issue proposes that we should switch to getting the artifacts from Maven 
> central. If the artifacts are not published to Maven central, we would need 
> to entirely remove this cuVS module from Solr so release is not affected.
> cuVS 25.10 is supposed to be released (and artifacts available on Maven 
> Central) by 9 October 2025 as mentioned here: 
> https://docs.rapids.ai/maintainers/



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to