[
https://issues.apache.org/jira/browse/SOLR-1754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829769#action_12829769
]
Hoss Man commented on SOLR-1754:
--------------------------------
The reason we never explicitly tested the input value was for speed -- if the
user says it's an int we trust them. The only places any FieldTypes explicitly
validate the input strings (ie: SortableIntField, DateField, etc..) is when
they get it free as a side effect of conversion (in DateField's case: even
though we index the raw string, we have to parse it anyway looking for DateMath)
Is there really any memory efficiency from IntField that can't be achieved with
an appropriate precisionStep on TrieIntField?
> Legacy numeric types do not check input for bad syntax
> ------------------------------------------------------
>
> Key: SOLR-1754
> URL: https://issues.apache.org/jira/browse/SOLR-1754
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Lance Norskog
> Fix For: 1.5
>
>
> The legacy numeric types do not check their input values for valid input. A
> text string is accepted as input for any of these types: IntField, LongField,
> FloatField, DoubleField. DateField checks its input.
> In general this is a no-fix, except: that IntField is a necessary memory type
> because it cuts memory use in sorting.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
