Hi Joe, > I am not sure about the semantics of TableView on a non-persistent topic. > What happens if the client crashes? What is the base state for the table?
If users use a non-persistent topic as the TableView topic, when the client crashes, the TableViews data will be lose. The current use case is to use the non-persistent topic to store the load data used by the new load manager. It doesn't require strong consistency ensure, and no need persistence. Thanks, Kai On 2022/11/14 23:03:13 Joe F wrote: > I am not sure about the semantics of TableView on a non-persistent topic. > > Exactly how does this work? > > What happens if the client crashes? What is the base state for the table? > > What exactly can I expect as a user from this? > > Joe > > On Sun, Nov 13, 2022 at 8:57 PM Kai Wang <kw...@apache.org> wrote: > > > 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 > > > > 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 > > > > > >
