[
https://issues.apache.org/jira/browse/SOLR-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-1270:
---------------------------
Description:
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
was:
The FloatField field type takes any string value at index. These values aren't
necessarily in JSON numeric, but the JSON writer does not check its validity
before writing it out as a JSON numeric.
I'm aware of the SortableFloatField which does do index time verification and
conversion of the value, but the way the JSON writer is working seemed like
either a bug that needed addressed or perhaps a gotch that needs better
documented?
This issue originally came from my php client issue tracker:
http://code.google.com/p/solr-php-client/issues/detail?id=13
Assignee: Yonik Seeley
Summary: Legacy Numeric Field types need to be more consistent in their
input/output error checking & documentation (was: The FloatField (and probably
others) field type takes any string value at index, but JSON writer outputs as
numeric without checking)
revised issue summarydescription to clarify full scope of issue, assigning to
yonik
> 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.
