cheng66551 opened a new pull request, #14163:
URL: https://github.com/apache/lucene/pull/14163
In version 7.6.0 of ElasticSearch, I found through /_cat/segments that the
docs.deleted count of many segments was continuously increasing, but over time,
**these deleted documents were never auto
cheng66551 closed pull request #14162: feat: Added the method
`forceMergeBySegmentNames` in IW, which suppor…
URL: https://github.com/apache/lucene/pull/14162
--
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
cheng66551 opened a new pull request, #14162:
URL: https://github.com/apache/lucene/pull/14162
In version 7.6.0 of ElasticSearch, I found through /_cat/segments that the
docs.deleted count of many segments was continuously increasing, but over time,
**these deleted documents were never auto
jhinch-at-atlassian-com opened a new issue, #14161:
URL: https://github.com/apache/lucene/issues/14161
### Description
PointInSetQuery in its constructor will check if the values provided to it
are in order and if not will attempt to throw an exception:
```
throw n
mkhludnev commented on code in PR #13974:
URL: https://github.com/apache/lucene/pull/13974#discussion_r1926069638
##
lucene/sandbox/src/java/org/apache/lucene/sandbox/search/SortedSetMultiRangeQuery.java:
##
@@ -0,0 +1,300 @@
+/*
+ * Licensed to the Apache Software Foundation (A
vigyasharma commented on issue #13387:
URL: https://github.com/apache/lucene/issues/13387#issuecomment-2608302325
> Having a Multi-Reader on all the child log-group directories still won't
provide a unified view of all group level segments associated with a Lucene
Index. Even now, OpenSearc
benwtrent opened a new pull request, #14160:
URL: https://github.com/apache/lucene/pull/14160
This is a continuation and completion of the work started by @benchaplin in
https://github.com/apache/lucene/pull/14085
The algorithm is fairly simple:
- Only score and then explore v
rmuir commented on code in PR #77:
URL: https://github.com/apache/lucene-site/pull/77#discussion_r1925577292
##
content/pages/privacy.md:
##
@@ -1,7 +0,0 @@
-Title: Privacy Policy
-URL: privacy.html
-save_as: privacy.html
-template: lucene/tlp/page
-
Review Comment:
personal
jpountz commented on PR #14154:
URL: https://github.com/apache/lucene/pull/14154#issuecomment-2607429171
I don't like that `CompletionAnalyzer` needs to track a thread-local, the
point of reuse strategy is to avoid this kind of thing. Also I'm not sure I
understand why `CompletionAnalyzer`
jpountz commented on PR #14156:
URL: https://github.com/apache/lucene/pull/14156#issuecomment-2607399239
> Seems we just trade an isLoaded for an madvise on systems with enough
memory?
This is correct. I made this suggestion because it was similar to your
initial proposal: skipping t
original-brownbear commented on PR #14156:
URL: https://github.com/apache/lucene/pull/14156#issuecomment-2607332400
@jpountz I see. Hmm I wonder how much that saves us? Seems we just trade an
`isLoaded` for an `madvise` on systems with enough memory? That said, maybe the
`madvise` is far c
benwtrent commented on code in PR #14154:
URL: https://github.com/apache/lucene/pull/14154#discussion_r1925341296
##
lucene/suggest/src/java/org/apache/lucene/search/suggest/document/CompletionAnalyzer.java:
##
@@ -112,6 +116,25 @@ public CompletionAnalyzer(
Concatenate
msokolov merged PR #14157:
URL: https://github.com/apache/lucene/pull/14157
--
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.ap
benwtrent merged PR #14147:
URL: https://github.com/apache/lucene/pull/14147
--
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.a
gmarsay commented on PR #13343:
URL: https://github.com/apache/lucene/pull/13343#issuecomment-2607247416
I also noticed a performance issue, maybe related to this topic?
I have an index that contains data from a metricbeat agent (1 shard + 1
replica; 18G).
When performing a search
benwtrent commented on code in PR #14147:
URL: https://github.com/apache/lucene/pull/14147#discussion_r1925317415
##
lucene/core/src/java/org/apache/lucene/search/knn/MultiLeafKnnCollector.java:
##
@@ -77,6 +76,7 @@ public MultiLeafKnnCollector(
int interval,
Block
jpountz commented on issue #14148:
URL: https://github.com/apache/lucene/issues/14148#issuecomment-2607239803
Intuitively, I had thought of the "throttle at start" approach, where we
would also give `MS` the ability to filter out some merges from `MP` (so that
they don't get registered to t
benwtrent closed issue #14149: TestManyKnnDocs is broken
URL: https://github.com/apache/lucene/issues/14149
--
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-ma
mikemccand commented on issue #14148:
URL: https://github.com/apache/lucene/issues/14148#issuecomment-2607224591
Doing this in `MergeScheduler` (`MS`) is indeed another option. It'd mean
you could cap replication bandwidth independent of your `MergePolicy` (`MP`).
`MS` could even fine-tun
benwtrent merged PR #14158:
URL: https://github.com/apache/lucene/pull/14158
--
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.a
jpountz commented on PR #14156:
URL: https://github.com/apache/lucene/pull/14156#issuecomment-2607163688
Well, you may be right as well that the cost of `MS::isLoaded` is of a
similar order of magnitude as `madvise`. What the current logic does is that if
you get `MS::isLoaded` to frequentl
iverase commented on PR #14157:
URL: https://github.com/apache/lucene/pull/14157#issuecomment-2607140645
Sounds good to me @msokolov, I didn't like to add yet a new parameter in
the search api. Thanks for taking the time to review it.
--
This is an automated message from the Apache Git
iverase closed pull request #14159: Prevent choosing connection nodes that are
already neighbours
URL: https://github.com/apache/lucene/pull/14159
--
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
msokolov commented on PR #14157:
URL: https://github.com/apache/lucene/pull/14157#issuecomment-2607133416
@iverase I see what you did there ... that would also solve this problem,
but I think it is less desirable since it (1) requires extending the HNSW
search API in a way I think we wouldn
original-brownbear commented on PR #14156:
URL: https://github.com/apache/lucene/pull/14156#issuecomment-2607056900
@jpountz
> was introduced had a benchmark that demonstrated an improvement with the
current logic
Huh those results are quite unexpected I must admit :) When me
msokolov merged PR #12828:
URL: https://github.com/apache/lucene/pull/12828
--
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.ap
msokolov commented on issue #5771:
URL: https://github.com/apache/lucene/issues/5771#issuecomment-2607027055
Thanks for pointing that out
--
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 speci
msokolov closed issue #5771: Tool to recover data from .fdt files [LUCENE-4706]
URL: https://github.com/apache/lucene/issues/5771
--
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.
cpoerschke commented on code in PR #77:
URL: https://github.com/apache/lucene-site/pull/77#discussion_r1925064849
##
content/pages/privacy.md:
##
@@ -1,7 +0,0 @@
-Title: Privacy Policy
-URL: privacy.html
-save_as: privacy.html
-template: lucene/tlp/page
-
Review Comment:
Alt
cpoerschke opened a new pull request, #77:
URL: https://github.com/apache/lucene-site/pull/77
The "Apache Project Website Checks" at
https://whimsy.apache.org/site/project/lucene identify
```
Privacy | https://lucene.apache.org/privacy.html | URL expected to match
regular expr
30 matches
Mail list logo
