ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Mashenkov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2560) Support injections in entry processors
Date Tue, 23 Aug 2016 15:01:22 GMT

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

Andrew Mashenkov commented on IGNITE-2560:

Hi, Semen
I can't find test for invokeAll(Map<? extends K, ? extends EntryProcessor<K, V, T>>
map, Object... args)', could you please point me where it was added?
See class _GridCacheAbstractFullApiSelfTest_. Method _testTransformResourceInjection_ calls
_doTransformResourceInjection_ with cache and cache-with-async. Method _doTransformResourceInjection_
make checks with _invoke_, _invokeAll_, _invokeAll (Map ...)_.

 in GridLocalAtomicCache let's do not use wrapper at all, instead just call GridResourceProcessor.inject
on entry processor
Please, take a look on method _invokeAllAsync_ in GridLocalAtomicCache class. Method signature
tells it throws *no* exceptions, but 
_resourceProcessor.inject(..)_ does. Whether exception is being processed correctly?

> Support injections in entry processors
> --------------------------------------
>                 Key: IGNITE-2560
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2560
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Valentin Kulichenko
>            Assignee: Andrew Mashenkov
>             Fix For: 1.8
> Currently resources are not injected in entry processor, which is not consistent with
other functionality, like closures, jobs, listeners, etc.
> To avoid performance degradation we should introspect the class only once, cache this
information and do not try to inject if there are no annotations.

This message was sent by Atlassian JIRA

View raw message