You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucy.apache.org by "Marvin Humphrey (JIRA)" <ji...@apache.org> on 2010/06/08 05:37:12 UTC
[jira] Updated: (LUCY-105) FieldType
[ 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.