accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-2574) Define storage data structure for data that needs replication
Date Fri, 28 Mar 2014 01:09:14 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950236#comment-13950236
] 

Josh Elser commented on ACCUMULO-2574:
--------------------------------------

Thinking about this some more -- we can't use a Mutation delete, but will have to serialize
the offset "subtraction" logic into a custom iterator as an actual delete would delete all
Values that the Combiner would want to merge. This iterator could also then know to drop a
K-V when the offset contains some empty offset.

> Define storage data structure for data that needs replication
> -------------------------------------------------------------
>
>                 Key: ACCUMULO-2574
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2574
>             Project: Accumulo
>          Issue Type: Sub-task
>            Reporter: Josh Elser
>             Fix For: 1.7.0
>
>
> We need to track data that needs replication. At a minimum we need to track where the
data came from (to support cycles in the replication graph), optional offsets into the file
that needs replicating (important for WALs to avoid having to wait for a WAL to be closed
before replicating).
> It might make sense to include where the data should be replicated to. Not sure if it
makes sense to do that as late as possible or earlier on.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message