[jira] Commented: (SOLR-1270) Legacy Numeric Field types need to be more consistent in their input/output error checking & documentation

["Hoss Man (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739118#action_12739118 ] 

Hoss Man commented on SOLR-1270:
--------------------------------

FYI: since 1.3 was released, the usages of FloatField (and it's ilk) in the example schema have already been largely removed.  So i think the big issue here is just making the behavior of the legacy classes consistent, and improving their javadocs.

Donovan/Matt: FloatField (and it's ilk) is still listed in the example schema.xml on the trunk, it's just no longer used in any of the example fields -- so if you think there are improvements to be made to the comments associate with those field types, please give a specific example of how you think it should be documented.

> 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.