Chris M. Hostetter created SOLR-18134:
-----------------------------------------
Summary: ancestor_path field type no longer works; Solr-10 upgrade
notes suggested change also does not work
Key: SOLR-18134
URL: https://issues.apache.org/jira/browse/SOLR-18134
Project: Solr
Issue Type: Bug
Affects Versions: 10.0
Reporter: Chris M. Hostetter
While trying the Solr-10.0.0 RCs, and reviewing the
{{major-changes-in-solr-10.adoc}} I noticed this commit made a while back as
part of SOLR-17631 ...
[https://github.com/apache/solr/commit/0f4cd0f846c]
* The test changes (both to the test configs and java test code) convert
{{testAncestors()}} into a test of _descendant_ behavior – not _ancestor_
behavior
** this problem is also reflected in the suggested configuration change in
{{major-changes-in-solr-10.adoc}} (it's not going to work for finding
"ancestors", no matter what type of query you send)
* The {{_default}} schema still uses the "old" configuration
** But the underlying lucene functionality for "ancestor path" type use cases
appears (AFAICT) to be fundamentally broken in Lucene > 10.0:
[#15769|https://github.com/apache/lucene/issues/15769] (unless maybe you write
a custom query parser)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
