dweiss commented on PR #11960:
URL: https://github.com/apache/lucene/pull/11960#issuecomment-1323272071
Sorry if I lost track among all these patches - I thought there would be
user facing changes as well. If there are none - no need to add anything.
--
This is an automated message from t
donnerpeter commented on PR #11960:
URL: https://github.com/apache/lucene/pull/11960#issuecomment-1323273222
There are some, but they're just API additions which should be
backward-compatible.
--
This is an automated message from the Apache Git Service.
To respond to the message, please l
dweiss commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323273394
I wonder if this should be reported to infra though. The fact you can close
an upload repository with top-level artifacts is strange... I wonder what would
happen if you clicked release o
jpountz commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323280633
@dweiss So I did release the staged repository with top-level artifacts, and
Nexus did not give me any errors either. :( After browsing the content, I saw
all the artifacts that I had ex
dweiss commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323295591
Darn. I see them here:
https://repository.apache.org/content/repositories/releases/
But they have not been synced with maven central. I honestly think it's
Nexus that's at blame here
dweiss commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323302321
I filed this question to infra:
https://issues.apache.org/jira/browse/INFRA-23931
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on t
jpountz commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323310172
Thanks Dawid!
--
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 un
stefanvodita closed issue #11814: Support deletes in IndexRearranger
URL: https://github.com/apache/lucene/issues/11814
--
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 unsub
stefanvodita commented on issue #11814:
URL: https://github.com/apache/lucene/issues/11814#issuecomment-1323341662
`IndexRearranger` now supports selecting docs for deletion from the original
index and applying the deletes to the rearranged index.
--
This is an automated message from the
dweiss commented on PR #11947:
URL: https://github.com/apache/lucene/pull/11947#issuecomment-1323346570
Just FYI - Sonatype's nexus wouldn't let you release that staging
repository, I've tried:
 under one or more
jpountz commented on code in PR #11954:
URL: https://github.com/apache/lucene/pull/11954#discussion_r1029194303
##
lucene/core/src/java/org/apache/lucene/index/ExitableDirectoryReader.java:
##
@@ -784,7 +770,10 @@ protected DirectoryReader
doWrapDirectoryReader(DirectoryReader
jpountz commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029197613
##
lucene/core/src/java/org/apache/lucene/document/BinaryRangeFieldRangeQuery.java:
##
@@ -91,7 +92,11 @@ public Query rewrite(IndexSearcher indexSearcher) throws
IOE
jpountz opened a new pull request, #11961:
URL: https://github.com/apache/lucene/pull/11961
This instance is illegal as it reports a number of dimensions equal to zero.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and u
jpountz opened a new pull request, #11962:
URL: https://github.com/apache/lucene/pull/11962
`VectorValues` have a `cost()` method that reports an approximate number of
documents that have a vector, but also a `size()` method that reports the
accurate number of vectors in the field. Since KN
shubhamvishu commented on code in PR #11954:
URL: https://github.com/apache/lucene/pull/11954#discussion_r1029256452
##
lucene/core/src/test/org/apache/lucene/index/TestExitableDirectoryReader.java:
##
@@ -292,7 +296,11 @@ public void testExitablePointValuesIndexReader() throws
jpountz opened a new issue, #11963:
URL: https://github.com/apache/lucene/issues/11963
### Description
Follow-up of
https://github.com/apache/lucene/pull/11860#discussion_r1027106953: the API for
quantization of vectors is a bit surprising at times in that you can index
bytes but th
jpountz commented on code in PR #11860:
URL: https://github.com/apache/lucene/pull/11860#discussion_r1029282728
##
lucene/backward-codecs/src/java/org/apache/lucene/backward_codecs/lucene94/ExpandingVectorValues.java:
##
@@ -0,0 +1,49 @@
+/*
+ * Licensed to the Apache Software F
jpountz commented on code in PR #11954:
URL: https://github.com/apache/lucene/pull/11954#discussion_r1029300137
##
lucene/core/src/java/org/apache/lucene/index/ExitableDirectoryReader.java:
##
@@ -784,7 +770,10 @@ protected DirectoryReader
doWrapDirectoryReader(DirectoryReader
benwtrent commented on issue #11963:
URL: https://github.com/apache/lucene/issues/11963#issuecomment-1323680557
This is a naive question, but is there a design principle I am missing that
makes `VectorValues` out of line?
I don't know how often folks will read the vector values direct
jpountz opened a new pull request, #11964:
URL: https://github.com/apache/lucene/pull/11964
`RandomAccessVectorValues` is internally used in our HNSW implementation to
provide random access to vectors, both at index and search time. In order to
better reflect this, this change does the foll
jpountz commented on issue #11963:
URL: https://github.com/apache/lucene/issues/11963#issuecomment-1323732143
I had not considered generics, I guess it would be an option indeed by
passing the expected vector array class to `getVectorValues` and
`searchNearestNeighbors`.
--
This is an au
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029458836
##
lucene/core/src/test/org/apache/lucene/search/TestRangeFieldsDocValuesQuery.java:
##
@@ -226,4 +228,30 @@ public void testToString() {
Query q4 = LongRangeDoc
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029466354
##
lucene/core/src/java/org/apache/lucene/document/BinaryRangeFieldRangeQuery.java:
##
@@ -91,7 +92,11 @@ public Query rewrite(IndexSearcher indexSearcher) throws
IO
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029470218
##
lucene/core/src/java/org/apache/lucene/document/BinaryRangeFieldRangeQuery.java:
##
@@ -91,7 +92,11 @@ public Query rewrite(IndexSearcher indexSearcher) throws
IO
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029471303
##
lucene/CHANGES.txt:
##
@@ -143,6 +143,9 @@ Bug Fixes
* GITHUB#11907: Fix latent casting bugs in BKDWriter. (Ben Trent)
+* GITHUB#11950: Fix NPE in BinaryRange
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029481972
##
lucene/core/src/java/org/apache/lucene/document/BinaryRangeFieldRangeQuery.java:
##
@@ -91,7 +92,11 @@ public Query rewrite(IndexSearcher indexSearcher) throws
IO
gsmiller commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029494212
##
lucene/CHANGES.txt:
##
@@ -143,6 +143,9 @@ Bug Fixes
* GITHUB#11907: Fix latent casting bugs in BKDWriter. (Ben Trent)
+* GITHUB#11950: Fix NPE in BinaryRange
jpountz commented on code in PR #11950:
URL: https://github.com/apache/lucene/pull/11950#discussion_r1029501693
##
lucene/core/src/java/org/apache/lucene/document/BinaryRangeFieldRangeQuery.java:
##
@@ -91,7 +92,11 @@ public Query rewrite(IndexSearcher indexSearcher) throws
IOE
donnerpeter merged PR #11960:
URL: https://github.com/apache/lucene/pull/11960
--
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
risdenk opened a new pull request, #2675:
URL: https://github.com/apache/lucene-solr/pull/2675
Backport to branch_8_11 for https://issues.apache.org/jira/browse/SOLR-16555
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and us
itygh commented on PR #2675:
URL: https://github.com/apache/lucene-solr/pull/2675#issuecomment-1324112666
这是来自QQ邮箱的假期自动回复邮件。您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
mdmarshmallow commented on code in PR #11958:
URL: https://github.com/apache/lucene/pull/11958#discussion_r1029879211
##
lucene/core/src/java/org/apache/lucene/store/FilterIndexOutput.java:
##
@@ -0,0 +1,113 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one o
rmuir commented on issue #11963:
URL: https://github.com/apache/lucene/issues/11963#issuecomment-1324355332
as i mentioned on the original issue(s) (there were several PRs closed and
opened and many comments were lost...), the problem is right in the title:
quantization.
there should
rmuir commented on issue #11963:
URL: https://github.com/apache/lucene/issues/11963#issuecomment-1324355812
we can break index backwards compatibility to fix this.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
37 matches
Mail list logo
