You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/01/23 21:43:39 UTC

[jira] [Updated] (PHOENIX-2092) Support read-your-own-writes semantics without sending updates to server

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

James Taylor updated PHOENIX-2092:
----------------------------------
    Summary: Support read-your-own-writes semantics without sending updates to server  (was: [BRAINSTORMING] Support read-your-own-writes semantics without sending updates to server)

> Support read-your-own-writes semantics without sending updates to server
> ------------------------------------------------------------------------
>
>                 Key: PHOENIX-2092
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2092
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> Our current transaction integration sends uncommitted data to the HBase server when a client attempts to read on a connection with uncommitted data. Instead, we could (in theory) keep the data on the client and treat these local edits as a kind of separate region which would get merged into the results of any queries. Unclear how many cases would be handled, though:
> - partially aggregated results would need to be adjusted (i.e. subtract the sum from an overridden value and add the sum from the new value)
> - secondary index usage - the client would need to know the rows to delete and the rows to add to the index table
> - deleted rows
> Parking this here for now as food for thought.



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