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

ASF GitHub Bot commented on OMID-78:
------------------------------------

GitHub user ohadshacham opened a pull request:

    https://github.com/apache/incubator-omid/pull/16

    [OMID-78] Identify transaction snapshot at the server

    To identify a transaction's snapshot in scans and gets, Omid reads and 
filters cells at the client side. This filtering requires checking the shadow 
cells and accessing the commit table if needed.
    Doing the filtering at the server side should be more efficient since less 
data is being transferred to the client and also, in some cases, RPCs are being 
saved.
    This feature requires implementing a coprocessor that will do the filtering 
at the server side and returns only the relevant snapshot to the client side.
    
    This feature is also needed to support the integration of Omid with 
Phoenix. This is required since Phoenix has coprocessors that change and 
condence the data returned to the client and therefore, filtering at the client 
side in this case is impossible. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ohadshacham/incubator-omid ServerFiltering

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-omid/pull/16.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #16
    
----
commit 83de11a7e64df7dd71c14f830fa96f8ec1646812
Author: Ohad Shacham <[email protected]>
Date:   2017-10-26T08:36:04Z

    Refactor the code to extract the filtering to a different object.
    The intention of the extraction is to share code between the client and 
server side filtering.

commit d49ff5b10fd4b35a740525e5ea9146e9cba48788
Author: Ohad Shacham <[email protected]>
Date:   2017-10-30T08:55:42Z

    intermediate version

commit d5ea6a23e00b02260f8708172bc505ac4a5c0b1b
Author: Ohad Shacham <[email protected]>
Date:   2017-10-31T10:11:35Z

    Implement get function at the coprocessor

commit 9aa6078a4821ea4e5a1e25e5a2bba2d894a3b055
Author: Ohad Shacham <[email protected]>
Date:   2017-10-31T10:53:33Z

    addition

commit 11e90026749ad2ac667bcd27f3ca48878fc08ec4
Author: Ohad Shacham <[email protected]>
Date:   2017-11-01T13:04:53Z

    Working get with tests

commit 51c887d4ab555318a3e70f83c2760fc0a7e5b1ad
Author: Ohad Shacham <[email protected]>
Date:   2017-11-01T14:32:50Z

    Merge branch 'ServerFiltering' of 
https://github.com/ohadshacham/incubator-omid into ServerFiltering

commit 20077d4bacfb0ec6524c8e70e6355059be432d6f
Author: Ohad Shacham <[email protected]>
Date:   2017-11-07T15:18:10Z

    Working version for hbase0

commit 8246c3c7e97474b7c7fc701c07d312093bb1cb05
Author: Ohad Shacham <[email protected]>
Date:   2017-11-08T09:50:55Z

    Working version for hbase-0 and hbase-1

commit ab2bb7b22535b7fa165d2cc2c0dbacd4c2f28009
Author: Ohad Shacham <[email protected]>
Date:   2017-11-08T11:02:26Z

    Let two mini clusters run concurrently.

----


> Identify transaction snapshot at the server
> -------------------------------------------
>
>                 Key: OMID-78
>                 URL: https://issues.apache.org/jira/browse/OMID-78
>             Project: Apache Omid
>          Issue Type: New Feature
>            Reporter: Ohad Shacham
>            Assignee: Ohad Shacham
>
> To identify a transaction's snapshot in scans and gets, Omid reads and filter 
> cells at the client side. This filtering requires checking the shadow cells 
> and accessing the commit table if needed.
> Doing the filtering at the server side should be more efficient since less 
> data is being transferred to the client and also, in some cases, RPCs are 
> being saved.
> This feature requires implementing a coprocessor that will do the filtering 
> at the server side and returns only the relevant snapshot to the client side.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to