[jira] [Updated] (KUDU-430) Consistent Operations
[ https://issues.apache.org/jira/browse/KUDU-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Henke updated KUDU-430: - Target Version/s: 1.8.0 (was: 1.5.0) > Consistent Operations > - > > 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 >Assignee: David Alves >Priority: Major > Labels: kudu-roadmap > > This ticket tracks consistency/isolation work for 1.2. > Scope Doc: > https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# > The sub-tasks that don't target 1.2 will likely be moved somewhere else, or > promoted to tasks once this ticket is done, but for now it's handy to have a > single view of all the remaining work -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (KUDU-430) Consistent Operations
[ https://issues.apache.org/jira/browse/KUDU-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Alves updated KUDU-430: - Description: This ticket tracks consistency/isolation work for 1.2. Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# The sub-tasks that don't target 1.2 will likely be moved somewhere else, or promoted to tasks once this ticket is done, but for now it's handy to have a single view of all the remaining work was: This ticket tracks consistency/isolation work for GA. Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# The sub-tasks that don't target GA will likely be moved somewhere else, or promoted to tasks once this ticket is done, but for now it's handy to have a single view of all the remaining work > Consistent Operations > - > > 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 >Assignee: David Alves > Labels: kudu-roadmap > > This ticket tracks consistency/isolation work for 1.2. > Scope Doc: > https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# > The sub-tasks that don't target 1.2 will likely be moved somewhere else, or > promoted to tasks once this ticket is done, but for now it's handy to have a > single view of all the remaining work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KUDU-430) Consistent Operations
[ https://issues.apache.org/jira/browse/KUDU-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Alves updated KUDU-430: - Description: This ticket tracks consistency/isolation work for GA. Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# The sub-tasks that don't target GA will likely be moved somewhere else, or promoted to tasks once this ticket is done, but for now it's handy to have a single view of all the remaining work was: 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 Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# > Consistent Operations > - > > 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 >Assignee: David Alves > Labels: kudu-roadmap > > This ticket tracks consistency/isolation work for GA. > Scope Doc: > https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# > The sub-tasks that don't target GA will likely be moved somewhere else, or > promoted to tasks once this ticket is done, but for now it's handy to have a > single view of all the remaining work -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KUDU-430) Consistent Operations
[ https://issues.apache.org/jira/browse/KUDU-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Alves updated KUDU-430: - Description: 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 Scope Doc: https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# was: 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 > Consistent Operations > - > > 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 > Scope Doc: > https://docs.google.com/document/d/1EaKlJyQdMBz6G-Xn5uktY-d_x0uRmjMCrDGP5rZ7AoI/edit# -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (KUDU-430) Consistent Operations
[ https://issues.apache.org/jira/browse/KUDU-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Alves updated KUDU-430: - Summary: Consistent Operations (was: Full support for snapshot consistency) > Consistent Operations > - > > 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)
