lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikolay Martynov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-11792) tvrh component doesn't work if unique key has stored="false"
Date Fri, 22 Dec 2017 19:33:00 GMT

     [ https://issues.apache.org/jira/browse/SOLR-11792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Nikolay Martynov updated SOLR-11792:
------------------------------------
    Summary: tvrh component doesn't work if unique key has stored="false"  (was: tvrh component
requires unique key to be stored and doesn't work with docValues)

> tvrh component doesn't work if unique key has stored="false"
> ------------------------------------------------------------
>
>                 Key: SOLR-11792
>                 URL: https://issues.apache.org/jira/browse/SOLR-11792
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6.2
>            Reporter: Nikolay Martynov
>
> If I create index with unique key defined like
> {code}
> <field name="uid" type="string" indexed="true" stored="false" required="true" docValues="true"/>
> {code}
> then searches seem to be working, but {{tvrh}} doesn't return any vectors for fields
that have one stored.
> Upon a cursory look at the code it looks like {{tvrh}} component requires unique key
to be specifically stored.
> Ideally {{tvrh}} should work fine with docValues. And at the very least this gotcha should
be documented, probably here: https://lucene.apache.org/solr/guide/6_6/field-properties-by-use-case.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message