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
{{ message }}
This repository was archived by the owner on Feb 3, 2026. It is now read-only.
Starlight for RabbitMQ combines the AMQP 0.9.1 API with {pulsar-short}, providing a powerful way to modernize your RabbitMQ infrastructure, improve performance, and reduce costs.
61
+
{starlight-rabbitmq} combines the AMQP 0.9.1 API with {pulsar-short}, providing a powerful way to modernize your RabbitMQ infrastructure, improve performance, and reduce costs.
62
62
63
63
xref:streaming-learning:use-cases-architectures:starlight/rabbitmq/index.adoc[Get started now] | xref:starlight-for-rabbitmq:ROOT:index.adoc[Configuring] | https://github.com/datastax/starlight-for-rabbitmq[Source Code]
. Check results: Go to the {astra_ui} to see your newly deployed function listed under the “Functions” tab for your Tenant. See <<controlling-your-function,Controlling your function>> for more information on testing and monitoring your function in {product}.
118
+
. Check results: Go to the {astra-ui} to see your newly deployed function listed under the “Functions” tab for your Tenant. See <<controlling-your-function,Controlling your function>> for more information on testing and monitoring your function in {product}.
119
119
120
120
.. You can also use the pulsar-admin command to list your functions:
121
121
+
@@ -249,7 +249,7 @@ userConfig:
249
249
+
250
250
[NOTE]
251
251
====
252
-
{product} requires the “inputs” topic to have a message schema defined before deploying the function. Otherwise, deployment errors may occur. Use the {astra_ui} to define the message schema for a topic.
252
+
{product} requires the “inputs” topic to have a message schema defined before deploying the function. Otherwise, deployment errors may occur. Use the {astra-ui} to define the message schema for a topic.
253
253
====
254
254
+
255
255
. Use pulsar-admin to deploy your new JAR to {product} or {pulsar-short}.
@@ -260,7 +260,7 @@ The command below assumes you've properly configured the client.conf file for pu
. Check results: Go to the {astra_ui} to see your newly deployed function listed under the “Functions” tab for your Tenant. See <<controlling-your-function,Controlling your function>> for more information on testing and monitoring your function in {product}.
263
+
. Check results: Go to the {astra-ui} to see your newly deployed function listed under the “Functions” tab for your Tenant. See <<controlling-your-function,Controlling your function>> for more information on testing and monitoring your function in {product}.
264
264
265
265
.. You can also use the pulsar-admin command to list your functions:
266
266
+
@@ -280,7 +280,7 @@ image::astream-name-function.png[Function and Namespace]
280
280
281
281
. Select the file you want to pull the function from and which function you want to use within that file.
282
282
283
-
Astra generates a list of acceptable classes. Python and Java functions are added a little differently from each other.
283
+
{product} generates a list of acceptable classes. Python and Java functions are added a little differently from each other.
284
284
285
285
Python functions are added by loading a Python file (.py) or a zipped Python file (.zip). When adding Python files, the Class Name is specified as the name of the Python file without the extension plus the class you want to execute.
Copy file name to clipboardExpand all lines: modules/functions/partials/deploy-as.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
Deploy transform functions in the *Functions* tab of the {astra_ui}.
1
+
Deploy transform functions in the *Functions* tab of the {astra-ui}.
2
2
3
-
The process is similar to xref:astra-streaming:developing:astream-functions.adoc[creating a function in the {astra_ui}], but with a few additional steps.
3
+
The process is similar to xref:astra-streaming:developing:astream-functions.adoc[creating a function in the {astra-ui}], but with a few additional steps.
4
4
5
5
. After naming your new function, select the *Use {company} transform function* option.
6
6
. Select a transform function from the list of available functions:
{company} is always experimenting with connectors. Below are the connectors currently in development that have not yet been promoted to official support in *{product}*.
30
30
31
-
To get access to these connectors, contact {support_url}[{company} Support].
31
+
To get access to these connectors, contact {support-url}[{company} Support].
32
32
33
33
=== Sink Connectors (experimental)
34
34
@@ -57,22 +57,32 @@ Assuming you have downloaded client.conf to the {pulsar-short} folder:
57
57
----
58
58
--
59
59
60
-
cURL::
60
+
curl::
61
61
+
62
62
--
63
+
// tag::rest-env-vars[]
64
+
You need a {pulsar-short} token for REST API authentication.
65
+
This is different from your {astra-db} application tokens.
66
+
67
+
. In the {astra-ui-link}, go to *Streaming*, click your tenant's name, and then click the *Settings* tab.
63
68
64
-
You'll need to create an {product} API token to be used with the Rest API. This is different from your Astra tokens.
69
+
. Click *Create Token*.
65
70
66
-
Navigate to the "Settings" area in the {product} UI and choose "Create Token".
71
+
. Copy the token, store it securely, and then click *Close*.
67
72
68
-
Retrieve the web service URL from the "Connect" tab in the {product} UI.
73
+
. Click the *Connect* tab, and then copy the *Web Service URL*.
69
74
75
+
. Create environment variables for your tenant's token and web service URL:
76
+
+
70
77
[source,shell,subs="attributes+"]
71
78
----
72
79
export WEB_SERVICE_URL=<replace-me>
73
80
export ASTRA_STREAMING_TOKEN=<replace-me>
74
81
----
82
+
// end::rest-env-vars[]
75
83
84
+
. Use these values to form curl commands to the REST API:
Copy file name to clipboardExpand all lines: modules/pulsar-io/pages/connectors/sinks/astra-db.adoc
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
-
= {astra_db} ({cass-reg} enhanced)
1
+
= {astra-db} ({cass-reg} enhanced)
2
2
:connectorName: astra-db-sink
3
3
:connectorType: astra-db
4
4
:page-tag: astra-db,cdc,sink-connector
5
5
6
-
{company}{astra_db} Sink Connector is based on the open-source https://docs.datastax.com/en/pulsar-connector/docs/index.html[{cass-reg} sink connector for {pulsar-reg}]. Depending on how you deploy the connector, it can be used to sink topic messages with a table in {astra_db} or a table in a {cass-short} cluster outside of DB.
6
+
{company}{astra-db} Sink Connector is based on the open-source https://docs.datastax.com/en/pulsar-connector/docs/index.html[{cass-reg} sink connector for {pulsar-reg}]. Depending on how you deploy the connector, it can be used to sink topic messages with a table in {astra-db} or a table in a {cass-short} cluster outside of DB.
7
7
8
-
The {product} portal provides simple way to connect this sink and a table in Astra DB with simply a token. Using pulsar-admin or the REST API, you can configure the sink to connect with a {cass-short} connection manually.
8
+
The {product} portal provides simple way to connect this sink and a table in {astra-db} with simply a token. Using pulsar-admin or the REST API, you can configure the sink to connect with a {cass-short} connection manually.
9
9
10
10
This reference assumes you are manually connecting to a {cass-short} table.
These values are provided in the *topic* area in the above cassandra connection parameters.
63
+
These values are provided in the *topic* area in the above {cass-short} connection parameters.
64
64
65
65
Refer to the official documentation for a https://docs.datastax.com/en/pulsar-connector/docs/cfgRefPulsarDseConnection.html[connection properties reference].
0 commit comments