[
https://issues.apache.org/jira/browse/SOLR-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17199665#comment-17199665
]
David Smiley commented on SOLR-10305:
-------------------------------------
For awhile now, uniqueKey supports docValues=true stored=false. Jan Hacker, if
you can get an exception in this scenario (help explain how to reproduce) then
I'll take a closer look.
uniqueKey is almost always "required" -- must be defined in the schema.
Stored/DocValues is a different matter than having your schema identify which
field is the unique key.
> uniqueKey field store=false will throw null NullPointerException
> ----------------------------------------------------------------
>
> Key: SOLR-10305
> URL: https://issues.apache.org/jira/browse/SOLR-10305
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.3.1
> Reporter: jin jing
> Priority: Major
>
> i found if set uniqueKey store=false ,when insert some index,and query as *:*
> will throw nullPointer:
> java.lang.NullPointerException
> at
> org.apache.solr.handler.component.QueryComponent.mergeIds(QueryComponent.java:1095)
> at
> org.apache.solr.handler.component.QueryComponent.handleRegularResponses(QueryComponent.java:754)
> at
> org.apache.solr.handler.component.QueryComponent.handleResponses(QueryComponent.java:733)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
