ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vyacheslav Daradur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version
Date Thu, 13 Apr 2017 11:49:41 GMT

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

Vyacheslav Daradur commented on IGNITE-4211:
--------------------------------------------

[~avinogradov]
bq. I'm 99% sure that the reason is valueLoader we sending at EntryProcessor. 
That's exactly what I was thinking.

The following simple implemenation works well.
{code}
    /** {@inheritDoc} */
    @SuppressWarnings("unchecked")
    @Override public <T> T get(Object key, Callable<T> valueLoader) {
        synchronized (this) {
            Object val = cache.get(key);

            if (val != null)
                return (T)fromStoreValue(val);

            try {
                val = valueLoader.call();
            }
            catch (Exception e) {
                throw new ValueRetrievalException(key, valueLoader, e);
            }

            cache.put(key, val);

            return (T) val;
        }
    }
{code}

> Update Spring dependency to latest stable version
> -------------------------------------------------
>
>                 Key: IGNITE-4211
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4211
>             Project: Ignite
>          Issue Type: Improvement
>          Components: build
>    Affects Versions: 1.7
>            Reporter: Sergey Kozlov
>            Assignee: Vyacheslav Daradur
>             Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still uses 4.1.0
released two years ago. Could we to update to latest stable version (4.3.4 at the moment)?



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message