On Feb 25, 2007, at 1:19 AM, Erik Hatcher wrote:
I have a hard envisioning a case where a document would be indexed
without a unique identifier. While it
^ time
*can* be done with just Lucene, I've never seen a case where a
unique key wasn't just a great idea but a real necessity.
In other words, I'm fine with Solr enforcing a unique identifier per
document if it helps streamline things. If there isn't a compelling
reason other than this pesky exception handling thing, then when the
schema says there is a unique id and one isn't sent, we send a
logical exception back, not an NPE. No biggie.
Erik
On Feb 24, 2007, at 6:10 PM, Ryan McKinley (JIRA) wrote:
[ https://issues.apache.org/jira/browse/SOLR-172?
page=com.atlassian.jira.plugin.system.issuetabpanels:comment-
tabpanel#action_12475663 ]
Ryan McKinley commented on SOLR-172:
------------------------------------
Is it ever ok to send a document without a unique Key? does/
should solr require a unique key field in the schema?
It seems like not much works properly if one is not specified -
maybe it should be an explicit requirement.
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.
