[
https://issues.apache.org/jira/browse/SOLR-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739123#action_12739123
]
Hoss Man commented on SOLR-1270:
--------------------------------
sorry, one last comment i forgot to mention before...
Yonik: i assigned to you to make the final call about how to make all the
behavior consistent. (i'm guessing based on the inadvertent commit you made to
FloatField that you prefer they all sanity check on output, but i didn't want
to make any assumptions). I'm -0 on any sanity checking, but I do agree they
should be consistent.
> Legacy Numeric Field types need to be more consistent in their input/output
> error checking & documentation
> ----------------------------------------------------------------------------------------------------------
>
> Key: SOLR-1270
> URL: https://issues.apache.org/jira/browse/SOLR-1270
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.2, 1.3, 1.4
> Environment: ubuntu 8.04, sun java 6, tomcat 5.5
> Reporter: Donovan Jimenez
> Assignee: Yonik Seeley
> Priority: Minor
> Fix For: 1.4
>
> Attachments: SOLR-1270.patch
>
>
> FloatField, IntField, ByteField, LongField. and DoubleField have inconsistent
> behavior at response writing time when dealing with "garbage" data in the
> index. the behavior should be standardized, and better documented.
> --
> This issue originally came from my php client issue tracker:
> http://code.google.com/p/solr-php-client/issues/detail?id=13
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
