Hi Jan! It seems that we can fix this issue with help of fields aliases.
I created issues for support fields aliases generation. https://issues.apache.org/jira/browse/IGNITE-3028 (Schema Import utility) https://issues.apache.org/jira/browse/IGNITE-3029 (Web Console) Thanks! On Wed, Apr 20, 2016 at 3:51 AM, vkulichenko <valentin.kuliche...@gmail.com> wrote: > Hi Jan, > > The first approach you mentioned should work for you, Ignite uses object > field names as SQL names. There is currently no way to generate classes > with > DB names used as field names, but as Alexey mentioned, this is something > that can be added later. > > In the meantime, you can modify POJOs and CacheConfig manually. > > -Val > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4341.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
