You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/astream-faq.adoc
+4-4
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ See xref:getting-started:index.adoc[].
10
10
11
11
See xref:operations:astream-pricing.adoc[].
12
12
13
-
== Why is {product} based on Apache Pulsar?
13
+
== Why is {product} based on {pulsar-reg}?
14
14
15
-
For information about the decision to use Apache Pulsar, see https://www.datastax.com/blog/four-reasons-why-apache-pulsar-essential-modern-data-stack[Four Reasons Why Apache Pulsar is Essential to the Modern Data Stack].
15
+
For information about the decision to use {pulsar}, see https://www.datastax.com/blog/four-reasons-why-apache-pulsar-essential-modern-data-stack[Four Reasons Why {pulsar} is Essential to the Modern Data Stack].
16
16
17
17
== What happened to Kesque?
18
18
@@ -26,11 +26,11 @@ With the launch of {product}, {company} began shutting down the Kesque service a
26
26
27
27
The pricing model also makes {product} accessible to mid market and small/medium business customers who need event stream processing capabilities to run core parts of their business.
28
28
29
-
And finally {product} offers a user-friendly interface and free tier to satisfy the needs of individual developers and technologists who want to learn more about Apache Pulsar and data streaming in general.
29
+
And finally {product} offers a user-friendly interface and free tier to satisfy the needs of individual developers and technologists who want to learn more about {pulsar} and data streaming in general.
30
30
31
31
== What is CDC for {astra_db}?
32
32
33
-
Change Data Capture (CDC) for {astra_db} uses a Pulsar IO source connector that processes changes from the Cassandra Change Agent through a Pulsar topic.
33
+
Change Data Capture (CDC) for {astra_db} uses a {pulsar-short} IO source connector that processes changes from the Cassandra Change Agent through a {pulsar-short} topic.
34
34
For more information, see xref:developing:astream-cdc.adoc[].
35
35
36
36
== What are tenants, namespaces, topics, and sinks?
Copy file name to clipboardExpand all lines: modules/ROOT/pages/astream-org-permissions.adoc
+8-8
Original file line number
Diff line number
Diff line change
@@ -36,22 +36,22 @@ Additional permissions might be required, depending on the tasks the role needs
36
36
To control access to specific streaming tenants, you can set granular xref:astra-db-serverless:administration:manage-database-access.adoc#role-scopes[resource scopes] on custom roles.
37
37
====
38
38
39
-
== Authentication and authorization in Pulsar and {astra_db}
39
+
== Authentication and authorization in {pulsar-reg} and {astra_db}
40
40
41
-
Pulsar has the concept of https://pulsar.apache.org/docs/security-authorization/[clients with role tokens].
42
-
In Pulsar, authentication is the process of verifying a provided token (JWT), and authorization is the process of determining if the role claimed in that token is allowed to complete the requested action.
41
+
{pulsar-short} has the concept of https://pulsar.apache.org/docs/security-authorization/[clients with role tokens].
42
+
In {pulsar-short}, authentication is the process of verifying a provided token (JWT), and authorization is the process of determining if the role claimed in that token is allowed to complete the requested action.
43
43
44
-
{product} uses the {company} version of Apache Pulsar (xref:luna-streaming::index.adoc[Luna Streaming]).
45
-
The https://github.com/datastax/pulsar[Luna project] is an open fork of the Pulsar project that maintains feature parity with OSS Pulsar. {product}, as a managed service, abstracts some features/options of Pulsar to ensure continuous, reliable service.
44
+
{product} uses the {company} version of {pulsar} (xref:luna-streaming::index.adoc[Luna Streaming]).
45
+
The https://github.com/datastax/pulsar[Luna project] is an open fork of the {pulsar-short} project that maintains feature parity with OSS {pulsar-short}. {product}, as a managed service, abstracts some features/options of {pulsar-short} to ensure continuous, reliable service.
46
46
47
-
On a shared cluster, your {astra_db} organization has one or more tenants on a shared Pulsar cluster.
48
-
Each of your tenants is secured by Pulsar authentication and authorization models, as well as your {astra_db} organization's authentication and authorization ({astra_db} RBAC).
47
+
On a shared cluster, your {astra_db} organization has one or more tenants on a shared {pulsar-short} cluster.
48
+
Each of your tenants is secured by {pulsar-short} authentication and authorization models, as well as your {astra_db} organization's authentication and authorization ({astra_db} RBAC).
49
49
50
50
{product} shared clusters are created and administered by {product} administrators.
51
51
Each tenant is assigned a custom role and permissions limited to that tenant only.
52
52
All tokens created within a tenant are assigned roles similar to the assigning tenant.
53
53
54
-
For programmatic access, you use {astra_db} application tokens or Pulsar JWT, depending on the operation you need to perform.
54
+
For programmatic access, you use {astra_db} application tokens or {pulsar-short} JWT, depending on the operation you need to perform.
55
55
For more information, see xref:operations:astream-token-gen.adoc[].
_Subscriptions_ in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data.
5
+
_Subscriptions_ in {pulsar-reg} describe which consumers are consuming data from a topic and how they want to consume that data.
6
6
7
7
An _exclusive subscription_ describes a basic publish-subscribe (pub-sub) pattern where a single consumer subscribes to a single topic and consumes from it.
8
8
9
-
This page explains how to use Pulsar's exclusive subscription model to manage your topic consumption.
9
+
This page explains how to use {pulsar-short}'s exclusive subscription model to manage your topic consumption.
10
10
11
11
include::ROOT:partial$subscription-prereq.adoc[]
12
12
13
13
[#example]
14
14
== Exclusive subscription example
15
15
16
-
. To configure a Pulsar exclusive subscription, define a `pulsarConsumer` object in `SimplePulsarConsumer.java`, as you would for other subscription types.
16
+
. To configure a {pulsar-short} exclusive subscription, define a `pulsarConsumer` object in `SimplePulsarConsumer.java`, as you would for other subscription types.
17
17
However, you don't need to declare a `subscriptionType`.
18
-
Whereas other subscription types required you to declare a specific `subscriptionType`, Pulsar creates an exclusive subscription by default if you don't declare a `subscriptionType`.
18
+
Whereas other subscription types required you to declare a specific `subscriptionType`, {pulsar-short} creates an exclusive subscription by default if you don't declare a `subscriptionType`.
_Subscriptions_ in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data.
5
+
_Subscriptions_ in {pulsar-reg} describe which consumers are consuming data from a topic and how they want to consume that data.
6
6
7
7
If an xref:astream-subscriptions-exclusive.adoc[exclusive] consumer fails, the topic backlog accumulates stale, unacknowledged messages.
8
-
Pulsar solves this problem with failover subscriptions.
9
-
In _failover subscriptions_, Pulsar designates one primary consumer and multiple standby consumers.
8
+
{pulsar-short} solves this problem with failover subscriptions.
9
+
In _failover subscriptions_, {pulsar-short} designates one primary consumer and multiple standby consumers.
10
10
If the primary consumer disconnects, the standby consumers begin consuming the subsequent unacknowledged messages.
11
11
12
-
This page explains how to use Pulsar's failover subscription model to manage your topic consumption.
12
+
This page explains how to use {pulsar-short}'s failover subscription model to manage your topic consumption.
13
13
14
14
include::ROOT:partial$subscription-prereq.adoc[]
15
15
16
16
[#example]
17
17
== Failover subscription example
18
18
19
-
To try out a Pulsar failover subscription, add `.subscriptionType(SubscriptionType.Failover)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
19
+
To try out a {pulsar-short} failover subscription, add `.subscriptionType(SubscriptionType.Failover)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
20
20
21
21
.SimplePulsarConsumer.java
22
22
[source,java]
@@ -86,7 +86,7 @@ To test them, you can progressively end each `SimplePulsarConsumer` process, and
86
86
87
87
== See also
88
88
89
-
* xref:astream-subscriptions.adoc[Subscriptions in Pulsar]
_Subscriptions_ in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data.
5
+
_Subscriptions_ in {pulsar-reg} describe which consumers are consuming data from a topic and how they want to consume that data.
6
6
7
-
Pulsar's xref:astream-subscriptions-shared.adoc[shared subscription] model can increase the message processing rate, but it risks losing message ordering guarantees.
7
+
{pulsar-short}'s xref:astream-subscriptions-shared.adoc[shared subscription] model can increase the message processing rate, but it risks losing message ordering guarantees.
8
8
In a round-robin delivery, there's no way for the broker to know which messages are going to which consumer.
9
9
10
10
_Key shared subscriptions_ allow multiple consumers to subscribe to a topic, and provide additional metadata in the form of _keys_ that link messages to specific consumers.
@@ -13,14 +13,14 @@ Keys are generated with hashing that converts arbitrary values like `topic-name`
13
13
* *Auto hash*: Uses _consistent hashing_ to balance range values across available consumers without requiring manual setup of hash ranges.
14
14
* *Sticky hash*: The client manually assigns consumer range values, and then all hashes within a configured range go to one consumer.
15
15
16
-
This page explains how to use Pulsar's key shared subscription model to manage your topic consumption.
16
+
This page explains how to use {pulsar-short}'s key shared subscription model to manage your topic consumption.
17
17
18
18
include::ROOT:partial$subscription-prereq.adoc[]
19
19
20
20
[#example]
21
21
== Key shared subscription example
22
22
23
-
. To try out a Pulsar key shared subscription, add `.subscriptionType(SubscriptionType.Key_Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
23
+
. To try out a {pulsar-short} key shared subscription, add `.subscriptionType(SubscriptionType.Key_Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
24
24
+
25
25
.SimplePulsarConsumer.java
26
26
[source,java]
@@ -144,7 +144,7 @@ Then, you can launch multiple instances of `SimplePulsarConsumer.java` to consum
144
144
145
145
== See also
146
146
147
-
* xref:astream-subscriptions.adoc[Subscriptions in Pulsar]
_Subscriptions_ in Pulsar describe which consumers are consuming data from a topic and how they want to consume that data.
5
+
_Subscriptions_ in {pulsar-reg} describe which consumers are consuming data from a topic and how they want to consume that data.
6
6
7
7
A _shared subscription_ allows multiple consumers to consume messages from a single topic in a round-robin fashion.
8
-
More consumers in a shared subscription can increase your Pulsar deployment's rate of message consumption.
8
+
More consumers in a shared subscription can increase your {pulsar-short} deployment's rate of message consumption.
9
9
However, there is a risk of losing message ordering guarantees and acknowledgment schemes.
10
10
11
-
This page explains how you can use Pulsar's shared subscription model to manage your topic consumption.
11
+
This page explains how you can use {pulsar-short}'s shared subscription model to manage your topic consumption.
12
12
13
13
include::ROOT:partial$subscription-prereq.adoc[]
14
14
15
15
[#example]
16
16
== Shared subscription example
17
17
18
-
To try out a Pulsar shared subscription, add `.subscriptionType(SubscriptionType.Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
18
+
To try out a {pulsar-short} shared subscription, add `.subscriptionType(SubscriptionType.Shared)` to the `pulsarConsumer` in `SimplePulsarConsumer.java`:
19
19
20
20
.SimplePulsarConsumer.java
21
21
[source,java]
@@ -85,7 +85,7 @@ All the consumers subscribe to the topic and consume messages in a round-robin f
85
85
86
86
== See also
87
87
88
-
* xref:astream-subscriptions.adoc[Subscriptions in Pulsar]
0 commit comments