Hi Michael, > What time is used to compute expiration? Is it the publish time or the > receive time? This TTL will be based on the message publish time. We can also make it configurable if users have this demand.
> Also, are there cases that will reset a key's timer? If some keys need to reset the timer, users can publish a new message with the old key . Since we are using the publish time as the expiration time. Thanks, Kai On 2022/11/14 16:43:06 Michael Marshall wrote: > > And this PIP title has been changed to `Make TableView support TTL`. > > What time is used to compute expiration? Is it the publish time or the > receive time? Also, are there cases that will reset a key's timer? > > Thanks, > Michael > > On Mon, Nov 14, 2022 at 2:40 AM Enrico Olivelli <eolive...@gmail.com> wrote: > > > > Il giorno lun 14 nov 2022 alle ore 05:57 Kai Wang <kw...@apache.org> ha > > scritto: > > > > > > Hi, pulsar-dev community, > > > > > > Since the non-persistent topic support doesn't require API changes. I > > > have pushed a PR to implement it, which has already been merged. > > > > > > See: https://github.com/apache/pulsar/pull/18375 > > > > Perfect > > > > Thanks > > Enrico > > > > > > > > And this PIP title has been changed to `Make TableView support TTL`. > > > > > > PIP link: https://github.com/apache/pulsar/issues/18229 > > > > > > Thanks, > > > Kai > > > > > > On 2022/11/04 02:28:41 Kai Wang wrote: > > > > Hi, pulsar-dev community, > > > > > > > > I’ve opened a PIP to discuss : PIP-221: Make TableView support read the > > > > non-persistent topic. > > > > > > > > PIP link: https://github.com/apache/pulsar/issues/18229 > > > > > > > > Thanks, > > > > Kai > > > > >
