Re: Custom string encoding

On Sat, Jul 1, 2017 at 2:24 AM, Sergi Vladykin wrote: > In SQL indexes we may store partial strings and assume them to be in UTF-8, > I don't think this can be abstracted away. But may be this is not a big > deal if in indexes we still will use UTF-8. > Sergi, why does

Re: Request for contributor permission

Thanks. I've assigned ticket to myself and started working on it, but could your answer some questions which have arisen? 1. IgniteCache#localEvict() internally delegates to IgniteInternalCache#evictAll(). Should evict() / evictAll() operations be left alone or deleted as well? 2. Tests heavily

Re: Custom string encoding

In SQL indexes we may store partial strings and assume them to be in UTF-8, I don't think this can be abstracted away. But may be this is not a big deal if in indexes we still will use UTF-8. Sergi 2017-07-01 10:13 GMT+03:00 Dmitriy Setrakyan : > Val, do you know how we

Re: Distributed scheduling

Val, In this case, we should have a notion of a named scheduler and ensure that we don't schedule the same task more than once. This is beginning to look more like a durable cluster singleton service, no? D. On Fri, Jun 30, 2017 at 1:39 PM, Valentin Kulichenko < valentin.kuliche...@gmail.com>

Re: Custom string encoding

Val, do you know how we compare strings in SQL queries? Will we be able to use this encoder? Additionally, I think that the encoder is a bit too abstract. Why not go even further and allow users create their own ASCII table for encoding? D. On Fri, Jun 30, 2017 at 6:49 PM, Valentin Kulichenko <