[
https://issues.apache.org/jira/browse/IGNITE-1039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladimir Ozerov resolved IGNITE-1039.
-------------------------------------
Resolution: Won't Fix
This doesn't work in general case. E.g. {{Organization}} may be a root of
object hierarchy, and some other {{FinancialOrganization extends Organization}}
may have other SQL fields which we will miss.
Another problem is that user will not be able to have nested class with query
fields which he do not want to add to the table (the opposite situation).
For this reason it is better to keep things simple and do not rely on
reflection which is out of our control.
> Need to inspect nested objects for indexing automatically
> ---------------------------------------------------------
>
> Key: IGNITE-1039
> URL: https://issues.apache.org/jira/browse/IGNITE-1039
> Project: Ignite
> Issue Type: Bug
> Components: cache, sql
> Affects Versions: sprint-4
> Reporter: Valentin Kulichenko
> Priority: Major
> Labels: Usability, sql
>
> Imagine we have this data model with {{Organization}} object nested into
> {{Person}}:
> {code}
> Person {
> @QuerySqlField
> String name;
> Organization org;
> }
> Organization {
> @QuerySqlField
> String name;
> }
> {code}
> This currently doesn't work because {{Organization}} is not inspected until
> we put {{@QuerySqlField}} annotation on {{Person.org}} field.
> Such design is not good because it is:
> * Counterintuitive
> * Adds {{org}} field to tables which is not needed.
> We should inspect nested objects automatically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
