Lucene: Status=Open

[Save this search]

Author relation

Updated ago

Comment count

Reaction count

Review Requested

User

Last comment user

Type

Filters: Status (Open), Issue type, Author relation, Created, Updated, Updated ago, Comment count, Reaction count, Review Requested, Mentioned, Reviewed, Commented, User, Last comment user, Draft, Component, Type, Labels, Commits?, Reporter, Assignee

#16989 PR: Skip registering a doc-values-update field with no applicable update

2.5 minutes ago 1 comments 0 votes 0 watches github-actions[bot], jimczi, kkewwei

When a doc-values update field is new to a segment, ReadersAndUpdates.writeFieldUpdates creates a ... A later merge of that segment then reads a null doc-values producer for the field and throws a ... This happens when an update to a field not yet present in a segment is still buffered while that ...

kkewwei 2.5 minutes ago:

#17003 PR: Don't undelete hard deleted docs when applying soft deletes updates

9.3 hours ago 1 comments 0 votes 0 watches diwu-sf, github-actions[bot], shbhar

Description With soft deletes, setting a document's soft deletes field to no value undeletes it. If the document is hard deleted before that update is written, the soft delete count goes negative, ... To reproduce, with maxBufferedDocs=2 and soft deletes field soft_delete: 1.

shbhar 9.4 hours ago:

Thanks for creating this issue @diwu-sf , this was also found in the AI agent bug hunt: https:// ... The diagrams, repros & tests might be of some help.

#17006 PR: Count soft deletes that aren't written yet in IndexWriter's doc stats

9.3 hours ago 1 comments 0 votes 0 watches diwu-sf, github-actions[bot], shbhar

DescriptionWith soft deletes, IndexWriter#getDocStats().numDocs and IndexWriterhasDeletions() can ... A soft delete or soft update resolved by an auto flush isn't counted. numDocs is too high, and ... A hard delete in the same spot is counted. 2.

shbhar 9.3 hours ago:

Thanks for creating this bug fix PR @diwu-sf, in case the repro, diagrams, tests or suggested fixes ...

#16997: Optimize Support for Negative Queries in Lucene Monitor

12.4 hours ago 0 comments 0 votes 0 watches kotman12

Description It is possible to extend the mechanics of the multi-pass term filtered pre-searcher ( ... Conjunctions of negative queries are especially ripe for this kind of optimization. The main idea is to index these -field:value sub-queries as special terms managed by the ...

#16998 PR: GITHUB#16997 Negative Query Optimizations for Lucene Monitor Presearcher

12.4 hours ago 14 comments 0 votes 0 watches github-actions[bot], kotman12, romseygeek

Description Hey all, I'm a Solr committer and also a frequent user of the lucene-monitor module ... I've had this idea for a while which was greatly inspired by the very clever way that ... The same approach can actually be extended to more optimally handle negative queries.

kotman12 13.2 hours ago:	I explain this in https://github.com/apache/lucene/pull/16998/changes#r4497736806
kotman12 14.8 hours ago:	Multi-doc batches don't work well with this feature as currently implemented. I am not a user of the batch feature but analyzing this PR made me realize that they don't work ... More details here https://github.com/apache/lucene/issues/17004.

#17005: Optimize Support for Range Queries in Lucene Monitor

14.8 hours ago 0 comments 0 votes 0 watches kotman12

Description Elastic's percolator already has support for this. The percolator implementation indexes the lower and upper bounds into special fields and then each ... It may seem less intuitive, but it does have some advantages.

#17004: Batching counteracts multi-pass pre-searcher efficiency

14.8 hours ago 0 comments 0 votes 0 watches kotman12

Description When encoding a _batch_ of documents the monitor effectively flattens the terms so ... Unfortunately, this can work against the main optimization within the multi-pass term filtered ... To give an example consider the query (apple AND pear) with df=field.

«
1
2
3
4
5
»

2,740 issues

[21.6 msec search, 22.6 msec total]