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-105) FieldType
Date Tue, 08 Jun 2010 03:37:12 GMT

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

Marvin Humphrey updated LUCY-105:
---------------------------------

    Attachment: field_type.patch

> FieldType
> ---------
>
>                 Key: LUCY-105
>                 URL: https://issues.apache.org/jira/browse/LUCY-105
>             Project: Lucy
>          Issue Type: New Feature
>          Components: Core - Plan
>            Reporter: Marvin Humphrey
>            Assignee: Marvin Humphrey
>            Priority: Blocker
>         Attachments: field_type.patch
>
>
> Lucy::Plan::FieldType is an abstract class used to define field traits and
> behaviors.  Unlike Lucene, field definitions apply to the entire index; it is
> not possible to have conflicting definitions across multiple segments.
> The initial FieldType class hierarchy will look like this:
> {code:none}
> Lucy::Plan::FieldType
>     Lucy::Plan::TextType
>     Lucy::Plan::BlobType
>     Lucy::Plan::NumericType
>         Lucy::Plan::IntegerType
>             Lucy::Plan::Int32Type
>             Lucy::Plan::Int64Type
>         Lucy::Plan::FloatType
>             Lucy::Plan::Float32Type
>             Lucy::Plan::Float64Type
> {code}
> FieldTypes get fully serialized as JSON within the Schema file, including
> Similarity objects (for indexed fields) and analyzers (for analyzed TextType
> fields).

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