Google Git
Sign in
apache / pulsar / HEAD / . / pip
tree: 6305f7ac450da5122821b09a60615987fe7c7a5e [path history] [tgz]
  1. images/
  2. pip-1.md
  3. pip-10.md
  4. pip-100.md
  5. pip-101.md
  6. pip-104.md
  7. pip-105.md
  8. pip-106.md
  9. pip-107.md
  10. pip-108.md
  11. pip-109.md
  12. pip-11.md
  13. pip-110.md
  14. pip-111.md
  15. pip-112.md
  16. pip-116.md
  17. pip-117.md
  18. pip-118.md
  19. pip-119.md
  20. pip-12.md
  21. pip-120.md
  22. pip-121.md
  23. pip-122.md
  24. pip-123.md
  25. pip-124.md
  26. pip-129.md
  27. pip-13.md
  28. pip-130.md
  29. pip-131.md
  30. pip-132.md
  31. pip-135.md
  32. pip-136.md
  33. pip-137.md
  34. pip-14.md
  35. pip-143.md
  36. pip-144.md
  37. pip-146.md
  38. pip-148.md
  39. pip-149.md
  40. pip-15.md
  41. pip-152.md
  42. pip-154.md
  43. pip-155.md
  44. pip-156.md
  45. pip-157.md
  46. pip-16.md
  47. pip-160.md
  48. pip-161.md
  49. pip-162.md
  50. pip-165.md
  51. pip-17.md
  52. pip-173.md
  53. pip-174.md
  54. pip-175.md
  55. pip-176.md
  56. pip-177.md
  57. pip-178.md
  58. pip-179.md
  59. pip-18.md
  60. pip-180.md
  61. pip-181.md
  62. pip-182.md
  63. pip-183.md
  64. pip-184.md
  65. pip-186.md
  66. pip-187.md
  67. pip-188.md
  68. pip-189.md
  69. pip-19.md
  70. pip-190.md
  71. pip-191.md
  72. pip-192.md
  73. pip-193.md
  74. pip-194.md
  75. pip-195.md
  76. pip-198.md
  77. pip-2.md
  78. pip-20.md
  79. pip-201.md
  80. pip-204.md
  81. pip-205.md
  82. pip-209.md
  83. pip-21.md
  84. pip-22.md
  85. pip-23.md
  86. pip-24.md
  87. pip-243.md
  88. pip-249.md
  89. pip-25.md
  90. pip-259.md
  91. pip-26.md
  92. pip-261.md
  93. pip-264.md
  94. pip-265.md
  95. pip-27.md
  96. pip-275.md
  97. pip-276.md
  98. pip-277.md
  99. pip-278.md
  100. pip-279.md
  101. pip-28.md
  102. pip-280.md
  103. pip-281.md
  104. pip-282.md
  105. pip-284.md
  106. pip-286.md
  107. pip-289.md
  108. pip-29.md
  109. pip-290.md
  110. pip-292.md
  111. pip-293.md
  112. pip-296.md
  113. pip-297.md
  114. pip-298.md
  115. pip-299.md
  116. pip-3.md
  117. pip-30.md
  118. pip-300.md
  119. pip-301.md
  120. pip-302.md
  121. pip-303.md
  122. pip-305.md
  123. pip-306.md
  124. pip-307.md
  125. pip-31.md
  126. pip-312.md
  127. pip-313.md
  128. pip-315.md
  129. pip-318.md
  130. pip-32.md
  131. pip-320.md
  132. pip-321.md
  133. pip-322.md
  134. pip-323.md
  135. pip-324.md
  136. pip-325.md
  137. pip-326.md
  138. pip-327.md
  139. pip-329.md
  140. pip-33.md
  141. pip-330.md
  142. pip-335.md
  143. pip-337.md
  144. pip-339.md
  145. pip-34.md
  146. pip-342.md
  147. pip-343.md
  148. pip-344.md
  149. pip-347.md
  150. pip-348.md
  151. pip-349.md
  152. pip-35.md
  153. pip-350.md
  154. pip-351.md
  155. pip-352.md
  156. pip-353.md
  157. pip-354.md
  158. pip-355.md
  159. pip-356.md
  160. pip-357.md
  161. pip-358.md
  162. pip-359.md
  163. pip-36.md
  164. pip-360.md
  165. pip-363.md
  166. pip-364.md
  167. pip-366.md
  168. pip-367.md
  169. pip-368.md
  170. pip-369.md
  171. pip-37.md
  172. pip-370.md
  173. pip-373.md
  174. pip-374.md
  175. pip-375.md
  176. pip-376.md
  177. pip-378.md
  178. pip-379.md
  179. pip-38.md
  180. pip-380.md
  181. pip-381.md
  182. pip-382.md
  183. pip-383.md
  184. pip-384.md
  185. pip-389.md
  186. pip-39.md
  187. pip-391.md
  188. pip-392.md
  189. pip-393.md
  190. pip-395.md
  191. pip-396.md
  192. pip-399.md
  193. pip-4.md
  194. pip-40.md
  195. pip-401.md
  196. pip-402.md
  197. pip-404.md
  198. pip-406.md
  199. pip-407.md
  200. pip-409.md
  201. pip-41.md
  202. pip-412.md
  203. pip-414.md
  204. pip-415.md
  205. pip-416.md
  206. pip-42.md
  207. pip-420.md
  208. pip-421.md
  209. pip-422.md
  210. pip-425.md
  211. pip-427.md
  212. pip-428.md
  213. pip-429.md
  214. pip-43.md
  215. pip-430.md
  216. pip-431.md
  217. pip-432.md
  218. pip-433.md
  219. pip-434.md
  220. pip-435.md
  221. pip-436.md
  222. pip-437.md
  223. pip-44.md
  224. pip-442.md
  225. pip-443.md
  226. pip-444.md
  227. pip-45.md
  228. pip-46.md
  229. pip-47.md
  230. pip-48.md
  231. pip-49.md
  232. pip-5.md
  233. pip-50.md
  234. pip-51.md
  235. pip-52.md
  236. pip-53.md
  237. pip-54.md
  238. pip-55.md
  239. pip-56.md
  240. pip-57.md
  241. pip-58.md
  242. pip-59.md
  243. pip-6.md
  244. pip-60.md
  245. pip-61.md
  246. pip-62.md
  247. pip-63.md
  248. pip-64.md
  249. pip-65.md
  250. pip-66.md
  251. pip-67.md
  252. pip-68.md
  253. pip-69.md
  254. pip-7.md
  255. pip-70.md
  256. pip-71.md
  257. pip-72.md
  258. pip-73.md
  259. pip-74.md
  260. pip-75.md
  261. pip-76.md
  262. pip-77.md
  263. pip-78.md
  264. pip-79.md
  265. pip-8.md
  266. pip-80.md
  267. pip-81.md
  268. pip-82.md
  269. pip-83.md
  270. pip-84.md
  271. pip-85.md
  272. pip-86.md
  273. pip-87.md
  274. pip-88.md
  275. pip-89.md
  276. pip-9.md
  277. pip-90.md
  278. pip-91.md
  279. pip-92.md
  280. pip-93.md
  281. pip-94.md
  282. pip-95.md
  283. pip-96.md
  284. pip-97.md
  285. pip-98.md
  286. pip-99.md
  287. README.md
  288. TEMPLATE.md
