incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <>
Subject [jira] [Commented] (BLUR-165) Allow columns to be added dynamically
Date Thu, 27 Jun 2013 11:20:20 GMT


Aaron McCurry commented on BLUR-165:

So for the addColumnDefinition(family,name,type,analyzer,fulltext) call, there should probably
be another param subname addColumnDefinition(family,name,subname,type,analyzer,fulltext).
 Subfields are used to index the data a different way without storing the fields more than
once.  There are also going to be some rules about what's allowed.

- Family and name can not be null.
- If the type is NOT Text then analyzer has to be null.
- If the subname is filled in, there has to be a field Family + name column already defined
- And if it's a subfield then fulltext has to be false


> Allow columns to be added dynamically
> -------------------------------------
>                 Key: BLUR-165
>                 URL:
>             Project: Apache Blur
>          Issue Type: Sub-task
>    Affects Versions: 0.2.0, 0.3.0
>            Reporter: Rahul Challapalli
>             Fix For: 0.3.0
> Modify Column struct to add type and once defined we should not allow updates for existing
column definitions
> Make changes to the way analyzer is stored in zookeeper 
> From an external api (Thrift), I would think we would need a method that looks like "addColumnDefinition(family,name,type,analyzer,fulltext)"
or something like that
> Update ZkCacheMap and store the new column definition in zookeeper

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:

View raw message