Skip to content

Commit 8c8e337

Browse files
authored
Merge pull request #174344 from v-albemi/register-scan-cassandra-source
edit pass: register-scan-cassandra-source
2 parents 120d14b + 3b1d916 commit 8c8e337

File tree

1 file changed

+78
-70
lines changed

1 file changed

+78
-70
lines changed
Lines changed: 78 additions & 70 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,20 @@
11
---
2-
title: Register Cassandra as a source and setup scans
3-
description: This article outlines how to register Cassandra server in Azure Purview and set up a scan.
2+
title: Register and scan a Cassandra source
3+
description: This article describes how to register a Cassandra server in Azure Purview and set up a scan to extract metadata.
44
author: chandrakavya
55
ms.author: kchandra
66
ms.service: purview
77
ms.subservice: purview-data-map
88
ms.topic: overview
99
ms.date: 09/27/2021
1010
---
11-
# Register and Scan a Cassandra source (Preview)
11+
# Register and scan a Cassandra source (preview)
1212

13-
This article outlines how to register a Cassandra server in Purview and set up a scan.
13+
This article describes how to register a Cassandra server in Azure Purview and set up a scan.
1414

1515
## Supported capabilities
1616

17-
The Cassandra source supports Full scan to extract metadata from a
18-
Cassandra server and fetches Lineage between data assets.
17+
You can use Purview to do full scans on Cassandra to extract metadata and lineage between data assets.
1918

2019
## Prerequisites
2120

@@ -24,120 +23,129 @@ Cassandra server and fetches Lineage between data assets.
2423
For more information, see 
2524
[Create and configure a self-hosted integration runtime](../data-factory/create-self-hosted-integration-runtime.md).
2625

