[
https://issues.apache.org/jira/browse/IGNITE-4009?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15544021#comment-15544021
]
ASF GitHub Bot commented on IGNITE-4009:
----------------------------------------
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1140
IGNITE-4009: Removed error message check for non-serializable fields …
…in writeObjectOverride().
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-4009
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1140.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1140
----
commit eff2f2abb3c74e8511378d3ac8c09f22f699335d
Author: shtykh_roman <[email protected]>
Date: 2016-10-04T01:31:03Z
IGNITE-4009: Removed error message check for non-serializable fields in
writeObjectOverride().
----
> OptimizedObjectOutputStream checks for error message of removed
> IgniteEmailProcessor
> ------------------------------------------------------------------------------------
>
> Key: IGNITE-4009
> URL: https://issues.apache.org/jira/browse/IGNITE-4009
> Project: Ignite
> Issue Type: Bug
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
> Priority: Minor
>
> I wonder if we need a catch part with {{if
> (CONVERTED_ERR.contains(t.getMessage()))}} of {{writeObjectOverride(...)}} at
> all.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
