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-org-permissions.adoc
+7-7
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,8 @@
2
2
:navtitle: Manage roles and permissions
3
3
:page-tag: astra-streaming,security,secure,pulsar
4
4
5
-
You manage role-based access control (RBAC) for {product} through your {astra-db} organization.
6
-
For information about {astra-db} RBAC, including default roles, custom roles, permissions, and user management, see xref:astra-db-serverless:administration:manage-database-access.adoc[].
5
+
You manage role-based access control (RBAC) for {product} through your {product-short} organization.
6
+
For information about {product-short} RBAC, including default roles, custom roles, permissions, and user management, see xref:astra-db-serverless:administration:manage-database-access.adoc[].
7
7
8
8
== {product} permissions
9
9
@@ -13,7 +13,7 @@ Permissions specific to {product} include the following:
13
13
14
14
=== Default roles for {product}
15
15
16
-
There are no default {astra-db} roles specifically scoped to {product}.
16
+
There are no default {product-short} roles specifically scoped to {product}.
17
17
However, the following default roles have the *Manage Streaming* permission:
18
18
19
19
* *Organization Administrator*
@@ -37,22 +37,22 @@ Additional permissions might be required, depending on the tasks the role needs
37
37
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.
38
38
====
39
39
40
-
== Authentication and authorization in {pulsar-reg} and {astra-db}
40
+
== Authentication and authorization in {pulsar-reg} and {product-short}
41
41
42
42
{pulsar-short} has the concept of https://pulsar.apache.org/docs/security-authorization/[clients with role tokens].
43
43
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.
44
44
45
45
{product} uses the {company} version of {pulsar} (xref:luna-streaming::index.adoc[Luna Streaming]).
46
46
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.
47
47
48
-
On a shared cluster, your {astra-db} organization has one or more tenants on a shared {pulsar-short} cluster.
49
-
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).
48
+
On a shared cluster, your {product-short} organization has one or more tenants on a shared {pulsar-short} cluster.
49
+
Each of your tenants is secured by {pulsar-short} authentication and authorization models, as well as your {product-short} organization's authentication and authorization ({product-short} RBAC).
50
50
51
51
{product} shared clusters are created and administered by {product} administrators.
52
52
Each tenant is assigned a custom role and permissions limited to that tenant only.
53
53
All tokens created within a tenant are assigned roles similar to the assigning tenant.
54
54
55
-
For programmatic access, you use {astra-db} application tokens or {pulsar-short} JWT, depending on the operation you need to perform.
55
+
For programmatic access, you use {product-short} application tokens or {pulsar-short} JWT, depending on the operation you need to perform.
56
56
For more information, see xref:operations:astream-token-gen.adoc[].
Copy file name to clipboardExpand all lines: modules/apis/pages/index.adoc
+2-2
Original file line number
Diff line number
Diff line change
@@ -6,9 +6,9 @@ You use two APIs to manage {pulsar-reg} tenants and their resources.
6
6
7
7
== {product}{devops-api}
8
8
9
-
Use the xref:astra-streaming:apis:attachment$devops.html[{product} {devops-api}] to manage higher-level {product} objects associated with your {astra-db} organization, such as the Change Data Capture (CDC) settings, {pulsar-short} tenants, geo-replications, {pulsar-short} stats, and {pulsar-short} tokens.
9
+
Use the xref:astra-streaming:apis:attachment$devops.html[{product} {devops-api}] to manage higher-level {product} objects associated with your {product-short} organization, such as the Change Data Capture (CDC) settings, {pulsar-short} tenants, geo-replications, {pulsar-short} stats, and {pulsar-short} tokens.
10
10
11
-
This API uses an {astra-db} application token for authentication.
11
+
This API uses an {product-short} application token for authentication.
Copy file name to clipboardExpand all lines: modules/developing/pages/astra-cli.adoc
+3-3
Original file line number
Diff line number
Diff line change
@@ -2,14 +2,14 @@
2
2
:navtitle: {astra-cli}
3
3
:description: {astra-cli} provides a one-stop shop for managing your Astra resources through scripts or commands in your local terminal.
4
4
5
-
The xref:astra-cli:ROOT:index.adoc[{astra-db} Command-Line Interface ({astra-cli})] is a set of commands you can use to create and manage {astra-db} and {product} resources:
5
+
The xref:astra-cli:ROOT:index.adoc[{product-short} Command-Line Interface ({astra-cli})] is a set of commands you can use to create and manage {product-short} and {product} resources:
6
6
7
7
* Creation and management of {astra-db} databases, {astra_stream} tenants, and their associated artifacts.
8
8
* Querying and data loading.
9
9
* Organization and user management.
10
10
* Security and token configuration.
11
11
12
-
{astra-cli} commands are available for {astra-db} and {astra_stream}.
12
+
{astra-cli} commands are available for {product-short} and {astra_stream}.
13
13
They're designed to get you working quickly, with an emphasis on automation.
14
14
15
15
For example, the following command creates an {pulsar-reg} tenant:
A response of `Created Successfully!` indicates the function is deployed and ready to accept messages.
251
251
252
-
If the response is `402 Payment Required` with `Reason: only qualified organizations can create functions`, then you must upgrade to a xref:operations:astream-pricing.adoc[paid {product} plan].
252
+
If the response is `402 Payment Required` with `Reason: only qualified organizations can create functions`, then you must upgrade to a xref:operations:astream-pricing.adoc[paid {product-short} plan].
253
253
Organizations on the *Free* plan can use xref:streaming-learning:functions:index.adoc[transform functions] only.
254
254
====
255
255
+
@@ -287,7 +287,7 @@ See <<controlling-your-function,Controlling your function>> for more information
287
287
288
288
== Deploy functions in the {astra-ui}
289
289
290
-
. In the {astra-ui} navigation menu, click *Streaming*, and then select a tenant.
290
+
. In the {astra-ui} navigation menu, click *Streaming*, and then click the name of the tenant where you want to deploy a function.
291
291
292
292
. On the *Functions* tab, click *Create Function*.
293
293
@@ -311,7 +311,7 @@ Upload your own code::
311
311
312
312
.. Based on the uploaded file, select the specific class (function) to deploy.
313
313
+
314
-
{astra-db} generates a list of acceptable classes detected in the code.
314
+
{product-short} generates a list of acceptable classes detected in the code.
315
315
A file can contain multiple classes, but only one is used per deployment.
316
316
+
317
317
For Python scripts, the class name is the Python filename (without the extension) and the class to execute.
@@ -336,9 +336,9 @@ For more information, see xref:streaming-learning:functions:index.adoc[] and xre
336
336
337
337
. Select input topics.
338
338
339
-
. (Optional) Select output and log topics.
339
+
. Optional: Select output and log topics.
340
340
341
-
. (Optional) Configure advanced settings:
341
+
. Optional: Configure advanced settings.
342
342
+
343
343
* *Instances*: Enter a number of sink instances to run.
344
344
* *Processing Guarantee*: Select one of the following:
@@ -349,7 +349,7 @@ This means there is a change that a message is not processed.
349
349
* *Timeout*: Set a timeout limit.
350
350
* *Auto Acknowledge*: Enable or disable automatic message acknowledgment.
351
351
352
-
. (Optional) Provide a config key, if required.
352
+
. Optional: Provide a config key, if required.
353
353
For more information, see the https://pulsar.apache.org/functions-rest-api/#operation/registerFunction[{pulsar-short} documentation].
Copy file name to clipboardExpand all lines: modules/developing/pages/clients/spring-produce-consume.adoc
+1-1
Original file line number
Diff line number
Diff line change
@@ -101,7 +101,7 @@ Message received: Hello World
101
101
----
102
102
====
103
103
104
-
. In the {astra-ui}, go to your tenant to verify that the message appears in the specified namespace and topic.
104
+
. In the {astra-ui} navigation menu, click *Streaming*, click the name of your tenant, and then verify that the message appears in the specified namespace and topic.
Copy file name to clipboardExpand all lines: modules/developing/pages/gpt-schema-translator.adoc
+2-2
Original file line number
Diff line number
Diff line change
@@ -23,9 +23,9 @@ The {gpt-schema-translator} is available for the {astra-db} sink connector only.
23
23
This example uses a JSON schema for a {pulsar-short} topic, and a CQL schema for an {astra-db} table.
24
24
The {gpt-schema-translator} generates a mapping between the two schemas that the {astra-db} sink connector can use to write data from the {pulsar-short} topic to the {astra-db} table.
25
25
26
-
. In the {astra-ui} navigation menu, click *Streaming*, and then select your tenant.
26
+
. In the {astra-ui} navigation menu, click *Streaming*, and then click the name of your tenant.
27
27
28
-
. On the *Namespaces and Topics* tab, locate the topic that you want to map to a table, and then click *Create mapping*.
28
+
. On the *Namespaces and Topics* tab, find the topic that you want to map to a table, and then click *Create mapping*.
29
29
30
30
. Select your database's keyspace, and then enter the name of the table that you want to map to.
Copy file name to clipboardExpand all lines: modules/operations/pages/astream-limits.adoc
+13-13
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@
4
4
{product} includes guardrails and limits to ensure best practices, foster availability, and promote optimal configurations for your databases.
5
5
6
6
Unless otherwise noted, the following limits apply to shared clusters.
7
-
In general, xref:operations:astream-pricing.adoc#dedicated-clusters[dedicated clusters] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support_url}[{company} Support].
7
+
In general, xref:operations:astream-pricing.adoc#dedicated-clusters[Streaming Capacity Units] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support_url}[{company} Support].
8
8
9
9
== {product} guardrails
10
10
11
11
Guardrails are provisioned in the default settings for {product}.
12
12
You can't directly change these guardrails.
13
-
For dedicated clusters, some guardrails can be changed by contacting {support_url}[{company} Support].
13
+
For Streaming Capacity Units, some guardrails can be changed by contacting {support_url}[{company} Support].
14
14
15
15
[cols="1,1,1"]
16
16
|===
@@ -19,7 +19,7 @@ For dedicated clusters, some guardrails can be changed by contacting {support_ur
19
19
|Number of tenants per organization
20
20
a|
21
21
* Shared clusters: 10
22
-
* Dedicated clusters: Unlimited
22
+
* Streaming Capacity Units: Unlimited
23
23
24
24
|This limit can't be changed for shared clusters.
25
25
@@ -30,32 +30,32 @@ a|
30
30
|Number of topics per namespace
31
31
a|
32
32
* Shared clusters: 100
33
-
* Dedicated clusters: 5000
33
+
* Streaming Capacity Units: 5000
34
34
|
35
35
36
36
|Max message size
37
37
a|
38
38
* Shared clusters: 5MB
39
-
* Dedicated clusters: Customizable
39
+
* Streaming Capacity Units: Customizable
40
40
|
41
41
42
42
|Max throughput per topic for consumers
43
43
a|
44
44
* Shared clusters: 5000 messages per second, 25MB per second
45
-
* Dedicated clusters: Customizable
45
+
* Streaming Capacity Units: Customizable
46
46
|This limit applies to non-partitioned topics and individual partitions of partitioned topics.
47
47
48
48
|Max throughput per topic for producers
49
49
a|
50
50
* Shared clusters: 5000 messages per second, 25MB per second
51
-
* Dedicated clusters: Customizable
51
+
* Streaming Capacity Units: Customizable
52
52
|This limit applies to non-partitioned topics and individual partitions of partitioned topics, regardless of the number of producers to a topic.
53
53
If there are multiple producers to a topic, they can produce a _combined maximum_ of 5000 messages per second.
54
54
55
55
|Max throughput per topic for subscriptions
56
56
a|
57
57
* Shared clusters: 5000 messages per second, 25MB per second
58
-
* Dedicated clusters: Customizable
58
+
* Streaming Capacity Units: Customizable
59
59
|This limit applies to non-partitioned topics and individual partitions of partitioned topics, regardless of the number of subscribers to a topic.
60
60
If there are multiple subscriptions to a topic, they can dispatch a _combined maximum_ of 5000 messages per second.
61
61
@@ -70,19 +70,19 @@ If there are multiple subscriptions to a topic, they can dispatch a _combined ma
70
70
|Number of producers per topic
71
71
a|
72
72
* Shared clusters: 50
73
-
* Dedicated clusters: 500
73
+
* Streaming Capacity Units: 500
74
74
|
75
75
76
76
|Number of consumers per topic
77
77
a|
78
78
* Shared clusters: 50
79
-
* Dedicated clusters: 500
79
+
* Streaming Capacity Units: 500
80
80
|
81
81
82
82
|Number of subscriptions per topic
83
83
a|
84
84
* Shared clusters: 50
85
-
* Dedicated clusters: 500
85
+
* Streaming Capacity Units: 500
86
86
|
87
87
88
88
|Max unacknowledged messages per consumer
@@ -314,12 +314,12 @@ The default settings are as follows:
314
314
|===
315
315
|Cluster type |CPU per instance |RAM per instance |Maximum function instances per namespace
0 commit comments