lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Rowe (JIRA)" <>
Subject [jira] [Commented] (SOLR-10845) GraphTermsQParserPlugin doesn't work with Point fields (or DocValues only fields?)
Date Tue, 01 Aug 2017 17:10:00 GMT


Steve Rowe commented on SOLR-10845:

My Jenkins found a reproducing branch_7x seed for a {{QueryEqualityTest}} failure (reproduces
for me on master) - this seed does not fail on the commit prior to the master commit on this

  [junit4]   2> NOTE: reproduce with: ant test  -Dtestcase=QueryEqualityTest -Dtests.method=testGraphTermsQuery
-Dtests.seed=C529FBFC60B56D6B -Dtests.slow=true -Dtests.locale=mt-MT -Dtests.timezone=BST
-Dtests.asserts=true -Dtests.file.encoding=UTF-8
   [junit4] ERROR   0.01s J6  | QueryEqualityTest.testGraphTermsQuery <<<
   [junit4]    > Throwable #1: org.apache.solr.common.SolrException: undefined field: "field1"
   [junit4]    > 	at __randomizedtesting.SeedInfo.seed([C529FBFC60B56D6B:6BDFA5079C41A1F7]:0)
   [junit4]    > 	at org.apache.solr.schema.IndexSchema.getField(
   [junit4]    > 	at$1.parse(
   [junit4]    > 	at
   [junit4]    > 	at
   [junit4]    > 	at

> GraphTermsQParserPlugin doesn't work with Point fields (or DocValues only fields?)
> ----------------------------------------------------------------------------------
>                 Key: SOLR-10845
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message