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-435) Create a per table lock for BulkTableUpdateCommand
Date Mon, 22 Jun 2015 13:14:00 GMT

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

Aaron McCurry closed BLUR-435.
------------------------------
    Resolution: Fixed

https://git-wip-us.apache.org/repos/asf?p=incubator-blur.git;a=commit;h=4c8ec52c7cc4a0537bfa3ce10f66d84e7a754da2

> Create a per table lock for BulkTableUpdateCommand
> --------------------------------------------------
>
>                 Key: BLUR-435
>                 URL: https://issues.apache.org/jira/browse/BLUR-435
>             Project: Apache Blur
>          Issue Type: Bug
>          Components: Blur
>            Reporter: Aaron McCurry
>            Assignee: Aaron McCurry
>             Fix For: 0.2.4
>
>
> The BulkTableUpdateCommand updates data in a Blur table by creating a snapshot of the
data and reading from the files in HDFS.  Then in the reduce phase of the MR job the Rows
that are not updated are dropped and the Row that have changes are re-indexed.  If there are
two jobs occurring at the same time and the same Rows are being updated data could be lost.
 So the issue is to create a lock (likely in ZK) per table for the bulk table updates.



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

Mime
View raw message