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 - BinaryMetadata mismatch error when using gerenated classes
Date Fri, 01 Apr 2016 12:18:31 GMT
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.

Mime
View raw message