ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: Warning if no table for BinaryObject
Date Mon, 25 Sep 2017 12:59:25 GMT
On Fri, Sep 22, 2017 at 9:47 AM, Mikhail Cherkasov <mcherkasov@gridgain.com>

> Hi all,
> I've seen several times that due wrong cache configuration people can't
> find
> data in cache and blame Ignite that it's buggy and doesn't work.
> And it's very difficult to find an error in the code, especially if you
> don't have reach experience with Ignite.
> One of the very common case is that user specifys a name to QueryEntity
> value type:
>     queryEntity.setValueType("MyCoolName")
> and later put data to cache like:
>     ignite.binary.toBinary(value)
> The example is simple and the error is obvious when you see this two lines
> close to each other, however, in real life, cache definition and data
> ingestion are separated by tons of code.
Mikhail, the example may be simple and obvious to some, but not to most
(including me). Can you please explain what it is we are trying to solve?
What is wrong with the above code snippet?

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message