You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/06/04 08:51:00 UTC
[jira] [Commented] (IGNITE-13112) CacheEvent#subjectId is always
null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED
[ https://issues.apache.org/jira/browse/IGNITE-13112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17125703#comment-17125703 ]
Ignite TC Bot commented on IGNITE-13112:
----------------------------------------
{panel:title=Branch: [pull/7897/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5361729&buildTypeId=IgniteTests24Java8_RunAll]
> CacheEvent#subjectId is always null for cache events with types EVT_CACHE_STARTED and EVT_CACHE_STOPPED
> -------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-13112
> URL: https://issues.apache.org/jira/browse/IGNITE-13112
> Project: Ignite
> Issue Type: Bug
> Components: cache, security
> Affects Versions: 2.8.1
> Reporter: Denis Garus
> Assignee: Denis Garus
> Priority: Major
> Labels: iep-41
> Time Spent: 10m
> Remaining Estimate: 0h
>
> CacheEvents with types EVT_CACHE_STARTED and EVT_CACHE_STARTED have fieldCacheEvent#subjectId always null.
> CacheEvent#subjectId should be subject id associated with SecuritySubject that trigged the cache event.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)