pip/README.md

Pulsar Improvement Proposal (PIP)

What is a PIP?

The PIP is a “Pulsar Improvement Proposal” and it's the mechanism used to propose changes to the Apache Pulsar codebases.

The changes might be in terms of new features, large code refactoring, changes to APIs.

In practical terms, the PIP defines a process in which developers can submit a design doc, receive feedback and get the “go ahead” to execute.

What is the goal of a PIP?

There are several goals for the PIP process:

  1. Ensure community technical discussion of major changes to the Apache Pulsar codebase.

  2. Provide clear and thorough design documentation of the proposed changes. Make sure every Pulsar developer will have enough context to effectively perform a code review of the Pull Requests.

  3. Use the PIP document to serve as the baseline on which to create the documentation for the new feature.

  4. Have greater scrutiny to changes are affecting the public APIs (as defined below) to reduce chances of introducing breaking changes or APIs that are not expressing an ideal semantic.

It is not a goal for PIP to add undue process or slow-down the development.

When is a PIP required?

  • Any new feature for Pulsar brokers or client
  • Any change to the public APIs (Client APIs, REST APIs, Plugin APIs)
  • Any change to the wire protocol APIs
  • Any change to the API of Pulsar CLI tools (eg: new options)
  • Any change to the semantic of existing functionality, even when current behavior is incorrect.
  • Any large code change that will touch multiple components
  • Any changes to the metrics (metrics endpoint, topic stats, topics internal stats, broker stats, etc.)
  • Any change to the configuration

