I would defer to Penghui & Ran & Bo to answer it. But I think the original idea to make sure the transaction is fully tested before turning the feature on for broader usage.
- Sijie On Tue, Apr 13, 2021 at 12:59 AM Enrico Olivelli <eolive...@gmail.com> wrote: > Hello, > I believe that "transactions" are a great feature in Pulsar and users > are trying them more and more. > > Currently if you want to use transactions with Pulsar Standalone you have > to: > - add enableTransactionCoordinator=true in the conf/standalone.conf > file and there is no example > - execute the initialization "bin/pulsar > initialize-transaction-coordinator-metadata -cs 127.0.0.1:2181 -c > standalone" (see https://pulsar.apache.org/docs/en/transactions-api/) > > I wonder if we can make it simpler for users and: > 1) add a commented line #enableTransactionCoordinator=true in > conf/standalone.conf > 2) perform automatically the initialization in pulsar standalone if > the enableTransactionCoordinator option is enabled > > For instance I am using pulsar standalone for testing, and I often > nuke the broker with "rm -Rf data" and when I am using transactions I > always have to rerun the initialization procedure (and I must not > forget about it !). > I would like to make the life of users that want to test transactions more > easy > > Thoughts ? > > Enrico >
