[
https://issues.apache.org/jira/browse/BLUR-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695188#comment-13695188
]
Aaron McCurry commented on BLUR-112:
------------------------------------
As a follow up to the previous comment. I think we should have the
TableContext hold the reference to the FieldManager. Next if figuring out how
to add new types to Blur so that they can be loaded and available to the
FieldManager. Perhaps we should start simple and only read new types from the
blur-site.properties because I don't see adding new field types as an everyday
occurrence.
Another thought I had was to have everything in the TableContext/FieldManager
(basically all the metadata about the table) only or also stored in HDFS. The
reasoning here is that if you disable and remove a table, then go to create (or
maybe a new function "import") a table the previous field and table descriptor
information is gone.
Aaron
> Allow for types to be set on blur tables
> ----------------------------------------
>
> Key: BLUR-112
> URL: https://issues.apache.org/jira/browse/BLUR-112
> Project: Apache Blur
> Issue Type: Improvement
> Affects Versions: 0.2.0, 0.3.0
> Reporter: Aaron McCurry
> Fix For: 0.3.0
>
>
> Create the ability for Blur to handle the default Lucene field types. This
> should not be tied to the table descriptor because types should be allowed to
> be added at runtime. Also 2 new fields should be added to the
> TableDescriptor:
> 1. A strict types attribute. If set to true, if a new column is added to the
> table and there is no type mapping for it. Throw an exception. Set to false
> by default.
> 2. Default type is strict is set to false. The default type should be text.
> Also, dynamic columns could be allowed if their name included the type. Such
> as:
> The column name could be "col1" with a type of "int", in the Column struct in
> thrift the name would be "col1/int" and if the type did not exist before the
> call it would be added.
> Thoughts?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
