Hi Denis,
I filed a ticket: https://issues.apache.org/jira/browse/IGNITE-6528
Thanks,
Mikhail.
On Tue, Sep 26, 2017 at 6:58 PM, Denis Magda wrote:
> Mikhail,
>
> Could you prepare a properly described ticket encompassing the suggested
> warning? Let’s do the improvement for the upcoming releas
Mikhail Cherkasov created IGNITE-6528:
-
Summary: Warning if no table for BinaryObject
Key: IGNITE-6528
URL: https://issues.apache.org/jira/browse/IGNITE-6528
Project: Ignite
Issue Type
Mikhail,
Could you prepare a properly described ticket encompassing the suggested
warning? Let’s do the improvement for the upcoming release.
—
Denis
> On Sep 26, 2017, at 7:23 AM, Mikhail Cherkasov
> wrote:
>
> Hi Dmitry,
>
> The problem is that we don't have strong typing when defining Qu
Hi Dmitry,
The problem is that we don't have strong typing when defining QueryEntriy
and a user can use an arbitrary string id to
define a type, but he should use the same string id to obtain binary object
builder, however, people sometimes confusing this.
So the user can define QueryEntity with v
Pavel, we can optionally enforce that, but not by default.
Dmitry, the problem is the following. User configures Ignite cache and
query entity, does several puts than empty results for SQL. The reason is
very simple - typo in class name or simply different classes in
configuration and of actual ca
On Fri, Sep 22, 2017 at 9:47 AM, Mikhail Cherkasov
wrote:
> 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
> d
We could even add a configuration switch to throw an exception in such case.
I guess that in majority of use cases there is a single type per cache,
and we should have a way to enforce that.
On Fri, Sep 22, 2017 at 7:47 PM, Mikhail Cherkasov
wrote:
> Hi all,
>
> I've seen several times that due
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 th
