[
https://issues.apache.org/jira/browse/IGNITE-10717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gert Dubois updated IGNITE-10717:
---------------------------------
Description:
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.
was:
When 2 clients submit different versions of the same job to the ignite cluster
that have conflicting class definitions for the Binary Marshaller (different
Type of a class field, eg.), the execution fails because of Binary MetaData
merging even with Deployment Mode ISOLATED specified.
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.
Summary: Binary Marshaller prevents Ignite jobs from being peer class
loaded regardless of Deployment mode (was: Behaviour of Binary Marshaller not
consistent with Deployment Mode)
> 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)
