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

Mithun Radhakrishnan commented on SOLR-17938:
---------------------------------------------

> This PR is created to revert the module in case Nvidia is not able to publish 
> the dependencies to Maven Central by tomorrow

About that:  The `cuvs-lucene` artifacts should now be available from Maven 
Central:
https://mvnrepository.com/artifact/com.nvidia.cuvs.lucene/cuvs-lucene
Also:  
https://repo.maven.apache.org/maven2/com/nvidia/cuvs/lucene/cuvs-lucene/25.10.0/

> 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
>              Labels: pull-request-available
>             Fix For: 10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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