[
https://issues.apache.org/jira/browse/SOLR-18197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18094997#comment-18094997
]
ASF subversion and git services commented on SOLR-18197:
--------------------------------------------------------
Commit 83422bbb870f404daf7651c8201d20d3b2ecf360 in solr's branch
refs/heads/main from Abhishek Umarjikar
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=83422bbb870 ]
SOLR-18197: Add root document query shortcut support to NestPathField (#4512)
Querying root (top-level) documents no longer requires the verbose
existence-negation idiom:
Before: fq=*:* -_nest_path_:*
After: fq=_nest_path_:\/
NestPathField now extends StrField instead of SortableTextField/CustomAnalyzer.
Lucene's query parser bypasses getFieldQuery() for "tokenized" field; switching
to an untokenized StrField fixed it. It's also simpler. The field is now a
bit more strict about misconfiguration that was previously allowed. It doesn't
support stored=true anymore but it's not needed anyway.
> Query _nest_path_ (NestPathField) ease-of-use
> ---------------------------------------------
>
> Key: SOLR-18197
> URL: https://issues.apache.org/jira/browse/SOLR-18197
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: David Smiley
> Priority: Major
> Labels: newdev, pull-request-available
> Time Spent: 4h 40m
> Remaining Estimate: 0h
>
> The {{\_nest\_path\_}} / {{NestPathField}} could use some ease-of-use
> affordances, particularly for when searching for root documents. Thanks to
> the ways that the FieldType gets plugged into query parsers (especially
> FieldType.getFieldQuery), we should be able to override that method so that
> we support the following query:
> {noformat}
> {!field f=_nest_path_ v=/}{noformat}
> As equivalent to today:
> {noformat}
> (*:* -{!prefix f=_nest_path_ v=/}){noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
