Mailing-List: contact solr-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-dev@lucene.apache.org
Message-ID: <934387587.51281265320888106.JavaMail.jira@brutus.apache.org>
Date: Thu, 4 Feb 2010 22:01:28 +0000 (UTC)
From: "Yonik Seeley (JIRA)" <jira@apache.org>
To: solr-dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-1754) Legacy numeric types do not check
 input for bad syntax
In-Reply-To: <700471519.28041265260587919.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yonik Seeley commented on SOLR-1754:
------------------------------------

bq. Is there really any memory efficiency from IntField that can't be achieved with an appropriate precisionStep on TrieIntField?

Nope... sorting on both will be equivalent, regardless of what the precisionStep is.


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