Denis,
Minor changes to your suggestion:
*"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."*
===
Garrett Alley
Documentation
GridGain Systems
On Wed, Jun 12, 2019 at 11:15 AM Denis Magda <dma...@apache.org> wrote:
> Alex, Garrett,
>
> How about this error message?
>
> That's what we have know: *ERROR: Binary type has different field types
> [typeName=Person, fieldName=salary, fieldTypeName1=double,
> fieldTypeName2=String]*
>
> That's how I would change it: *"Type 'Person' has 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"*
>
> -
> Denis
>
>
> On Thu, Jun 6, 2019 at 5:24 AM Alexey Goncharuk <
> alexey.goncha...@gmail.com>
> wrote:
>
> > Hello Denis,
> >
> > As for p.1 - fully agree. For p.2 - I have some ideas to be implemented
> in
> > the future in Ignite 3.0, will share some ideas later.
> >
> > чт, 6 июн. 2019 г. в 13:29, Denis Magda <dma...@apache.org>:
> >
> > > Hey Igniters,
> > >
> > > I'd like us to brainstorm how to solve the following usability issue.
> > >
> > > A user starts developing an app and can change the data model via a
> > > configuration or DDL frequently. However, if there is an incompatible
> > data
> > > model change like a type/field modification Ignite will fail to restart
> > or
> > > begins throwing "wrong data type" exceptions.
> > >
> > > A solution for these scenarios is to clean the "marshaller/" folder.
> > Guess
> > > who knows this trick? A few of us. Had to do this all the time while
> > baking
> > > a demo for one of the recent shows and here is a good example of users'
> > > hardships:
> > >
> > >
> >
> https://stackoverflow.com/questions/56384773/apache-ignite-programmatically-destroy-persistent-cache
> > >
> > > How do you see this needs to be addressed considering:
> > >
> > > 1. Current Ignite serialization format - a special message that
> > explains
> > > what to clean and where or some sort of automation?
> > > 2. Future storage independent format - when binary serialization
> logic
> > > will be revisited. @Alex Goncharuk, please step in.
> > >
> > >
> > > -
> > > Denis
> > >
> >
>
