ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "jan.swaelens" <jan.swael...@sofico.be>
Subject Ignite Schema Import Utility - Case mismatch between table index and query index defined in generated code
Date Fri, 01 Apr 2016 12:32:45 GMT
Hello,

Continuing my initial mention of this problem in another  thread
<http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-tp3790p3806.html>
 
where more information such as DDL and generated code can be found:

Looking in the CacheConfig java file you see query indexes being defined
which reference uppercase column names, this indeed matches with the table
definition. However the pojo and defined fields are not completely in
uppercase, which causes a failure when the H2 tables are being created
during the definition of the cache.

Would this be something than be fixed in the code generator, to use the
field name generated in java rather than the direct index name obtained from
the DDL when generating query index definition code?

br
jan



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Case-mismatch-between-table-index-and-query-index-defined-in-generated-e-tp3858.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message