Ivan Kelly
Ivan Kelly
👍 good stuff. In our case we're just going to assume nothing is cancellation safe. It's too sharp an edge to be load bearing for correctness. Our final solution used...
there shouldn't be a BC consideration for the new API
Ya, old API can stay as it is. Maybe deprecate it. I seem to remember it being very broken at some point in any case, and noone complained.
@sijie This one (https://issues.apache.org/jira/browse/BOOKKEEPER-673). In my head it was more recent than almost 5 years ago. Getting old I guess.
Pulsar tiered storage usage uses the length in the metadata.
Bumping to 4.8.0 We'll do this once salesforce and yahoo stuff are in.