You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2019/06/13 21:56:00 UTC

[jira] [Created] (IGNITE-11919) Change message format for incompatible fields' types changes

Denis Magda created IGNITE-11919:
------------------------------------

             Summary: Change message format for incompatible fields' types changes
                 Key: IGNITE-11919
                 URL: https://issues.apache.org/jira/browse/IGNITE-11919
             Project: Ignite
          Issue Type: Task
            Reporter: Denis Magda
             Fix For: 2.8


Follow this discussion thread to find out the reason for the change:
http://apache-ignite-developers.2346864.n4.nabble.com/Ignite-stops-working-suddenly-during-dev-td42207.html

It's suggested to apply the following format:
_ERROR: Type 'ClassName/TypeName' has a different/incorrect type
for field 'FieldName'. Expected 'type1' but 'type2' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._

That's an example of how it will look like:
_ERROR: Type 'Person' has a different/incorrect type
for field 'salary'. Expected 'double' but 'string' was provided. Field
type's modification is unsupported, clean {root_path}/marshaller directory
if the type change is required._



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)