Jochen Barth created SOLR-13267:
-----------------------------------
Summary: complex {!graph query: NullPointerException
Key: SOLR-13267
URL: https://issues.apache.org/jira/browse/SOLR-13267
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 7.7
Reporter: Jochen Barth
this query leads to NullPointerException:
(\{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:phoron
AND \{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:terrae)
AND NOT (\{!graph from=id to=parent_ids returnRoot=false}
(\{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:phoron AND
{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:terrae))
It is essentially the query
X = \{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:phoron
AND \{!graph from=id to=parent_ids}fulltext_ocr_txtlarge:terrae
(X) AND NOT (\{!graph from=id to=parent_ids returnRoot=false}(X))
parent_ids is a multiValued string docValue-Field; fulltext_ocr_txtlarge is
essentially like the *_txt field.
Use case is: hierarchical solr-docs, think book, chapter, subchapter etc. Each
containing fulltext_ocr_txtlarge with the fulltext of this element only. So
higher level elements (e. g. book) does not contain the fulltext of lower level
elements (e. g. chapters).
The query X delivers all chapters with both words, but of course higher level
elements, too, because the whole book has always more text than single chapters.
the »AND NOT ({!graph ... « part is to filter out the unecessary results, like
»book« if a chapter already matches.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
