On Wed, Nov 29, 2017 at 12:33 AM, Vladimir Ozerov
wrote:
> Alexey,
>
> This is completely unrelated activity.
>
But still is a great idea :)
Alexey,
This is completely unrelated activity.
On Wed, Nov 29, 2017 at 11:16 AM, Dmitriy Setrakyan
wrote:
> On Wed, Nov 29, 2017 at 12:14 AM, Alexey Kuznetsov
> wrote:
>
> >
> > If we are going to rework indexes, could we also think about supporting
> TTL
> > Indexes (like in Mongo DB [1])?
>
On Wed, Nov 29, 2017 at 12:14 AM, Alexey Kuznetsov
wrote:
>
> If we are going to rework indexes, could we also think about supporting TTL
> Indexes (like in Mongo DB [1])?
>
Awesome idea. Is there a ticket?
Vova,
If we are going to rework indexes, could we also think about supporting TTL
Indexes (like in Mongo DB [1])?
[1] https://docs.mongodb.com/manual/core/index-ttl/
On Tue, Nov 28, 2017 at 3:46 AM, Vladimir Ozerov
wrote:
> Igniters,
>
> I'd like to start a discussion about new storage forma
Dima,
1) Primary key lookups could become a bit faster, but no breakthrough is
expected - there will be no need to jump from B+Tree leaf to data page, but
the tree itself will be bigger, because data records will take more space
than index records. I expect parity here.
2) We should observe drama
Denis,
No, most likely free lists (or any other space management component) will
stay still. But in case of index-organized storage we will use it in less
number of scenarios.
On Tue, Nov 28, 2017 at 6:27 AM, Dmitriy Setrakyan
wrote:
> Vladimir,
>
> I definitely like the overall direction. My c
Vladimir,
I definitely like the overall direction. My comments are below...
On Mon, Nov 27, 2017 at 12:46 PM, Vladimir Ozerov
wrote:
>
> I propose to adopt this approach in two phases:
> 1) Optionally add data to leaf pages. This should improve our ScanQuery
> dramatically
>
Definitely a goo
Vladimir,
How the free lists will be affected by the indexed-organized architecture? From
what I see they’re becoming optional.
—
Denis
> On Nov 27, 2017, at 12:46 PM, Vladimir Ozerov wrote:
>
> Igniters,
>
> I'd like to start a discussion about new storage format for Ignite. Our
> current
