lucy-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marvin Humphrey (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCY-108) Numeric FieldTypes
Date Thu, 10 Jun 2010 04:22:24 GMT

     [ https://issues.apache.org/jira/browse/LUCY-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marvin Humphrey updated LUCY-108:
---------------------------------

    Attachment: numeric_type.patch

In the KinoSearch prototype, NumericType fields can be "stored" and
"sortable"; soon, it will be possible to make them "indexed" as well, though
details such as query parsing have yet to be worked out.

Since search terms in Lucy may be any arbitrary Obj (in contrast to the
text-based Term class in Lucene), it is not necessary to have specialized
NumericRangeQuery classes; an ordinary RangeQuery will do.

{code:none}
    my $price_range_query = Lucy::Search::RangeQuery->new(
        field => 'price',
        lower_term => 0,
        upper_term => 1000,
    );
{code}

Default values for NumericType:

{noformat}
    indexed:       1
    stored:        1
    sortable:      0
{noformat}


> Numeric FieldTypes
> ------------------
>
>                 Key: LUCY-108
>                 URL: https://issues.apache.org/jira/browse/LUCY-108
>             Project: Lucy
>          Issue Type: New Feature
>          Components: Core - Plan
>            Reporter: Marvin Humphrey
>            Assignee: Marvin Humphrey
>         Attachments: numeric_type.patch
>
>
> The NumericType classes are broken into IntType and FloatType branches.  
> The initial hierarchy will include concrete classes Int32Type, Int64Type,
> Float32Type and Float64Type. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message