Re: log compaction of entries

2017-11-08 Thread Enrico Olivelli
Il mer 8 nov 2017, 16:27 Ivan Kelly ha scritto: > > I believe I'm missing the implication of this. Does that mean we need > > to logically name ledgers in a way that can keep track, because each > > has only one uninterrupted session of write operations, otherwise it > > is

Re: log compaction of entries

2017-11-08 Thread Ivan Kelly
> I believe I'm missing the implication of this. Does that mean we need > to logically name ledgers in a way that can keep track, because each > has only one uninterrupted session of write operations, otherwise it > is read only? It's not possible to specify a name on ledger creation. When you

Re: log compaction of entries

2017-11-07 Thread Sijie Guo
On Tue, Nov 7, 2017 at 12:18 PM, Istvan Soos wrote: > On Tue, Nov 7, 2017 at 8:09 PM, Sijie Guo wrote: > > But I would to learn more about your use case and to see how we can > support > > you. > > It is a nice feature in Kafka, and I've seen a complex

Re: log compaction of entries

2017-11-07 Thread Istvan Soos
On Tue, Nov 7, 2017 at 8:09 PM, Sijie Guo wrote: > But I would to learn more about your use case and to see how we can support > you. It is a nice feature in Kafka, and I've seen a complex app using it: https://kafka.apache.org/documentation.html#compaction My use case is

Re: log compaction of entries

2017-11-07 Thread Sijie Guo
On Tue, Nov 7, 2017 at 10:47 AM, Istvan Soos wrote: > On the website [0] I gather that data compaction is mostly about > cleaning up after we delete a ledger. Is there a feature or plan to > implement entry-level compaction, e.g. to have an ID that uniquely > identifies an