When is a PIP not required?

  • Bug-fixes
  • Simple enhancements that won't affect the APIs or the semantic
  • Small documentation changes
  • Small website changes
  • Build scripts changes (except: a complete rewrite)

Who can create a PIP?

Any person willing to contribute to the Apache Pulsar project is welcome to create a PIP.

How does the PIP process work?

A PIP proposal can be in these states:

  1. DRAFT: (Optional) This might be used for contributors to collaborate and to seek feedback on an incomplete version of the proposal.

  2. DISCUSSION: The proposal has been submitted to the community for feedback and approval.

  3. ACCEPTED: The proposal has been accepted by the Pulsar project.

  4. REJECTED: The proposal has not been accepted by the Pulsar project.

  5. IMPLEMENTED: The implementation of the proposed changes have been completed and everything has been merged.

  6. RELEASED: The proposed changes have been included in an official Apache Pulsar release.

The process works in the following way:

  1. Fork https://github.com/apache/pulsar repository (Using the fork button on GitHub).
  2. Clone the repository, and on it, copy the file pip/TEMPLATE.md and name it pip-xxx.md. The number xxx should be the next sequential number after the last contributed PIP. You view the list of contributed PIPs (at any status) as a list of Pull Requests having a “PIP” label. Use the link here as shortcut.
  3. Write the proposal following the section outlined by the template and the explanation for each section in the comment it contains (you can delete the comment once done).
    • If you need diagrams, avoid attaching large files. You can use MermaidJS as simple language to describe many types of diagrams.
  4. Create GitHub Pull request (PR). The PR title should be [improve][pip] PIP-xxx: {title}, where the xxx match the number given in previous step (file-name). Replace {title} with a short title to your proposal. Validate again that your number does not collide, by step (2) numbering check.
  5. The author(s) will email the dev@pulsar.apache.org mailing list to kick off a discussion, using subject prefix [DISCUSS] PIP-xxx: {PIP TITLE}. The discussion will happen in broader context either on the mailing list or as general comments on the PR. Many of the discussion items will be on particular aspect of the proposal, hence they should be as comments in the PR to specific lines in the proposal file.
  6. Update file with a link to the discussion on the mailing. You can obtain it from Apache Pony Mail.
  7. Based on the discussion and feedback, some changes might be applied by authors to the text of the proposal. They will be applied as extra commits, making it easier to track the changes.
  8. Once some consensus is reached, there will be a vote to formally approve the proposal. The vote will be held on the dev@pulsar.apache.org mailing list, by sending a message using subject [VOTE] PIP-xxx: {PIP TITLE}. Make sure to include a link to the PIP PR in the body of the message. Make sure to update the PIP with a link to the vote. You can obtain it from Apache Pony Mail. Everyone is welcome to vote on the proposal, though only the vote of the PMC members will be considered binding. The requirement is to have at least one binding +1 vote from a lazy majority if no binding -1 votes have been cast on the PIP. The vote should stay open for at least 48 hours.
  9. When the vote is closed, if the outcome is positive, ask a PMC member (using voting thread on mailing list) to merge the PR.
  10. If the outcome is negative, please close the PR (with a small comment that the close is a result of a vote).

All the future implementation Pull Requests that will be created, should always reference the PIP-XXX in the commit log message and the PR title. It is advised to create a master GitHub issue to formulate the execution plan and track its progress.

