[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12662696#action_12662696
]
Hoss Man commented on SOLR-284:
-------------------------------
bq. I put in the code b/c I figured it was better to generate an ID than to
outright reject the document,
Hmmm ... that means that if i have a schema with a uniqueKey field, and i
forget to specify a uniqueKey value when indexing my document, the handler will
"silently succeed" in adding a document with a key i have no control over
instead of failing in a way that will make me aware of my mistake -- and i have
no way of configuring solr to prevent that kind of "silent success"
If i wanted that behavior, i could configure the schema with a UUIDFIeld as the
uniqueKey and take advantage of the default. but as it is now i have no way to
prevent it.
I would think consistency and flexibility is more important, and remove that
"generateId" functionality along the lines of Lance's suggestion.
> Parsing Rich Document Types
> ---------------------------
>
> Key: SOLR-284
> URL: https://issues.apache.org/jira/browse/SOLR-284
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Eric Pugh
> Assignee: Grant Ingersoll
> Fix For: 1.4
>
> Attachments: libs.zip, rich.patch, rich.patch, rich.patch,
> rich.patch, rich.patch, rich.patch, rich.patch, SOLR-284.patch,
> SOLR-284.patch, SOLR-284.patch, SOLR-284.patch, SOLR-284.patch,
> SOLR-284.patch, SOLR-284.patch, solr-word.pdf, source.zip, test-files.zip,
> test-files.zip, test.zip, un-hardcode-id.diff
>
>
> I have developed a RichDocumentRequestHandler based on the CSVRequestHandler
> that supports streaming a PDF, Word, Powerpoint, Excel, or PDF document into
> Solr.
> There is a wiki page with information here:
> http://wiki.apache.org/solr/UpdateRichDocuments
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
