apache / pulsar

Pulsar is a distributed pub-sub messaging platform with a very flexible messaging model and an intuitive client API. Learn more about Pulsar at https://pulsar.apache.org Main features • Horizontally scalable (Millions of independent topics and millions of messages published per second) • Strong ordering and consistency guarantees • Low latency durable storage • Topic and queue semantics • Load balancer • Designed for being deployed as a hosted service: • Multi-tenant • Authentication • Authorization • Quotas • Support mixing very different workloads • Optional hardware isolation • Keeps track of consumer cursor position • REST API for provisioning, admin and stats • Geo replication • Transparent handling of partitioned topics • Transparent batching of messages Repositories This repository is the main repository of Apache Pulsar. Pulsar PMC also maintains other repositories for components in the Pulsar ecosystem, including connectors, adapters, and other language clients. • Pulsar Core Helm Chart • Pulsar Helm Chart Ecosystem • Pulsar Adapters Clients • .NET/C# Client • C++ Client • Go Client • NodeJS Client • Python Client • Reactive Java Client Dashboard & Management Tools • Dekaf UI • Pulsar Manager Website • Pulsar Site CI/CD • Pulsar CI Archived/Halted • Pulsar Connectors (bundled as pulsar-io) • Pulsar Translation • Pulsar SQL (Pulsar Presto Connector) (bundled as pulsar-sql) • Ruby Client Pulsar Runtime Java Version Recommendation > **Note**: > > When using Java versions, it is recommended to > use a recent version of a particular Java release (17 or 21) > with the most recent bug fixes and security patches. > For example, the JVM bug JDK-8351933 can cause stability issues in > Pulsar. > JDK-8351933 was fixed in Java 17.0.17+ and Java 21.0.8+. > Pulsar Docker images come with the most recent Java version at the time of release. When using the Pulsar Java client, it is recommended to set specific system properties and JVM options to allow optimal performance. pulsar ver >= 4.1 and master branch | Component | Java Version | |-----------------|:------------:| | Broker | 21 | | Functions / IO | 21 | | CLI | 17 or 21 | | Java Client | 17 or 21 | Docker image Java runtime: 21 3.3 **Note**: > > This project includes a Maven Wrapper that can be used instead of a system-installed Maven. > Use it by replacing by on Linux and on Windows in the commands below. Build Compile and install: Compile and install individual module Minimal build (This skips most of external connectors and tiered storage handlers) Run Unit Tests: Run Individual Unit Test: Run Selected Test packages: Start standalone Pulsar service: Check https://pulsar.apache.org for documentation and examples. Build custom docker images The commands used in the Apache Pulsar release process can be found in the release process documentation. Here are some general instructions for building custom docker images: • Docker images must be built with Java 8 for or previous branches because of ISSUE-8445. • Java 11 is the recommended JDK version in , and . • Java 17 is the recommended JDK version in , and . • Java 21 is the recommended JDK version since . The following command builds the docker images and : After the images are built, they can be tagged and pushed to your custom repository. Here's an example of a bash script that tags the docker images with the current version and git revision and pushes them to . Setting up your IDE Read https://pulsar.apache.org/contribute/setup-ide for setting up IntelliJ IDEA or Eclipse for developing Pulsar. Documentation > **Note**: > > For how to make contributions to Pulsar documentation, see Pulsar Documentation Contribution Guide. Contact Mailing lists • The mailing lists are the primary contact for the Apache Pulsar project. • Your email to the mailing list might be placed in a moderation queue if you haven't joined the mailing list by subscribing before posting. > **Note** > > Please note that security-related issues or concerns should not be reported in public channels. > Follow the instructions in the Security Policy to contact the ASF Security Team and the Apache Pulsar PMC directly. | Name | Scope | Subscribe | Unsubscribe | Archives | |:----------------------------------------------------------|:--------------------------------|:------------------------------------------------------|:----------------------------------------------------------|:-------------------------------------------------------------------| | users@pulsar.apache.org | User-related discussions | Subscribe | Unsubscribe | Archives | | dev@pulsar.apache.org | Development-related discussions | Subscribe | Unsubscribe | Archives | Slack Pulsar slack channel at https://apache-pulsar.slack.com/ You can self-register at https://communityinviter.com/apps/apache-pulsar/apache-pulsar Security Policy If you find a security issue with Pulsar then please read the security policy. It is critical to avoid public disclosure. Reporting a security vulnerability To report a vulnerability for Pulsar, contact the Apache Security Team. When reporting a vulnerability to security@apache.org, you can copy your email to private@pulsar.apache.org to send your report to the Apache Pulsar Project Management Committee. This is a private mailing list. https://github.com/apache/pulsar/security/policy contains more details. License Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0 Crypto Notice This distribution includes cryptographic software. The country in which you currently reside may have restrictions on the import, possession, use, and/or re-export to another country, of encryption software. BEFORE using any encryption software, please check your country's laws, regulations and policies concerning the import, possession, or use, and re-export of encryption software, to see if this is permitted. See The Wassenaar Arrangement for more information. The U.S. G…