You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Dawid Weiss (Jira)" <ji...@apache.org> on 2020/07/22 13:14:00 UTC

[jira] [Created] (LUCENE-9439) Matches API should enumerate hit fields that have no positions (no iterator)

Dawid Weiss created LUCENE-9439:
-----------------------------------

             Summary: Matches API should enumerate hit fields that have no positions (no iterator)
                 Key: LUCENE-9439
                 URL: https://issues.apache.org/jira/browse/LUCENE-9439
             Project: Lucene - Core
          Issue Type: Improvement
            Reporter: Dawid Weiss
            Assignee: Dawid Weiss


I have been fiddling with Matches API and it's great. There is one corner case that doesn't work for me though -- queries that affect fields without positions return {{MatchesUtil.MATCH_WITH_NO_TERMS}} but this constant is problematic as it doesn't carry the field name that caused it (returns null).

The associated fromSubMatches combines all these constants into one (or swallows them) which is another problem.

I think it would be more consistent if MATCH_WITH_NO_TERMS was replaced with a true match (carrying field name) returning an empty iterator (or a constant "empty" iterator NO_TERMS).

I have a very compelling use case: I wrote an "auto-highlighter" that runs on top of Matches API and automatically picks up query-relevant fields and snippets. Everything works beautifully except for cases where fields are searchable but don't have any positions (token-like fields).

I can work on a patch but wanted to reach out first - [~romseygeek]?




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org