ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-331) CacheTypeMetadata is not read in case CacheQueryConfiguration is not set.
Date Tue, 24 Feb 2015 14:20:08 GMT
Vladimir Ozerov created IGNITE-331:
--------------------------------------

             Summary: CacheTypeMetadata is not read in case CacheQueryConfiguration is not
set.
                 Key: IGNITE-331
                 URL: https://issues.apache.org/jira/browse/IGNITE-331
             Project: Ignite
          Issue Type: Bug
          Components: cache
    Affects Versions: sprint-2
            Reporter: Vladimir Ozerov
             Fix For: sprint-2


I see the following code in GridQueryProcessor.start():
{code}
CacheQueryConfiguration qryCfg = ccfg.getQueryConfiguration();

if (qryCfg != null) {
    if (!F.isEmpty(ccfg.getTypeMetadata())) {
        for (CacheTypeMetadata meta : ccfg.getTypeMetadata())
            declaredTypesByName.put(new TypeName(ccfg.getName(), meta.getValueType()), meta);
    }

    if (qryCfg.getTypeResolver() != null)
        typeResolvers.put(ccfg.getName(), qryCfg.getTypeResolver());
}
{code}
So, type metadata is not read in case CacheQueryConfiguration is not set. If we set empty
CacheQueryConfiguration, all is fine. Looks like a usability issue - why does user have to
specify empty CacheQueryConfiguration?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message