ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yury Gerzhedovich (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-9274) Pass transaction label to cache events
Date Tue, 04 Sep 2018 15:18:00 GMT

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

Yury Gerzhedovich commented on IGNITE-9274:
-------------------------------------------

[~vozerov], TC run has been successfully done - [https://ci.ignite.apache.org/viewLog.html?buildId=1792649&]

> Pass transaction label to cache events
> --------------------------------------
>
>                 Key: IGNITE-9274
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9274
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Vladimir Ozerov
>            Assignee: Yury Gerzhedovich
>            Priority: Major
>             Fix For: 2.7
>
>
> It is possible to set transaction label - \{{IgniteTransactions.withLabel}}. We need
to pass this label to related cache and transaction events:
> 1) EVT_TX_STARTED, EVT_TX_COMMITTED, EVT_TX_ROLLED_BACK, EVT_TX_SUSPENDED, EVT_TX_RESUMED
> 2) EVT_CACHE_OBJECT_READ, EVT_CACHE_OBJECT_PUT, EVT_CACHE_OBJECT_REMOVED
> For TX events most probably everything is already passed (see  \{{TransactionStateChangedEvent}}),
we only need to add tests.
> For put/remove events we need to investigate correct messages to pass label, prepare
requests appear to be good candidates for this.
> For read operation we may need to add pass label to get/lock requests ({{GridNearLockRequest}},
{{GridNearGetRequest}}, {{GridNearSingleGetRequest}}).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message