[jira] [Commented] (KUDU-430) Full support for snapshot consistency

["Mike Percy (JIRA)" <ji...@apache.org>]

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

Mike Percy commented on KUDU-430:
---------------------------------

This JIRA is orthogonal to KUDU-1497 but they complement each other.

> Full support for snapshot consistency
> -------------------------------------
>
>                 Key: KUDU-430
>                 URL: https://issues.apache.org/jira/browse/KUDU-430
>             Project: Kudu
>          Issue Type: New Feature
>          Components: client, tablet, tserver
>    Affects Versions: M4
>            Reporter: Todd Lipcon
>              Labels: kudu-roadmap
>
> A number of small subtasks remain before we fully support snapshot consistency.
> In particular, a few of the issues:
> - right now, after compactions, we can lose history for a given row, and then a snapshot read in the past wouldn't produce correct results.
> - the C++ client doesn't handle timestamp propagation
> - we need to evaluate and make sure all of our APIs are in good shape in both Java and C++ clients
> - need to add some security (hashes) around timestamp propagation to prevent malicious clients from mucking with our machinery



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