Alex Savitsky created IGNITE-11840:
--------------------------------------
Summary: Annotation-based configuration creates not only nested fields, but the enclosing object as well
Key: IGNITE-11840
URL:
https://issues.apache.org/jira/browse/IGNITE-11840 Project: Ignite
Issue Type: Bug
Components: general
Affects Versions: 2.7
Reporter: Alex Savitsky
Using the annotation-based example from the [documentation|
https://apacheignite-sql.readme.io/docs/schema-and-indexes#annotation-based-configuration], I'm creating a cache of Person object, with a nested Address inside. The expectation is that the created SQL table would have 4 columns: "id", "name", "street", and "zip". However, it also creates a column named "address" of type OTHER, and there's no apparent way to turn the creation of that column off, without also losing the columns "street" and "zip". The OTHER type messes up most of the SQL tools, as they don't know how to deal with it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)