[
https://issues.apache.org/jira/browse/SOLR-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-308:
-----------------------------
Assignee: Hoss Man
Thomas: I understand you concerns, but in the balance of performance vs safety
Solr tends to err on the side of performance when dealing with indexing data --
since that comes from a finite number of controlled sources (you may get it
from dozens of places, but *you* must trust them at least a little and have the
chance to sanitize their data before deciding to use it) while query inputs are
treaty much more delicately since they typically come from much more diverse
group of users many of whom you may outright distrust.
that said, i went ahead and left in the remaining validation you had, although
i had to replace the isEmpty() call (Solr still uses Java 1.5)
I also changed the toInternal methods to always lowercase whatever value they
get (the hex values need to be case insensitve in case someone tries to
query/update using a different case then was orriginally indexed)
> Add a field that generates an unique id when you have none in your data to
> index
> --------------------------------------------------------------------------------
>
> Key: SOLR-308
> URL: https://issues.apache.org/jira/browse/SOLR-308
> Project: Solr
> Issue Type: New Feature
> Components: search
> Reporter: Thomas Peuss
> Assignee: Hoss Man
> Priority: Minor
> Attachments: UUIDField.patch, UUIDField.patch, UUIDField.patch,
> UUIDField.patch, UUIDField.patch
>
>
> This patch adds a field that generates an unique id when you have no unique
> id in your data you want to index.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
