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 modules/ROOT/pages/connect-clients-to-proxy.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ If there is no CQL version that is compatible with both clusters, `cqlsh` won't

To connect `cqlsh` to a {product-proxy} instance, do the following:

. On a machine that can connect to your {product-proxy} instance, xref:cql:connect:start-cqlsh-linux-mac.adoc[download and install the {cql-shell}].
. On a machine that can connect to your {product-proxy} instance, xref:cql:cqlsh:use-cql-shell.adoc[download and install the {cql-shell}].
+
Any version of `cqlsh` can connect to {product-proxy}, but some clusters require a specific `cqlsh` version.

Expand Down
2 changes: 1 addition & 1 deletion modules/sideloader/pages/migrate-sideloader.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -205,7 +205,7 @@ During the migration, {sstable-sideloader} automatically populates any SAI defin
* Exact primary key definition as defined in your origin cluster, including the partition key, clustering columns, and ascending/descending ordering clauses.
You must define partition key columns and clustering columns in the exact order that they are defined on your origin cluster.
+
To retrieve schema properties, you can run the `xref:astra@cql:reference:cqlsh-commands/describe-keyspace.adoc[DESCRIBE KEYSPACE]` command on your origin cluster:
To retrieve schema properties, you can run the `xref:astra@cql:cqlsh:cqlsh-commands/describe-keyspace.adoc[DESCRIBE KEYSPACE]` command on your origin cluster:
+
[source,cql,subs="+quotes"]
----
Expand Down