You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Evgenii Zhuravlev <e....@gmail.com> on 2019/05/01 16:24:36 UTC
Re: sizing
Hi,
What do you mean here? Do you mean binary fields VS varchars? Could you
please give an example of the object?
Thank you,
Evgenii
вт, 30 апр. 2019 г. в 12:27, Clay Teahouse <cl...@gmail.com>:
> Hi All
> If I choose binary data type for my objects, as opposed to varchar, will
> it result in any saving, and yes, how much?
> I know that binary type would be faster to read/write but wanted to see if
> there will be any saving in storage.
>
> thanks
> Clay
>
Re: sizing
Posted by Denis Mekhanikov <dm...@gmail.com>.
Clay,
If you want to store plain strings without any schema or markup, then use
varchar.
But if you plan to store POJOs, then binary objects should certainly be
used instead of varchar. Binary types contain meta information, improving
type safety of stored data.
Binary objects don't apply any compression. This improvement is planned to
be implemented on data storage level, not the objects format.
IEP related to data compression:
https://cwiki.apache.org/confluence/display/IGNITE/IEP-20%3A+Data+Compression+in+Ignite
Denis
ср, 1 мая 2019 г. в 19:33, Evgenii Zhuravlev <e....@gmail.com>:
> Hi,
>
> What do you mean here? Do you mean binary fields VS varchars? Could you
> please give an example of the object?
>
> Thank you,
> Evgenii
>
> вт, 30 апр. 2019 г. в 12:27, Clay Teahouse <cl...@gmail.com>:
>
>> Hi All
>> If I choose binary data type for my objects, as opposed to varchar, will
>> it result in any saving, and yes, how much?
>> I know that binary type would be faster to read/write but wanted to see
>> if there will be any saving in storage.
>>
>> thanks
>> Clay
>>
>