[ https://issues.apache.org/jira/browse/SOLR-10845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109221#comment-16109221 ]
ASF subversion and git services commented on SOLR-10845: -------------------------------------------------------- Commit de0c6ca29e18afa5ddf6934f1ae26f7b078dba3c in lucene-solr's branch refs/heads/branch_7_0 from [~yo...@apache.org] [ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=de0c6ca ] SOLR-10845: add Points support to graphTerms query > 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 > Priority: Blocker > Labels: numeric-tries-to-points > Fix For: 7.0 > > Attachments: SOLR-10845.patch > > > 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