incubator-blur-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron McCurry (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (BLUR-59) During table creation re-read the field types from the index.
Date Sun, 31 May 2015 18:08:17 GMT

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

Aaron McCurry closed BLUR-59.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 0.2.4
         Assignee: Aaron McCurry

This has been resolved for awhile.

> During table creation re-read the field types from the index.
> -------------------------------------------------------------
>
>                 Key: BLUR-59
>                 URL: https://issues.apache.org/jira/browse/BLUR-59
>             Project: Apache Blur
>          Issue Type: Bug
>            Reporter: Aaron McCurry
>            Assignee: Aaron McCurry
>             Fix For: 0.2.4
>
>
> Currently in ZooKeeper blur stores the fields and their types so that no 2 shards can
have the same field name with different types.  However if the table is dropped but the indexes
are saved (i.e. Not deleted).  Then the table is re-created referencing the same indexes the
field types will be lost.
> There are several ways to solve this issue, however this brings a larger issue up.  The
fact that meta-data about the index and the indexes themselves are stored in 2 different locations.
 Perhaps the right solution would be to move all the meta-data about the table and the indexes
to the storage location and remove it from ZooKeeper.  That way the meta-data and the data
can be kept in sync more easily.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message