ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Schäfer (Jira) <j...@apache.org>
Subject [jira] [Created] (IGNITE-14338) Unable to use same class with @QuerySqlField for multiple times for field.
Date Thu, 18 Mar 2021 13:07:00 GMT
André Schäfer created IGNITE-14338:
--------------------------------------

             Summary: Unable to use same class with @QuerySqlField for multiple times for
field.
                 Key: IGNITE-14338
                 URL: https://issues.apache.org/jira/browse/IGNITE-14338
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 2.9.1, 2.10, 2.9
            Reporter: André Schäfer


Potential Regression of IGNITE-13216 ?

When a Class with @QuerySqlField annotated fields is used for fields of the parent entity
multiple time, this results in a pseudo conflict.

e.g. 
{code:java}
class Address { // nested
    @QuerySqlField
    String street;
}

class Person { // parent
    @QuerySqlField
    String name;

    @QuerySqlField
    Address contact; // first usage

    @QuerySqlField
    Address billing; // second usage
}
 {code}
Leads to an Exception like
{code:java}
 javax.cache.CacheException: Property with name 'street' already exists for value: QueryEntity
[key=String, value=Address]{code}
Most likely this is caused by the change in

{{QueryEntityTypeDescriptor:172}}

from {{String propName = prop.fullName();}}

to {{String propName = prop.name();}} 

to be able to perform a check with the annotations name value.

 

 

 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message