ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8446) Ability to check and completely fill transactions on creation
Date Thu, 26 Jul 2018 21:07:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558891#comment-16558891

Valentin Kulichenko commented on IGNITE-8446:

[~avinogradov], changes make sense to me, however I would prefer if someone else who is more
knowledgable in cache internal takes a look as well. I'm not 100% sure that {{recordStateChangedEvent}}
is invoked from a correct place and if there are no other places where this should happen.

I have couple usability related comments:
# Message provided for the event is {{null}}. This doesn't look good to me, every event should
have an explanation about what happened.
# {{UnsupportedOperationException}}-s thrown by {{TransactionEventProxyImpl}} should contain
a message describing the limitations.

> Ability to check and completely fill transactions on creation
> -------------------------------------------------------------
>                 Key: IGNITE-8446
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8446
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>             Fix For: 2.7
> Since {{label}} added to {{tx}} at IGNITE-6827 we'd like to have ability to guarantee
it filled. 
> So, we have to add special event fired on {{tx}} creation. 
> This event can be used to provide such guarantee.
> Plan:
> Event EVT_TX_STARTED should be created.
> Tx.label should be recodred as a part of this event.
> Test, checking it's possible to restrict tx creation without filling the meta should
be added.

This message was sent by Atlassian JIRA

View raw message