3. Pluggable metadata interface
● Unified metadata interface
● Support for diverse implementations of metadata backend
● Local KV for Standalone
4. Transactions enhancements
● Transaction logs
● Transaction buffer persistence
● Transaction buffer max read position and snapshot
● Pending ack state persistence
● Pending ack snapshot
5. Message payload processor for Pulsar client
● Originally introduced by KoP
● Support consume Kafka format data by the Pulsar client with custom processor
● Without broker-side format conversion, reduce the burden on brokers
6. Replicate schemas across clusters
● Avoid centralized schema registry
● Reduce the complexity of schema registry operation and maintenance
● Rewrite the schema version during the message replication
● To support global topic policy
7. Produce messages with REST API
Proposal: https://github.com/apache/pulsar/wiki/PIP-64%3A-Introduce-REST-endpoints-for-producing%2C-consuming-and-reading-messages