ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Denis Magda <dma...@apache.org>
Subject Re: Warning if no table for BinaryObject
Date Tue, 26 Sep 2017 15:58:03 GMT
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 <mcherkasov@gridgain.com> wrote:
> 
> 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 value type:
> queryEntity.setValueType("MyCoolName") and
> later put to cache the following binary object:
> ignite.binary.toBinary(value), but this object won't be indexed, because
> ignite.binary.toBinary uses class name as string id while indexing expects
> to find "MyCoolName" as id.
> 
> There's no bug in ignite about this, but I think the warning can make
> users' life easy and
> make ignite configuration more friendly to new users.
> 
> Thanks,
> Mikhail.
> 
> 
> 
> 
> On Tue, Sep 26, 2017 at 8:15 AM, Yakov Zhdanov <yzhdanov@apache.org> wrote:
> 
>> 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 cache entry. The fix is pretty simple and make
>> product more usable.
>> 
>> --Yakov
>> 
> 
> 
> 
> -- 
> Thanks,
> Mikhail.


Mime
View raw message