Example

  • Eve ran into some issues with the client metrics - she needed a metric which was missing.
  • She read the code a bit, and has an idea what metrics she wishes to add.
  • She summarized her idea and direction in an email to the DEV mailing list (she located it on Discussions section on the website.
  • She didn't get any response from the community, so she joined the next community meeting. There Matteo Merli and Asaf helped setup a channel in Slack to brainstorm the idea and meet on Zoom with a few Pulsar contributors (e.g. Lari and Tison).
  • Once Eve had a good enough context, and good design outline, she opened a new branch in her Pulsar repository, duplicated TEMPLATE.md and created pip-xxx.MD (the number she will take later).
  • She followed the template and submitted the pip as a new PR to pulsar repository.
  • Once the PR was created, she modified the version to match the rules described at step 2, both for PR title and file name.
  • She sent an email to the DEV mailing list, titled “[DISCUSS] PIP-123: Adding metrics for ...” , described shortly in the email what the PIP was about and gave a link.
  • She got no response for anyone for 2 weeks, so she nudged the people that helped her brainstorm (e.g. Lary and Tison) and pinged in #dev that she needs more reviewers.
  • Once she got 3 reviews from PMC members and the community had at least a few days from the moment the PR was announceed on DEV, she sent a vote email to the DEV mailing list titled “[VOTE] PIP-123: Adding metrics for ...”.
  • She nudged the reviewers to reply with a binding vote, waited for 2-3 days, and then concluded the vote by sending a reply tallying up the binding and non-binding votes.
  • She updated the PIP with links to discuss and vote emails, and then asked a PMC member who voted +1, to merge (using GitHub mentionon the PR).

List of PIPs

Current PIPs Table of Contents

The following table lists all current PIPs in this directory, sorted by PIP number:

PIP NumberTitle
PIP-1Pulsar Proxy
PIP-2Non Persistent topic
PIP-3Message dispatch throttling
PIP-4Pulsar End to End Encryption
PIP-5Event time
PIP-6Guaranteed Message Deduplication
PIP-7Pulsar Failure domain and Anti affinity namespaces
PIP-8Pulsar beyond 1M topics
PIP-9Adding more Security checks to Pulsar Proxy
PIP-10Remove cluster for namespace and topic names
PIP-11Short topic names
PIP-12Introduce builder for creating Producer Consumer Reader
PIP-13Subscribe to topics represented by regular expressions
PIP-14Topic compaction
PIP-15Pulsar Functions
PIP-16Pulsar “instance” terminology change
PIP-17Tiered storage for Pulsar topics
PIP-18Pulsar Replicator
PIP-19Pulsar SQL
PIP-20Mechanism to revoke TLS authentication
PIP-21Pulsar Edge Component
PIP-22Pulsar Dead Letter Topic
PIP-23Message Tracing By Interceptors
PIP-24Simplify memory settings
PIP-25Token based authentication
PIP-26Delayed Message Delivery
PIP-27Add checklist in github pull request template
PIP-28Pulsar Proxy Gateway Improvement
PIP-29One package for both pulsar-client and pulsar-admin
PIP-30change authentication provider API to support mutual authentication
PIP-31Transaction Support
PIP-32Go Function API, Instance and LocalRun
PIP-33Replicated subscriptions
PIP-34Add new subscribe type Key_shared
PIP-35Improve topic lookup for topics that have high number of partitions
PIP-36Max Message Size
PIP-37Large message size handling in Pulsar
PIP-38Batch Receiving Messages
PIP-39Namespace Change Events
PIP-40Pulsar Manager
PIP-41Pluggable Protocol Handler
PIP-42KoP - Kafka on Pulsar
PIP-43producer send message with different schema
PIP-44Separate schema compatibility checker for producer and consumer
PIP-45Pluggable metadata interface
PIP-46Next-gen Proxy
PIP-47Time Based Release Plan
PIP-48hierarchical admin api
PIP-49Permission levels and inheritance
PIP-50Package Management
PIP-51Tenant policy support
PIP-52Message dispatch throttling relative to publish rate
PIP-53Contribute DotPulsar to Apache Pulsar
PIP-54Support acknowledgement at batch index level
PIP-55Refresh Authentication Credentials
PIP-56Python3 Migration
PIP-57Improve Broker's Zookeeper Session Timeout Handling
PIP-58Support Consumers Set Custom Retry Delay
PIP-59gPRC Protocol Handler
PIP-60Support Proxy server with SNI routing
PIP-61Advertised multiple addresses
PIP-62Move connectors, adapters and Pulsar Presto to separate repositories
PIP-63Readonly Topic Ownership Support
PIP-64Introduce REST endpoints for producing, consuming and reading messages
PIP-65Adapting Pulsar IO Sources to support Batch Sources
PIP-66Pulsar Function Mesh
PIP-67Pulsarctl - An alternative tools of pulsar-admin
PIP-68Exclusive Producer
PIP-69Schema design for Go client
PIP-70Introduce lightweight broker entry metadata
PIP-71Pulsar SQL migrate SchemaHandle to presto decoder
PIP-72Introduce Pulsar Interface Taxonomy: Audience and Stability Classification
PIP-73Configurable data source priority for message reading
PIP-74Pulsar client memory limits
PIP-75Replace protobuf code generator
PIP-76Streaming Offload
PIP-77Contribute Supernova to Apache Pulsar
PIP-78Generate Docs from Code Automatically
PIP-79Reduce redundant producers from partitioned producer
PIP-80Unified namespace-level admin API
PIP-81Split the individual acknowledgments into multiple entries
PIP-82Tenant and namespace level rate limiting
PIP-83Pulsar client: Message consumption with pooled buffer
PIP-84Pulsar client: Redeliver command add epoch
PIP-85Expose Pulsar-Client via Function/Connector BaseContext
PIP-86Pulsar Functions: Preload and release external resources
PIP-87Upgrade Pulsar Website Framework (Docusaurus)
PIP-88Replicate schemas across multiple
PIP-89Structured document logging
PIP-90Expose broker entry metadata to the client
PIP-91Separate lookup timeout from operation timeout
PIP-92Topic policy across multiple clusters
PIP-93Transaction performance tools
PIP-94Message converter at broker level
PIP-95Smart Listener Selection with Multiple Bind Addresses
PIP-96Message payload processor for Pulsar client
PIP-97Asynchronous Authentication Provider
PIP-98Redesign Pulsar Information Architecture
PIP-99Pulsar Proxy Extensions
PIP-100Pulsar pluggable topic factory
PIP-101Add seek by index feature for consumer
PIP-104Add new consumer type: TableView
PIP-105Support pluggable entry filter in Dispatcher
PIP-106Negative acknowledgment backoff
PIP-107Introduce the chunk message ID PIP
PIP-108Pulsar Feature Matrix (Client and Function)
PIP-109Introduce Bot to Improve Efficiency of Developing Docs
PIP-110Topic metadata
PIP-111Add messages produced by Protocol Handler When checking maxMessagePublishBufferSizeInMB
PIP-112Generate Release Notes Automatically
PIP-116Create Pulsar Writing Style Guide
PIP-117Change Pulsar Standalone defaults
PIP-118Do not restart brokers when ZooKeeper session expires
PIP-119Enable consistent hashing by default on KeyShared dispatcher
PIP-120Enable client memory limit by default
PIP-121Pulsar cluster level auto failover
PIP-122Change loadBalancer default loadSheddingStrategy to ThresholdShedder
PIP-123Introduce Pulsar metadata CLI tool
PIP-124Create init subscription before sending message to DLQ
PIP-129Introduce intermediate state for ledger deletion
PIP-130Apply redelivery backoff policy for ack timeout
PIP-131Resolve produce chunk messages failed when topic level maxMessageSize is set
PIP-132Include message header size when check maxMessageSize for non-batch message on the client side
PIP-135Include MetadataStore backend for Etcd
PIP-136Sync Pulsar policies across multiple clouds
PIP-137Pulsar Client Shared State API
PIP-143Support split bundle by specified boundaries
PIP-144Making SchemaRegistry implementation configurable
PIP-146ManagedCursorInfo compression
PIP-148Create Pulsar client release notes
PIP-149Making the REST Admin API fully async
PIP-152Support subscription level dispatch rate limiter setting
PIP-154Max active transaction limitation for transaction coordinator
PIP-155Drop support for Python2
PIP-156Build and Run Pulsar Server on Java 17
PIP-157Bucketing topic metadata to allow more topics per namespace
PIP-160Make transactions work more efficiently by aggregation operation for transaction log and pending ack store
PIP-161Exclusive Producer: new mode ExclusiveWithFencing
PIP-162LTS Releases
PIP-165Auto release client useless connections
PIP-173Create a built-in Function implementing the most common basic transformations
PIP-174Provide new implementation for broker dispatch cache
PIP-175Extend time based release process
PIP-176Refactor Doc Bot
PIP-177Add the classLoader field for SchemaDefinition
PIP-178Multiple snapshots for transaction buffer
PIP-179Support the admin API to check unknown request parameters
PIP-180Shadow Topic, an alternative way to support readonly topic ownership
PIP-181Pulsar Shell
PIP-182Provide new load balance placement strategy implementation for ModularLoadManagerStrategy
PIP-183Reduce unnecessary REST call in broker
PIP-184Topic specific consumer priorityLevel
PIP-186Introduce two phase deletion protocol based on system topic
PIP-187Add API to analyse a subscription backlog and provide a accurate value
PIP-188Cluster migration or Blue-Green cluster deployment support in Pulsar
PIP-189No batching if only one message in batch
PIP-190Simplify documentation release and maintenance strategy
PIP-191Support batched message using entry filter
PIP-192New Pulsar Broker Load Balancer
PIP-193Sink preprocessing Function
PIP-194Pulsar client: seek command add epoch
PIP-195New bucket based delayed message tracker
PIP-198Standardize PR Naming Convention using GitHub Actions
PIP-201Extensions mechanism for Pulsar Admin CLI tools
PIP-204Extensions for broker interceptor
PIP-205Reactive Java client for Apache Pulsar
PIP-209Separate C++/Python clients to own repositories
PIP-243Register Jackson Java 8 support modules by default
PIP-249Pulsar website redesign
PIP-259Make the config httpMaxRequestHeaderSize of the pulsar web server to configurable
PIP-261Restructure Getting Started section
PIP-264Support OpenTelemetry metrics in Pulsar
PIP-265PR-based system for managing and reviewing PIPs
PIP-275Rename numWorkerThreadsForNonPersistentTopic to topicOrderedExecutorThreadNum
PIP-276Add pulsar prefix to topic_load_times metric
PIP-277Add current cluster marking to clusters list command
PIP-278Pluggable topic compaction service
PIP-279Support topic-level policies using TableView API
PIP-280Refactor CLI Argument Parsing Logic for Measurement Units using JCommander's custom converter
PIP-281Add notifyError method on PushSource
PIP-282Add Key_Shared subscription initial position support
PIP-284Migrate topic policies implementation to use TableView
PIP-286Support get position based on timestamp with topic compaction
PIP-289Secure Pulsar Connector Configuration
PIP-290Support message encryption in WebSocket proxy
PIP-292Enforce token expiration time in the Websockets plugin
PIP-293Support reader to read compacted data
PIP-296Add getLastMessageIds API for Reader
PIP-297Support terminating Function & Connector with the fatal exception
PIP-298Support read transaction buffer snapshot segments from earliest
PIP-299Support setting max unacked messages at subscription level
PIP-300Add RedeliverCount field to CommandAck
PIP-301Separate load data storage from configuration metadata store
PIP-302Support for TableView with strong read consistency
PIP-303Support PartitionedTopicStats exclude publishers and subscriptions
PIP-305Add OpAddEntry and pendingData statistics info in JVM metrics
PIP-306Support subscribing multi topics for WebSocket
PIP-307Optimize Bundle Unload(Transfer) Protocol for ExtensibleLoadManager
PIP-312Use StateStoreProvider to manage state in Pulsar Functions endpoints
PIP-313Support force unsubscribe using consumer api
PIP-315Configurable max delay limit for delayed delivery
PIP-318Don't retain null-key messages during topic compaction
PIP-320OpenTelemetry Scaffolding
PIP-321Split the responsibilities of namespace replication-clusters
PIP-322Pulsar Rate Limiting Refactoring
PIP-323Complete Backlog Quota Telemetry
PIP-324Switch to Alpine Linux base Docker images
PIP-325Support reading from transaction buffer for pending transaction
PIP-326Create a BOM to ease dependency management
PIP-327Support force topic loading for unrecoverable errors
PIP-329Strategy for maintaining the latest tag to Pulsar docker images
PIP-330getMessagesById gets all messages
PIP-335Support Oxia metadata store plugin
PIP-337SSL Factory Plugin to customize SSLContext/SSLEngine generation
PIP-339Introducing the --log-topic Option for Pulsar Sinks and Sources
PIP-342Support OpenTelemetry metrics in Pulsar client
PIP-343Use picocli instead of jcommander
PIP-344Correct the behavior of the public API pulsarClient.getPartitionsForTopic(topicName)
PIP-347add role field in consumer's stat
PIP-348Trigger offload on topic load stage
PIP-349Add additionalSystemCursorNames ignore list for ttl check
PIP-350Allow to disable the managedLedgerOffloadDeletionLagInMillis
PIP-351Additional options for Pulsar-Test client to support KeyStore based TLS
PIP-352Event time based topic compactor
PIP-353Improve transaction message visibility for peek-messages cli
PIP-354apply topK mechanism to ModularLoadManagerImpl
PIP-355Enhancing Broker-Level Metrics for Pulsar
PIP-356Support Geo-Replication starts at earliest position
PIP-357Correct the conf name in load balance module.
PIP-358let resource weight work for OverloadShedder, LeastLongTermMessageRate, ModularLoadManagerImpl.
PIP-359Support custom message listener executor for specific subscription
PIP-360Admin API to display Schema metadata
PIP-363Add callback parameters to the method: org.apache.pulsar.client.impl.SendCallback.sendComplete.
PIP-364Introduce a new load balance algorithm AvgShedder
PIP-366Support to specify different config for Configuration and Local Metadata Store
PIP-367Propose a Contributor Repository for Pulsar
PIP-368Support lookup based on the lookup properties
PIP-369Flag based selective unload on changing ns-isolation-policy
PIP-370configurable remote topic creation in geo-replication
PIP-373Add a topic's system prop that indicates whether users have published TXN messages in before.
PIP-374Visibility of messages in receiverQueue for the consumers
PIP-376Make Topic Policies Service Pluggable
PIP-378Add ServiceUnitStateTableView abstraction (ExtensibleLoadMangerImpl only)
PIP-379Key_Shared Draining Hashes for Improved Message Ordering
PIP-380Support setting up specific namespaces to skipping the load-shedding
PIP-381Handle large PositionInfo state
PIP-383Support granting/revoking permissions for multiple topics
PIP-384ManagedLedger interface decoupling
PIP-389Add Producer config compressMinMsgBodySize to improve compression performance
PIP-391Improve Batch Messages Acknowledgment
PIP-392Add configuration to enable consistent hashing to select active consumer for partitioned topic
PIP-393Improve performance of Negative Acknowledgement
PIP-395Add Proxy configuration to support configurable response headers for http reverse-proxy
PIP-396Align WindowFunction's WindowContext with BaseContext
PIP-399Fix Metric Name for Delayed Queue
PIP-401Support set batching configurations for Pulsar Functions&Sources
PIP-402Role Anonymizer for Pulsar Logging
PIP-404Introduce per-ledger properties
PIP-406Introduce metrics related to dispatch throttled events
PIP-407Add a newMessage API to create a message with a schema and transaction
PIP-409support producer configuration for retry/dead letter topic producer
PIP-412Support setting messagePayloadProcessor in Pulsar Functions and Sinks
PIP-414Enforce topic consistency check
PIP-415Support getting message ID by index
PIP-416Add a new topic method to implement trigger offload by size threshold
PIP-420Provides an ability for Pulsar clients to integrate with third-party schema registry service
PIP-421Require Java 17 as the minimum for Pulsar Java client SDK
PIP-422Support global topic-level policy: replicated clusters and new API to delete topic-level policies
PIP-425Support connecting with next available endpoint for multi-endpoint serviceUrls
PIP-427Align pulsar-admin Default for Mark-Delete Rate with Broker Configuration
PIP-428Change TopicPoliciesService interface to fix consistency issues
PIP-429Optimize Handling of Compacted Last Entry by Skipping Payload Buffer Parsing
PIP-430Pulsar Broker cache improvements: refactoring eviction and adding a new cache strategy based on expected read count
PIP-431Add Creation and Last Publish Timestamps to Topic Stats
PIP-432Add isEncrypted field to EncryptionContext
PIP-433Optimize the conflicts of the replication and automatic creation mechanisms, including the automatic creation of topics and schemas
PIP-435Add startTimestamp and endTimestamp for consuming messages in client cli
PIP-436Add decryptFailListener to Consumer

Additional Information

  1. You can view all PIPs (besides the historical ones) as the list of Pull Requests having title starting with [improve][pip] PIP-. Here is the link for it.
    • Merged PR means the PIP was accepted.
    • Closed PR means the PIP was rejected.
    • Open PR means the PIP was submitted and is in the process of discussion.
  2. All PIP files in the pip folder follow the naming convention pip-xxx.md where xxx is the PIP number.