Jan, I think it is know bug.
See https://issues.apache.org/jira/browse/IGNITE-2849 This issue is already closed. Could you check this using master branch? You will need to build sources from master and check. Any way it will be available in next release. It seems that Ignite missing nightly builds from master. I will ask on dev list about this. On Fri, Apr 1, 2016 at 7:18 PM, jan.swaelens <[email protected]> wrote: > Hello, > > I get an error which stops the cache from loading in > 'BinaryUtils.mergeMetadata' when it tries to merge two values for the > 'nameMlid' field. At a certain point it generates a mismatch error because > newFieldTypeName is set to long and OldFieldTypeName is set to Object. > > The trace leading to the error can be found here: > > http://apache-ignite-users.70518.x6.nabble.com/file/n3813/binaryMismatch.log > < > http://apache-ignite-users.70518.x6.nabble.com/file/n3813/binaryMismatch.log > > > > Additional information (generated files, ddl...) can also be found in that > thread: > > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-td3790.html > < > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-td3790.html > > > > The loading of the cache is triggered by calling the following method: > cache.loadCache(null); > > > thanks > jan > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-BinaryMetadata-mismatch-error-when-using-gerenated-classes-tp3857.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
