Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion antora.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ asciidoc:
pulsar: 'Apache Pulsar'
pulsar-short: 'Pulsar'
product: 'Starlight for JMS'
luna-streaming: 'Luna Streaming'
luna-streaming: 'IBM Elite Support for Apache Pulsar'
astra-stream: 'Astra Streaming'
activemq-reg: 'Apache ActiveMQ(R)'
activemq-short: 'ActiveMQ'
Expand Down
5 changes: 3 additions & 2 deletions modules/examples/pages/pulsar-jms-server-side-filters.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ Server-side filtering offloads the filtering to the Broker nodes and includes th

== Limitations

* **Required version**: Server-side filtering requires {pulsar-short} version 2.10.1 or later, or {luna-streaming} version 2.10 or later.
* **Required version**: Server-side filtering requires {pulsar-short} version 2.10.1 or later, or {luna-streaming} (formerly DataStax Luna Streaming) version 2.10 or later.

* *Batch messages*: Server-side filtering works on the entry level in {pulsar-short}.
An _entry_ is a single message, or a single batch of messages.
Expand Down Expand Up @@ -41,7 +41,8 @@ For the same reason, {product} doesn't support custom formats like native {kafka

== Enable server-side filtering

The `.nar` file filter is packaged with {luna-streaming} *2.10.03+* and also available in the GitHub repo {jms_repo}/releases[here].
The `.nar` file filter is packaged with {luna-streaming} version 2.10.03 and later.
It is also available in the {jms_repo}/releases[{product} GitHub repository].

. Install {product} with the fat JAR that includes all dependencies.
Put the `.nar` file in `/pulsar/filters`.
Expand Down
7 changes: 6 additions & 1 deletion modules/jms-migration/pages/pulsar-jms-install.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -40,9 +40,14 @@ Typically, the latest {product} version is compatible with the {pulsar-short} ve
{luna-streaming}::
+
--
[TIP]
====
{luna-streaming} was formerly DataStax Luna Streaming.
====

* To use Transactions with {luna-streaming} 2.8.x, you must use {product} version 1.x.
* To use Transactions with {luna-streaming} 2.10.x or later, you must use {product} version 2.x or later.
* To use server-side filtering with {luna-streaming}, you must use {luna-streaming} 2.10.0 or later and {product} 2.x or later.
* To use server-side filtering, you must use {luna-streaming} 2.10.0 or later _and_ {product} 2.x or later.
--

Self-managed::
Expand Down
8 changes: 4 additions & 4 deletions modules/jms-migration/pages/pulsar-jms-quickstart-sa.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -30,11 +30,11 @@ If you don't have these structures configured in {astra-stream}, see the xref:as
{luna-streaming}::
+
--
To use {product} with a {luna-streaming} {pulsar-short} cluster, you need the following:
To use {product} with {luna-streaming} (formerly DataStax Luna Streaming), you need the following:

* A {luna-streaming} {pulsar-short} cluster.
* An {luna-streaming} cluster.
+
If you don't have a {luna-streaming} cluster, see the xref:luna-streaming:install-upgrade:quickstart-helm-installs.adoc[{luna-streaming} installation guide].
To create a cluster, see the xref:luna-streaming:install-upgrade:quickstart-helm-installs.adoc[{luna-streaming} installation guide].

* Access to the cluster's admin port 8080 and the binary port 6650.
+
Expand Down Expand Up @@ -326,7 +326,7 @@ Received: Hello world! 9
[pulsar-client-io-5-1] INFO org.apache.pulsar.client.impl.ClientCnx - [id: 0xe43071e3, L:/127.0.0.1:65236 ! R:localhost/127.0.0.1:6650] Disconnected
----

. Use the {pulsar-short} Admin CLI or the {luna-streaming} {pulsar-short} Admin Console to inspect your tenant's activity, and verify that messages were published and consumed on the specified topic.
. Use the {pulsar-short} Admin CLI or the {luna-streaming} Admin Console to inspect your tenant's activity, and verify that messages were published and consumed on the specified topic.
--

Self-managed::
Expand Down