You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2018/01/05 21:39:00 UTC
[jira] [Commented] (IGNITE-7250) Apache Ignite Transactional
Subsystem Architecture
[ https://issues.apache.org/jira/browse/IGNITE-7250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313944#comment-16313944 ]
Denis Magda commented on IGNITE-7250:
-------------------------------------
Moved the information to Ignite wiki:
https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+Architecture
No reason to update the existing Ignite readme.io documentation that should stay a little bit more high-level.
[~abchaudhri], as discussed, please edit the wiki page and make out several blog posts on the matter:
* 2-phase commit in Ignite
* Failure resolution
* Transactions handling when Ignite persistence is enabled (this topic is not covered on the wiki, feel free to put it there once you finish the blog)
> Apache Ignite Transactional Subsystem Architecture
> --------------------------------------------------
>
> Key: IGNITE-7250
> URL: https://issues.apache.org/jira/browse/IGNITE-7250
> Project: Ignite
> Issue Type: Task
> Components: documentation
> Reporter: Denis Magda
> Assignee: Denis Magda
> Fix For: 2.4
>
> Attachments: Apache Ignite Transactions Architecture Eng 0.2.pdf, Apache Ignite Transactions Architecture Eng 0.4.pdf, Apache Ignite Transactions Architecture Rus 0.2.pdf, Apache Ignite Transactions Architecture Rus 0.4.pdf
>
>
> A couple of community members prepared a well-defined document about Ignite transactions architecture. See the PDF version attached.
> Use this document to enrich the existing page on Ignite transactions. Even more, it makes sense to define a unique category for transactions and create several pages.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)