Hi all,
I was just wondering on what forms of testing (i.e. fault injection) that
had been performed on Pulsar.
I'm interested because usually some certain frameworks (i.e. Jepsen) has
been used to break distributed
services on purpose.
Therefore, I thought it would be good to know if Pulsar had
Hi Ali,
Thank you for putting this together.
What are the changes required for this? Code changes, documentation
changes, docker file changes? What is the backward compatibility story?
It would be great if you can incorporate these considerations into your
proposal. It is hard for me to figure o
Here is proposal for it, please add comments.
https://docs.google.com/document/d/1kcRIvJVd8pfKxX3lgCRT1XWUAvh5HyHh9XCGIYZ5Flk/edit?usp=sharing
On Sun, Jan 5, 2020 at 7:34 AM Sijie Guo wrote:
> Please create a PIP for that. This requires a discussion and vote.
>
> - Sijie
>
> On Sat, Jan 4, 20
Please create a PIP for that. This requires a discussion and vote.
- Sijie
On Sat, Jan 4, 2020 at 5:04 PM Ali Ahmed wrote:
> Python 2.7 is officially EOL. We should remove associated build artifacts
> and update base docker build and distribution images to jdk11 and python3.
> Ideally before th
2020-01-04 17:58:46 UTC - markg: @markg has joined the channel
2020-01-04 19:31:31 UTC - Sean Carroll: is `mvn clean compile` the only thing
required to compile pulsar? I've been getting
>
pulsar/tiered-storage/jcloud/src/main/java/org/apache/bookkeeper/mledger/offload/jcloud/impl/BlobStoreM