27-
2. Make sure [JDK 11](https://www.oracle.com/java/technologies/javase-jdk11-downloads.html)
28-
is installed on your virtual machine where self-hosted integration
26+
2. Ensure [JDK 11](https://www.oracle.com/java/technologies/javase-jdk11-downloads.html)
27+
is installed on the virtual machine where the self-hosted integration
2928
runtime is installed.
3029

31-
3. Make sure \"Visual C++ Redistributable 2012 Update 4\" is installed
32-
on the self-hosted integration runtime machine. If you don\'t yet
33-
have it installed, download it from
34-
[here](https://www.microsoft.com/download/details.aspx?id=30679).
30+
3. Ensure Visual C++ Redistributable for Visual Studio 2012 Update 4 is installed
31+
on the self-hosted integration runtime machine. If you don't
32+
have this update installed, [download it](https://www.microsoft.com/download/details.aspx?id=30679).
3533

36-
4. Supported Cassandra server versions are 3.x to 4.x
34+
4. Ensure your Cassandra server is version 3.*x* or 4.*x*.
3735

3836
## Register a Cassandra server
3937

40-
To register a new Cassandra server in your data catalog, do the
41-
following:
38+
To register a new Cassandra server in your data catalog:
4239

43-
1. Navigate to your Purview account.
44-
2. Select **Data Map** on the left navigation.
45-
3. Select **Register.**
46-
4. On Register sources, select **Cassandra** . Select **Continue.**
47-
:::image type="content" source="media/register-scan-cassandra-source/register-sources.png" alt-text="register Cassandra source" border="true":::
40+
1. Go to your Purview account.
41+
2. Select **Data Map** on the left pane.
42+
3. Select **Register**.
43+
4. On the **Register sources** screen, select **Cassandra**, and then select **Continue**:
44+
45+
:::image type="content" source="media/register-scan-cassandra-source/register-sources.png" alt-text="Screenshot that shows the Register sources screen." border="true":::
4846

49-
On the Register sources (Cassandra) screen, do the following:
47+
1. On the **Register sources (Cassandra)** screen:
5048

51-
1. Enter a **Name** that the data source will be listed within the
52-
Catalog.
49+
1. Enter a **Name**. The data source will use this name in the
50+
catalog.
5351

54-
2. Enter the server address where Cassandra server is running in the **Host** field. For example, 20.190.193.10
52+
2. In the **Host** box, enter the server address where the Cassandra server is running. For example, 20.190.193.10.
5553

56-
3. Enter the port used by Cassandra server in the **Port** field.
57-
4. Select a collection or create a new one (Optional)
54+
3. In the **Port** box, enter the port used by the Cassandra server.
55+
4. Select a collection or create a new one (optional).
56+
:::image type="content" source="media/register-scan-cassandra-source/configure-sources.png" alt-text="Screenshot that shows the Register sources (Cassandra) screen." border="true":::
57+
5. Select **Register**.
5858

59-
5. Select **Register**.
60-
:::image type="content" source="media/register-scan-cassandra-source/configure-sources.png" alt-text="configure Cassandra source" border="true":::
6159

62-
## Creating and running a scan
60+
## Create and run a scan
6361

64-
To create and run a new scan, do the following:
62+
To create and run a new scan:
6563

66-
1. In the Management Center, select Integration runtimes. Make sure a
67-
self-hosted integration runtime is set up. If it is not set up, use
68-
the steps mentioned
69-
[here](./manage-integration-runtimes.md)
70-
to setup a self-hosted integration runtime
64+
1. In the Management Center, select **Integration runtimes**. Make sure a
65+
self-hosted integration runtime is set up. If you don't have one set up, complete
66+
[these steps to set up a self-hosted integration runtime](./manage-integration-runtimes.md).
67+
7168

72-
2. Navigate to **Sources**.
69+
2. Go to **Sources**.
7370

74-
3. Select the registered **Cassandra** server.
71+
3. Select the registered Cassandra server.
7572

76-
4. Select **+ New scan**.
73+
4. Select **New scan**.
7774

78-
5. Provide the below details:
75+
5. Provide the following details.
7976

80-
a. **Name**: The name of the scan
77+
a. **Name**: Specify a name for the scan.
8178

8279
b. **Connect via integration runtime**: Select the configured
83-
self-hosted integration runtime
80+
self-hosted integration runtime.
8481

85-
c. **Credential**: While configuring Cassandra credential, make sure
82+
c. **Credential**: When you configure the Cassandra credentials, be sure
8683
to:
8784

88-
- Select **Basic Authentication** as the Authentication method
89-
- Provide the username on who's behalf the connection is being made in the User name field.
90-
- Save Cassandra user's password on whose behalf the connection is being made in the key vault's secret
85+
- Select **Basic Authentication** as the authentication method.
86+
- In the **User name** box, provide the name of the user you're making the connection for.
87+
- In the key vault's secret, save the password of the Cassandra user you're making the connection for.
88+
89+
For more information, see [Credentials for source authentication in Purview](manage-credentials.md).
90+
91+
d. **Keyspaces**: Specify a list of Cassandra keyspaces to import. Multiple keyspaces must be separated with semicolons. For example, keyspace1; keyspace2. When the list is empty, all available keyspaces are imported.
92+
93+
You can use keyspace name patterns that use SQL LIKE expression syntax, including %.
9194

92-
To understand more on credentials, refer to the link [here](manage-credentials.md).
95+
For example: A%; %B; %C%; D
9396

94-
d. **Keyspaces**: Specify a list of Cassandra keyspaces to be imported. Multiple keypsaces must be semicolon separated. For example, keyspace1; keyspace2. When the list is empty, all available keyspaces are imported.
95-
Acceptable keyspace name patterns using SQL LIKE expressions syntax include using %,
97+
This expression means:
98+
- Starts with A or
99+
- Ends with B or
100+
- Contains C or
101+
- Equals D
96102

97-
e.g. A%; %B; %C%; D
98-
- start with A or
99-
- end with B or
100-
- contain C or
101-
- equal D
102-
Usage of NOT and special characters are not acceptable.
103+
You can't use NOT or special characters.
103104

104-
f. **Use Secure Sockets Layer(SSL)** : Select True or False to Notify
105-
if Secure Sockets Layer (SSL) must be used when connecting to the
106-
Cassandra server. By default, this value is set to False.
105+
e. **Use Secure Sockets Layer(SSL)**: Select **True** or **False** to specify whether
106+
to use Secure Sockets Layer (SSL) when connecting to the
107+
Cassandra server. By default, this option is set to **False**.
107108

108-
g. **Maximum memory available**: Maximum memory (in GB) available on customer's VM to be used by scanning processes. This is dependent on the size of Cassandra server to be scanned.
109+
f. **Maximum memory available**: Specify the maximum memory (in GB) available on your VM to be used for scanning processes. This value depends on the size of Cassandra server to be scanned.
109110
:::image type="content" source="media/register-scan-cassandra-source/scan.png" alt-text="scan Cassandra source" border="true":::
110111

111112
6. Select **Test connection.**
112113

113114
7. Select **Continue**.
114115

115-
8. Choose your **scan trigger**. You can set up a schedule or ran the
116+
8. Select a **scan trigger**. You can set up a schedule or run the
116117
scan once.
117118

118-
9. Review your scan and select **Save and Run**.
119+
9. Review your scan, and then select **Save and Run**.
119120

120-
## Viewing your scans and scan runs
121+
## View your scans and scan runs
121122

122-
1. Navigate to the management center. Select **Data sources** under the **Sources and scanning** section.
123+
1. Go to the Management Center. Select **Data sources** in the **Sources and scanning** section.
123124

124-
2. Select the desired data source. You will see a list of existing scans on that data source.
125+
2. Select the data source whose scans you want to view. You'll see a list of existing scans on that data source.
125126

126-
3. Select the scan whose results you are interested to view.
127+
3. Select the scan whose results you want to view.
127128

128-
4. This page will show you all of the previous scan runs along with metrics and status for each scan run. It will also display whether your scan was scheduled or manual, how many assets had classifications applied, how many total assets were discovered, the start and end time of the scan, and the total scan duration.
129+
The resulting page will show all previous scan runs together with metrics and status for each one.
130+
It will also indicate:
131+
- Whether your scan was scheduled or manual.
132+
- How many assets had classifications applied.
133+
- How many total assets were discovered.
134+
- The start and end time of the scan.
135+
- The duration of the scan.
129136

130137
## Manage your scans
131138

132-
To manage or delete a scan, do the following:
139+
To manage or delete a scan:
133140

134-
1. Navigate to the management center. Select **Data sources** under the **Sources and scanning** section then select on the desired data source.
141+
1. Go to the Management Center. Select **Data sources** in the **Sources and scanning** section. Then select the data source whose scan you want to manage.
135142

136-
2. Select the scan you would like to manage. You can edit the scan by selecting **Edit**.
143+
2. Select the scan you want to manage.
144+
- You can edit the scan by selecting **Edit**.
137145

138-
3. You can delete your scan by selecting **Delete**.
146+
- You can delete the scan by selecting **Delete**.
139147

140148
## Next steps
141149

142150
- [Browse the Azure Purview Data catalog](how-to-browse-catalog.md)
143-
- [Search the Azure Purview Data Catalog](how-to-search-catalog.md)
151+
- [Search the Azure Purview Data Catalog](how-to-search-catalog.md)

0 commit comments

Comments
 (0)