André Schäfer created IGNITE-14339:
--------------------------------------
Summary: Class with @QuerySqlField annotated fields cannot be used
for multiple fields of an aggregate
Key: IGNITE-14339
URL: https://issues.apache.org/jira/browse/IGNITE-14339
Project: Ignite
Issue Type: Bug
Affects Versions: 2.9.1, 2.10, 2.9
Reporter: André Schäfer
Potential Regression of IGNITE-13216 ?
If a class that has fields annotated with @QuerySqlField (without name
attribute) and should be used for multiple fields of a parent class, this
results in a pseudo conflict and throws an exception.
e.g.
{code}
class Person { // parent
@QuerySqlField
Address contact; // first usage
@QuerySqlField
Address billing; // second usage
}
class Address { // nested
@QuerySqlField
String street;
}
{code}
leads to an exception like
{code}
javax.cache.CacheException: Property with name 'street' already exists for
value: QueryEntity [key=String, value=Person]
{code}
This is cause by a change in \{{QueryEntityTypeDescriptor:172}}:
from \{{String propName = prop.fullName();}}
to \{{String propName = prop.name();}}
most likely to be able to use it for some hangling logic for the value
attribute of the annotation.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
