You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Amelchev Nikita (JIRA)" <ji...@apache.org> on 2018/07/05 09:43:00 UTC
[jira] [Commented] (IGNITE-8714) CacheEntryEvent.getOldValue should
be available
[ https://issues.apache.org/jira/browse/IGNITE-8714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533451#comment-16533451 ]
Amelchev Nikita commented on IGNITE-8714:
-----------------------------------------
[~sharpler], Yes, I will continue your work.
> CacheEntryEvent.getOldValue should be available
> -----------------------------------------------
>
> Key: IGNITE-8714
> URL: https://issues.apache.org/jira/browse/IGNITE-8714
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Alexander Menshikov
> Assignee: Amelchev Nikita
> Priority: Major
> Labels: iep-21
> Fix For: 2.7
>
>
> A table is copied from speck changing discussion:
> When CacheEntryListenerConfiguration#isOldValueRequired is *true*:
> ||CacheEntryEvent Method||CreatedListener||UpdatedListener||Removed/Expired Listener||
> |getValue()|_value_|_value_|_oldValue_|
> |getOldValue()|null|_oldValue_|_oldValue_|
> The last column is new behavior for #getValue().
> Сurrent master fails with this reason on following tests:
> * CacheListenerTest.testFilteredListener
> * CacheListenerTest.testCacheEntryListener
> I have to say tests testFilteredListener and testCacheEntryListener also fail in `afterTests` section because of IGNITE-8715, so PR will not change the number of failed tests if ignite-8715 unfixed. But it will change the reason – please see the log.
> Please see also link on JCache TCK and speck 1.1.0 changes.
>
> *UPD:*
> There are a lot of our tests wich going to break by this change. Also, we use events in Services deployment, which will be affected too.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)