You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ryabov Dmitrii (JIRA)" <ji...@apache.org> on 2017/04/04 14:46:41 UTC
[jira] [Commented] (IGNITE-4795) Inherit TransactionException and
update Javadoc
[ https://issues.apache.org/jira/browse/IGNITE-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15955212#comment-15955212 ]
Ryabov Dmitrii commented on IGNITE-4795:
----------------------------------------
[~agura], I made fix, can you look it?
About third item - I have no idea how to describe it more. Is it enough or can you orient me with advice?
About {{TransactionCheckedException}} - Avoid? Do you mean remove it completely?
> Inherit TransactionException and update Javadoc
> -----------------------------------------------
>
> Key: IGNITE-4795
> URL: https://issues.apache.org/jira/browse/IGNITE-4795
> Project: Ignite
> Issue Type: Improvement
> Components: cache, SQL, website
> Affects Versions: 1.8
> Reporter: Alexandr Kuramshin
> Assignee: Ryabov Dmitrii
> Labels: documentation, important
> Fix For: 2.0
>
>
> Understanding transactional behaviour is not clear in Javadoc at this point of time. Even after reading website some doubt remain.
> Proposal.
> 1. Create {{TransactionException}} as the marker of transactional methods and inherit from it all the existed transactional exceptions like {{TransactionTimeoutException}}, {{TransactionRollbackException}}, {{TransactionHeuristicException}}, {{TransactionOptimisticException}}, etc.
> 2. Update all the transactional methods ({{get}}, {{put}}, {{invoke}}, etc) as throwing the base {{TransactionException}}. Comment all the {{IgniteCache}} methods whether they are transactional or not, add {{@see TransactionException}} annotation.
> 3. Make extensive documentation in the header of {{TransactionException}} to get understanding of transactional and non-transactional methods behaviour.
> 4. Update website and Javadoc to clarify the fact that {{put}} value is cached within the transaction and affects successive {{get}}.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)