javanna merged PR #11985:
URL: https://github.com/apache/lucene/pull/11985
--
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.apa
epugh commented on code in PR #976:
URL: https://github.com/apache/lucene-solr/pull/976#discussion_r1035762208
##
solr/core/src/java/org/apache/solr/search/join/XCJFQuery.java:
##
@@ -0,0 +1,380 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * co
v00d00c0de opened a new issue, #11989:
URL: https://github.com/apache/lucene/issues/11989
### Description
_org.apache.lucene.analysis.pattern.PatternReplaceFilter_ supports null
value in 'replacement' parameter which is eventually replaced by an empty
string.
After an upgrade
rmuir closed issue #11989: Null support in
PatternReplaceFilter/PatternReplaceFilterFactory
URL: https://github.com/apache/lucene/issues/11989
--
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 spe
rmuir commented on issue #11989:
URL: https://github.com/apache/lucene/issues/11989#issuecomment-1332052656
Support null 😂
Rejecting null values with NullPointerException is the correct behavior here.
--
This is an automated message from the Apache Git Service.
To respond to the me
romseygeek opened a new pull request, #11990:
URL: https://github.com/apache/lucene/pull/11990
PassageScorer uses a priority queue of size `maxPassages` to keep track of
which highlighted passages are worth returning to the user. Once all
passages have been collected, we go through and
luyuncheng commented on PR #11987:
URL: https://github.com/apache/lucene/pull/11987#issuecomment-1332277159
@rmuir Thanks for the replying this issue, i did some benchmarks:
> better to assign null and create array of the correct size, if it won't be
reused.
LGTM , i assigned n
rmuir commented on PR #11987:
URL: https://github.com/apache/lucene/pull/11987#issuecomment-1332307323
Thanks for running the stored fields benchmark: are you able to report the
retrieval time as well? That's my first concern. Maybe, the
StoredFieldsBenchmark.java needs to be run standalone
luyuncheng commented on PR #11987:
URL: https://github.com/apache/lucene/pull/11987#issuecomment-1332336907
> are you able to report the retrieval time as well?
runStoredFieldsBenchmark.py
|retrieved_time_msec | Baseline | Candidate |
| :---|:: |
rmuir commented on PR #11987:
URL: https://github.com/apache/lucene/pull/11987#issuecomment-1332427293
Thanks, yeah my remaining concern is the non-optimized merge... especially
for those that delete and update documents (as it prevents them from getting
optimized merges).
Alternativ
costin commented on PR #11984:
URL: https://github.com/apache/lucene/pull/11984#issuecomment-1332462998
> LGTM. Can you add a CHANGES entry under 9.5?
Done.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
UR
uschindler commented on PR #11987:
URL: https://github.com/apache/lucene/pull/11987#issuecomment-1332570305
Yes, before we work around all that stuff here, I'd also suggest to remove
those ThreadLocals.
--
This is an automated message from the Apache Git Service.
To respond to the message
navneet1v commented on issue #11752:
URL: https://github.com/apache/lucene/issues/11752#issuecomment-1332600579
Resolving the issue as the code is merged.
--
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 t
navneet1v closed issue #11752: Enable Relate Interface of Shape Doc Values to
be used by clients of Lucene
URL: https://github.com/apache/lucene/issues/11752
--
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 t
navneet1v commented on issue #11827:
URL: https://github.com/apache/lucene/issues/11827#issuecomment-1332603551
@iverase Where are we seeing the degradation? We are seeing the degradation
in K-NN Queries between 9.3 and 9.4 release. I am trying to figure out if there
are other clients of lu
dweiss commented on code in PR #11990:
URL: https://github.com/apache/lucene/pull/11990#discussion_r1036450814
##
lucene/highlighter/src/java/org/apache/lucene/search/matchhighlight/PassageSelector.java:
##
@@ -89,8 +89,9 @@ public List pickBest(
}
// Best passages s
dweiss commented on code in PR #11990:
URL: https://github.com/apache/lucene/pull/11990#discussion_r1036458813
##
lucene/highlighter/src/java/org/apache/lucene/search/matchhighlight/PassageSelector.java:
##
@@ -89,8 +89,9 @@ public List pickBest(
}
// Best passages s
iverase commented on issue #11827:
URL: https://github.com/apache/lucene/issues/11827#issuecomment-124626
@navneet1v this issue was triggered by a regression on a geo query and was
addressed before the release. I have no knowledge of any regression in vector
search.
--
This is an aut
18 matches
Mail list logo