[
https://issues.apache.org/jira/browse/SOLR-17917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18028868#comment-18028868
]
Ishan Chattopadhyaya edited comment on SOLR-17917 at 10/9/25 7:31 PM:
----------------------------------------------------------------------
> This is a seriously fucked up situation:
> https://github.com/apache/solr/pull/3731
Ah, I missed that.
> ...how did the checksums on the cuvs jars change?????
Yes, that's because cuvs jars are coming from a snapshots maven repository, not
a release repository. cuVS-Lucene is pre-release software at this point.
Want to switch to Maven Central based artifacts, which will be stable:
https://issues.apache.org/jira/browse/SOLR-17938.
I'll check on the status of the cuVS release (I guess it is in the process of
releasing) and fix this mess.
was (Author: ichattopadhyaya):
> This is a seriously fucked up situation:
> https://github.com/apache/solr/pull/3731
Ah, I missed that.
> ...how did the checksums on the cuvs jars change?????
Yes, that's because cuvs jars are coming from a snapshots maven repository, not
a release repository. cuVS is pre-release software at this point.
Want to switch to Maven Central based artifacts, which will be stable:
https://issues.apache.org/jira/browse/SOLR-17938.
I'll check on the status of the cuVS release (I guess it is in the process of
releasing) and fix this mess.
> Upgrade to Lucene 10.3
> ----------------------
>
> Key: SOLR-17917
> URL: https://issues.apache.org/jira/browse/SOLR-17917
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Major
> Labels: pull-request-available
> Fix For: main (10.0)
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Lucene 10.3 is releasing shortly. I think we should upgrade to it before our
> Solr 10.0 release. WDYT, [~anshum]?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
