You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Larry Ludden (JIRA)" <ji...@apache.org> on 2019/02/15 14:44:00 UTC
[jira] [Commented] (IGNITE-10717) Binary Marshaller prevents Ignite
jobs from being peer class loaded regardless of Deployment mode
[ https://issues.apache.org/jira/browse/IGNITE-10717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769379#comment-16769379 ]
Larry Ludden commented on IGNITE-10717:
---------------------------------------
On this topic ( although it might not make sense ) maybe a way to remove a class definition from a node / cluster? In our use case all of the objects are temporary, so it would be nice when the node is empty to delete the class definition so we could use an updated version of the class. Just a thought.
> Binary Marshaller prevents Ignite jobs from being peer class loaded regardless of Deployment mode
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-10717
> URL: https://issues.apache.org/jira/browse/IGNITE-10717
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.7
> Reporter: Gert Dubois
> Priority: Major
> Attachments: tm-ignite-serialization-poc.zip
>
>
> When ignite clients submit different versions of the same job that have conflicting class definitions for the Binary Marshaller (different Type of a class field, eg.) through peer class loading to the ignite cluster, the execution fails because of Binary MetaData merging regardless of the specified Deployment Mode.
> This issue prevents us to support clients that might execute older versions of our code (or 3rd party library code) on our Ignite cluster using the default Marshalling settings.
> I added a sample maven project that contains the code to reproduce the issue easily.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)