[
https://issues.apache.org/jira/browse/OMID-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16499422#comment-16499422
]
ASF GitHub Bot commented on OMID-72:
------------------------------------
GitHub user ohadshacham opened a pull request:
https://github.com/apache/incubator-omid/pull/36
[OMID-72] bug fix, accessed tables should be sent to transaction mana…
…ger also for conflict free writes. This is because fences should also
force conflict free transactions to abort.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ohadshacham/incubator-omid OMID-72-bug
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-omid/pull/36.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 #36
----
commit d96ff96e4fa264472ae684bdb1834e791a6d25ef
Author: Ohad Shacham <ohads@...>
Date: 2018-06-03T13:41:45Z
[OMID-72] bug fix, accessed tables should be sent to transaction manager
also for conflict free writes. This is because fences should also force
conflict free transactions to abort.
----
> Add fences to support secondary index in Phoenix
> ------------------------------------------------
>
> Key: OMID-72
> URL: https://issues.apache.org/jira/browse/OMID-72
> Project: Apache Omid
> Issue Type: Sub-task
> Reporter: Ohad Shacham
> Assignee: Ohad Shacham
> Priority: Major
>
> Add support for fences over a table. These fences guarantee that every
> transaction started before the fence and writes to the table the fence was
> created for will be aborted.
> These fences are needed for creating a secondary index in Apache Phoenix. The
> scenario was discussed in [TEPHRA-157] and [PHOENIX-2478]. Augmenting Omid
> with this kind of transactions was also discussed in [OMID-56].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
