[
https://issues.apache.org/jira/browse/SOLR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12475700
]
Hoss Man commented on SOLR-172:
-------------------------------
solr is designed so that if you don't specify a <uniqueKey> field in your
schema, then no uniqueness is enforced (just like lucene) the tradeoffs being
that you can't replace a document by readding it, and and you (obviously) can't
delete by id.
i've never used this functionality myself, but i can imagine it might be useful
to some people.
this bug in particular is about the confusing error message when the schema
says there is a uniqueKey, but no value was specified in the add ... if the
schema didn't say there was a uniqueKey - there wouldn't be an error at all
> add doc without uniqueKey field causes NPE
> ------------------------------------------
>
> Key: SOLR-172
> URL: https://issues.apache.org/jira/browse/SOLR-172
> Project: Solr
> Issue Type: Bug
> Reporter: Hoss Man
>
> as mentioned in email by otis...
> SimplePostTool: WARNING: Unexpected response from Solr: '<result
> status="1">java.lang.NullPointerException
> at
> org.apache.solr.schema.FieldType.storedToIndexed(FieldType.java:248)
> at
> org.apache.solr.update.UpdateHandler.getIndexedId(UpdateHandler.java:134)
> at
> org.apache.solr.update.DirectUpdateHandler2.overwriteBoth(DirectUpdateHandler2.java:380)
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
