[
https://issues.apache.org/jira/browse/SOLR-10845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16092348#comment-16092348
]
Hoss Man commented on SOLR-10845:
---------------------------------
As noted in SOLR-11093, yonik and i both got confused by the diff between...
* GraphQParserPlugin (aka {{q={!graph from=node_s to=edge_s\}bar}})
* GraphTermsQParserPlugin (aka {{q={!graphTerms f=field1
maxDocFreq=1000\}term1,term2}})
This issue is about GraphTermsQParserPlugin, and I suspect by it's very nature
it will never be able to support points, and should always give an error for
fields which are not TermEnum based {{(isPointField() || indexed="false")}}
> GraphTermsQParserPlugin doesn't work with Point fields (or DocValues only
> fields?)
> ----------------------------------------------------------------------------------
>
> Key: SOLR-10845
> URL: https://issues.apache.org/jira/browse/SOLR-10845
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Hoss Man
> Assignee: Yonik Seeley
>
> GraphTermsQParserPlugin (aka {{graphTerms}}) doesn't work if the {{f}} field
> being used to build the graph is "Points" based (because the field won't have
> any {{Terms}})
> GraphTermsQParserPlugin should either be enhanced to work correctly with
> Points based fields, or should give a clear error if the {{isPointsField()}}
> returns true for the field type being used. At present, it silently matches
> no documents.
> (Note: It appears at first glance that the same basic problem probably exists
> for any trie/string field which is {{docValues="true" indexed="false}} ?)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
