gt; and most likely the last plan will be chosen as the best one.
>>>>>
>>>>> --
>>>>> Kind Regards
>>>>> Roman Kondakov
>>>>>
>>>>>
>>>>> On 10.12.2019 17:19, Vladimir Ozerov wrote:
>&
Why do you think that Drill-style will not let you exploit collation?
>>>>> Collation should be propagated from the index scan in the same way as
>> in
>>>>> other sorted operators, such as merge join or streaming aggregate.
>>>> Provided
>>&g
ck (or any alternative solution to trigger
> >> parent
> >>> re-analysis).
> >>> In other words, propagation of collation from Drill-style indexes
> should
> >> be
> >>> no different from other sorted operators.
> >>>
> >>> Regards,
>
om other sorted operators.
>>>
>>> Regards,
>>> Vladimir.
>>>
>>> вт, 10 дек. 2019 г. в 16:40, Zhenya Stanilovsky
>> >>> :
>>>
>>>>
>>>> Roman just as fast remark, Phoenix builds their approach on
>&g
> > >> Roman just as fast remark, Phoenix builds their approach on
> > >> already existing monolith HBase architecture, most cases it`s just a
> > stub
> > >> for someone who wants use secondary indexes with a base with no
> > >> native s
eir approach on
> >> already existing monolith HBase architecture, most cases it`s just a
> stub
> >> for someone who wants use secondary indexes with a base with no
> >> native support of it. Don`t think it`s good idea here.
> >>
> >>>
> &
who wants use secondary indexes with a base with no
>>> native support of it. Don`t think it`s good idea here.
>>>
>>>>
>>>>
>>>> --- Forwarded message ---
>>>> From: "Roman Kondakov" < kondako...@mail.ru.invalid >
k it`s good idea here.
>>
>>>
>>>
>>> --- Forwarded message -------
>>> From: "Roman Kondakov" < kondako...@mail.ru.invalid >
>>> To: dev@ignite.apache.org
>>> Cc:
>>> Subject: Adding support for Ignite se
tive support of it. Don`t
> think it`s good idea here.
>
>>
>>
>> --- Forwarded message ---
>> From: "Roman Kondakov" < kondako...@mail.ru.invalid >
>> To: dev@ignite.apache.org
>> Cc:
>> Subject: Adding support for Ignite secon
gt; > >From: "Roman Kondakov" < kondako...@mail.ru.invalid >
> > >To: dev@ignite.apache.org
> > >Cc:
> > >Subject: Adding support for Ignite secondary indexes to Apache Calcite
> > >planner
> > >Date: Tue, 10 Dec 2019 15:
kov" < kondako...@mail.ru.invalid >
> >To: dev@ignite.apache.org
> >Cc:
> >Subject: Adding support for Ignite secondary indexes to Apache Calcite
> >planner
> >Date: Tue, 10 Dec 2019 15:55:52 +0300
> >
> >Hi all!
> >
> >As you may know there is
d message ---
>From: "Roman Kondakov" < kondako...@mail.ru.invalid >
>To: dev@ignite.apache.org
>Cc:
>Subject: Adding support for Ignite secondary indexes to Apache Calcite
>planner
>Date: Tue, 10 Dec 2019 15:55:52 +0300
>
>Hi all!
>
>As you may know there
Hi all!
As you may know there is an activity on integration of Apache Calcite
query optimizer into Ignite codebase is being carried out [1],[2].
One of a bunch of problems in this integration is the absence of
out-of-the-box support for secondary indexes in Apache Calcite. After
some research I
13 matches
Mail list logo
