Thanks. A simple BinaryConfiguration has helped in the case of one isolated node or more nodes with the same configuration. The problem is that the storable cache is configured with the node filter. So, only several nodes share the cache. Another nodes aren't supposed to know anything about these manually configured types in the BinaryConfiguration and haven't such config. That causes:
IgniteSpiException: Local node's binary configuration is not equal to remote node's binary configuration Can I anyhow bind BinaryConfiguration to certain cache with node filter, not to entire cluster? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/BinaryInvalidTypeException-Unknown-pair-platformId-typeId-when-using-CacheJdbcPojoStoreFactory-and-rh-tp13384p13431.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
