[
https://issues.apache.org/jira/browse/SOLR-10305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17021524#comment-17021524
]
Kevin Risden commented on SOLR-10305:
-------------------------------------
SOLR-3682 says this should fail loudly, but this was fixed in 4.x. I don't see
anything after 5.x in jira that would have changed this behavior.
I know in SOLR-11768 there are cases where if you CHANGE the schema of a
collection after documents are already indexed you can end up in some bad
situations. The ID basically doesn't "exist" as far as the schema and
underlying data says.
> uniqueKey filed 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: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
