Skip to content

Commit fa2e31c

Browse files
authored
Merge pull request #224740 from whhender/more-30-adla-review
More 30 adla review
2 parents 9d5695c + 62b61e3 commit fa2e31c

File tree

29 files changed

+235
-232
lines changed

29 files changed

+235
-232
lines changed

articles/data-lake-analytics/data-lake-analytics-add-users.md

Lines changed: 18 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -2,48 +2,48 @@
22
title: Add users to an Azure Data Lake Analytics account
33
description: Learn how to correctly add users to your Data Lake Analytics account using the Add User Wizard and Azure PowerShell.
44
ms.service: data-lake-analytics
5-
ms.reviewer: jasonh
5+
ms.reviewer: whhender
66
ms.topic: how-to
7-
ms.date: 05/24/2018
7+
ms.date: 01/20/2023
88
---
99

1010
# Adding a user in the Azure portal
1111

1212
[!INCLUDE [retirement-flag](includes/retirement-flag.md)]
1313

1414
## Start the Add User Wizard
15-
1. Open your Azure Data Lake Analytics via https://portal.azure.com.
16-
2. Click **Add User Wizard**.
17-
3. In the **Select user** step, find the user you want to add. Click **Select**.
18-
4. the **Select role** step, pick **Data Lake Analytics Developer**. This role has the minimum set of permissions required to submit/monitor/manage U-SQL jobs. Assign to this role if the group is not intended for managing Azure services.
19-
5. In the **Select catalog permissions** step, select any additional databases that user will need access to. Read and Write Access to the default static database called "master" is required to submit jobs. When you are done, click **OK**.
20-
6. In the final step called **Assign selected permissions** review the changes the wizard will make. Click **OK**.
2115

16+
1. Open your Azure Data Lake Analytics via https://portal.azure.com.
17+
2. Select **Add User Wizard**.
18+
3. In the **Select user** step, find the user you want to add. Select **Select**.
19+
4. the **Select role** step, pick **Data Lake Analytics Developer**. This role has the minimum set of permissions required to submit/monitor/manage U-SQL jobs. Assign to this role if the group isn't intended for managing Azure services.
20+
5. In the **Select catalog permissions** step, select any other databases that user will need access to. Read and Write Access to the default static database called "master" is required to submit jobs. When you're done, select **OK**.
21+
6. In the final step called **Assign selected permissions** review the changes the wizard will make. Select **OK**.
2222

2323
## Configure ACLs for data folders
24+
2425
Grant "R-X" or "RWX", as needed, on folders containing input data and output data.
2526

27+
## Optionally, add the user to the Azure Data Lake Storage Gen1 role **Reader** role
2628

27-
## Optionally, add the user to the Azure Data Lake Storage Gen1 role **Reader** role.
28-
1. Find your Azure Data Lake Storage Gen1 account.
29-
2. Click on **Users**.
30-
3. Click **Add**.
31-
4. Select an Azure role to assign this group.
32-
5. Assign to Reader role. This role has the minimum set of permissions required to browse/manage data stored in ADLSGen1. Assign to this role if the Group is not intended for managing Azure services.
33-
6. Type in the name of the Group.
34-
7. Click **OK**.
29+
1. Find your Azure Data Lake Storage Gen1 account.
30+
2. Select **Users**.
31+
3. Select **Add**.
32+
4. Select an Azure role to assign this group.
33+
5. Assign to Reader role. This role has the minimum set of permissions required to browse/manage data stored in ADLSGen1. Assign to this role if the Group isn't intended for managing Azure services.
34+
6. Type in the name of the Group.
35+
7. Select **OK**.
3536

3637
## Adding a user using PowerShell
3738

3839
1. Follow the instructions in this guide: [How to install and configure Azure PowerShell](/powershell/azure/).
3940
2. Download the [Add-AdlaJobUser.ps1](https://github.com/Azure/AzureDataLake/blob/master/Samples/PowerShell/ADLAUsers/Add-AdlaJobUser.ps1) PowerShell script.
40-
3. Run the PowerShell script.
41+
3. Run the PowerShell script.
4142

4243
The sample command to give user access to submit jobs, view new job metadata, and view old metadata is:
4344

4445
`Add-AdlaJobUser.ps1 -Account myadlsaccount -EntityToAdd 546e153e-0ecf-417b-ab7f-aa01ce4a7bff -EntityType User -FullReplication`
4546

46-
4747
## Next steps
4848

4949
* [Overview of Azure Data Lake Analytics](data-lake-analytics-overview.md)

articles/data-lake-analytics/data-lake-analytics-analyze-weblogs.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Analyze Website logs using Azure Data Lake Analytics
33
description: Learn how to analyze website logs using Azure Data Lake Analytics to run U-SQL functions and queries.
4-
ms.reviewer: jasonh
4+
ms.reviewer: whhender
55
ms.service: data-lake-analytics
66
ms.topic: how-to
7-
ms.date: 12/05/2016
7+
ms.date: 01/20/2023
88
---
99
# Analyze Website logs using Azure Data Lake Analytics
1010
Learn how to analyze website logs using Data Lake Analytics, especially on finding out which referrers ran into errors when they tried to visit the website.
@@ -15,29 +15,29 @@ Learn how to analyze website logs using Data Lake Analytics, especially on findi
1515
* **Visual Studio 2015 or Visual Studio 2013**.
1616
* **[Data Lake Tools for Visual Studio](https://aka.ms/adltoolsvs)**.
1717

18-
Once Data Lake Tools for Visual Studio is installed, you will see a **Data Lake** item in the **Tools** menu in Visual Studio:
18+
Once Data Lake Tools for Visual Studio is installed, you'll see a **Data Lake** item in the **Tools** menu in Visual Studio:
1919

2020
![U-SQL Visual Studio menu](./media/data-lake-analytics-data-lake-tools-get-started/data-lake-analytics-data-lake-tools-menu.png)
2121
* **Basic knowledge of Data Lake Analytics and the Data Lake Tools for Visual Studio**. To get started, see:
2222

2323
* [Develop U-SQL script using Data Lake tools for Visual Studio](data-lake-analytics-data-lake-tools-get-started.md).
2424
* **A Data Lake Analytics account.** See [Create an Azure Data Lake Analytics account](data-lake-analytics-get-started-portal.md).
25-
* **Install the sample data.** In the Azure Portal, open you Data Lake Analytics account and click **Sample Scripts** on the left menu, then click **Copy Sample Data**.
25+
* **Install the sample data.** In the Azure portal, open your Data Lake Analytics account and select **Sample Scripts** on the left menu, then select **Copy Sample Data**.
2626

2727
## Connect to Azure
2828
Before you can build and test any U-SQL scripts, you must first connect to Azure.
2929

3030
### To connect to Data Lake Analytics
3131

3232
1. Open Visual Studio.
33-
2. Click **Data Lake > Options and Settings**.
34-
3. Click **Sign In**, or **Change User** if someone has signed in, and follow the instructions.
35-
4. Click **OK** to close the Options and Settings dialog.
33+
2. Select **Data Lake > Options and Settings**.
34+
3. Select **Sign In**, or **Change User** if someone has signed in, and follow the instructions.
35+
4. Select **OK** to close the Options and Settings dialog.
3636

3737
### To browse your Data Lake Analytics accounts
3838

3939
1. From Visual Studio, open **Server Explorer** by press **CTRL+ALT+S**.
40-
2. From **Server Explorer**, expand **Azure**, and then expand **Data Lake Analytics**. You shall see a list of your Data Lake Analytics accounts if there are any. You cannot create Data Lake Analytics accounts from the studio. To create an account, see [Get Started with Azure Data Lake Analytics using Azure Portal](data-lake-analytics-get-started-portal.md) or [Get Started with Azure Data Lake Analytics using Azure PowerShell](data-lake-analytics-get-started-powershell.md).
40+
2. From **Server Explorer**, expand **Azure**, and then expand **Data Lake Analytics**. You shall see a list of your Data Lake Analytics accounts if there are any. You can't create Data Lake Analytics accounts from the studio. To create an account, see [Get Started with Azure Data Lake Analytics using Azure portal](data-lake-analytics-get-started-portal.md) or [Get Started with Azure Data Lake Analytics using Azure PowerShell](data-lake-analytics-get-started-powershell.md).
4141

4242
## Develop U-SQL application
4343
A U-SQL application is mostly a U-SQL script. To learn more about U-SQL, see [Get started with U-SQL](data-lake-analytics-u-sql-get-started.md).
@@ -46,13 +46,13 @@ You can add addition user-defined operators to the application. For more inform
4646

4747
### To create and submit a Data Lake Analytics job
4848

49-
1. Click the **File > New > Project**.
49+
1. Select the **File > New > Project**.
5050

5151
2. Select the U-SQL Project type.
5252

5353
![new U-SQL Visual Studio project](./media/data-lake-analytics-data-lake-tools-get-started/data-lake-analytics-data-lake-tools-new-project.png)
5454

55-
3. Click **OK**. Visual studio creates a solution with a Script.usql file.
55+
3. Select **OK**. Visual studio creates a solution with a Script.usql file.
5656

5757
4. Enter the following script into the Script.usql file:
5858

@@ -153,13 +153,13 @@ You can add addition user-defined operators to the application. For more inform
153153

154154
6. Switch back to the first U-SQL script and next to the **Submit** button, specify your Analytics account.
155155

156-
7. From **Solution Explorer**, right click **Script.usql**, and then click **Build Script**. Verify the results in the Output pane.
156+
7. From **Solution Explorer**, right select **Script.usql**, and then select **Build Script**. Verify the results in the Output pane.
157157

158-
8. From **Solution Explorer**, right click **Script.usql**, and then click **Submit Script**.
158+
8. From **Solution Explorer**, right select **Script.usql**, and then select **Submit Script**.
159159

160-
9. Verify the **Analytics Account** is the one where you want to run the job, and then click **Submit**. Submission results and job link are available in the Data Lake Tools for Visual Studio Results window when the submission is completed.
160+
9. Verify the **Analytics Account** is the one where you want to run the job, and then select **Submit**. Submission results and job link are available in the Data Lake Tools for Visual Studio Results window when the submission is completed.
161161

162-
10. Wait until the job is completed successfully. If the job failed, it is most likely missing the source file. Please see the Prerequisite section of this tutorial. For additional troubleshooting information, see [Monitor and troubleshoot Azure Data Lake Analytics jobs](data-lake-analytics-monitor-and-troubleshoot-jobs-tutorial.md).
162+
10. Wait until the job is completed successfully. If the job failed, it's most likely missing the source file. See the Prerequisite section of this tutorial. For more troubleshooting information, see [Monitor and troubleshoot Azure Data Lake Analytics jobs](data-lake-analytics-monitor-and-troubleshoot-jobs-tutorial.md).
163163

164164
When the job is completed, you shall see the following screen:
165165

@@ -169,14 +169,14 @@ You can add addition user-defined operators to the application. For more inform
169169

170170
### To see the job output
171171

172-
1. From **Server Explorer**, expand **Azure**, expand **Data Lake Analytics**, expand your Data Lake Analytics account, expand **Storage Accounts**, right-click the default Data Lake Storage account, and then click **Explorer**.
172+
1. From **Server Explorer**, expand **Azure**, expand **Data Lake Analytics**, expand your Data Lake Analytics account, expand **Storage Accounts**, right-click the default Data Lake Storage account, and then select **Explorer**.
173173
2. Double-click **Samples** to open the folder, and then double-click **Outputs**.
174174
3. Double-click **UnsuccessfulResponses.log**.
175175
4. You can also double-click the output file inside the graph view of the job in order to navigate directly to the output.
176176

177177
## Next steps
178178
To get started with Data Lake Analytics using different tools, see:
179179

180-
* [Get started with Data Lake Analytics using Azure Portal](data-lake-analytics-get-started-portal.md)
180+
* [Get started with Data Lake Analytics using Azure portal](data-lake-analytics-get-started-portal.md)
181181
* [Get started with Data Lake Analytics using Azure PowerShell](data-lake-analytics-get-started-powershell.md)
182182
* [Get started with Data Lake Analytics using .NET SDK](./data-lake-analytics-get-started-cli.md)

articles/data-lake-analytics/data-lake-analytics-cicd-overview.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: How to set up a CI/CD pipeline for Azure Data Lake Analytics
33
description: Learn how to set up continuous integration and continuous deployment for Azure Data Lake Analytics.
44
ms.service: data-lake-analytics
55
ms.topic: how-to
6-
ms.date: 09/14/2018
6+
ms.date: 01/20/2023
77
ms.custom: devx-track-azurepowershell
88
---
99
# How to set up a CI/CD pipeline for Azure Data Lake Analytics
@@ -62,7 +62,7 @@ Learn more about [U-SQL database project](data-lake-analytics-data-lake-tools-de
6262
6363
### Build a U-SQL project with the MSBuild command line
6464

65-
First migrate the project and get the NuGet package. Then call the standard MSBuild command line with the following additional arguments to build your U-SQL project:
65+
First migrate the project and get the NuGet package. Then call the standard MSBuild command line with the following arguments to build your U-SQL project:
6666

6767
```console
6868
msbuild USQLBuild.usqlproj /p:USQLSDKPath=packages\Microsoft.Azure.DataLake.USQL.SDK.1.3.180615\build\runtime;USQLTargetType=SyntaxCheck;DataRoot=datarootfolder;/p:EnableDeployment=true
@@ -312,7 +312,7 @@ To add the NuGet package reference, right-click the solution in Visual Studio So
312312

313313
### Build U-SQL a database project with the MSBuild command line
314314

315-
To build your U-SQL database project, call the standard MSBuild command line and pass the U-SQL SDK NuGet package reference as an additional argument. See the following example:
315+
To build your U-SQL database project, call the standard MSBuild command line and pass the U-SQL SDK NuGet package reference as another argument. See the following example:
316316

317317
```console
318318
msbuild DatabaseProject.usqldbproj /p:USQLSDKPath=packages\Microsoft.Azure.DataLake.USQL.SDK.1.3.180615\build\runtime
@@ -340,7 +340,7 @@ In addition to the command line, you can use Visual Studio Build or an MSBuild t
340340

341341
### U-SQL database project build output
342342

343-
The build output for a U-SQL database project is a U-SQL database deployment package, named with the suffix `.usqldbpack`. The `.usqldbpack` package is a zip file that includes all DDL statements in a single U-SQL script in a DDL folder. It includes all **.dlls** and additional files for assembly in a temp folder.
343+
The build output for a U-SQL database project is a U-SQL database deployment package, named with the suffix `.usqldbpack`. The `.usqldbpack` package is a zip file that includes all DDL statements in a single U-SQL script in a DDL folder. It includes all **.dlls** and other files for assembly in a temp folder.
344344

345345
## Test table-valued functions and stored procedures
346346

@@ -478,9 +478,9 @@ Take the following steps to set up a database deployment task in Azure Pipelines
478478
|AzureSDKPath|The path to search dependent assemblies in the Azure SDK.|null|true|
479479
|Interactive|Whether or not to use interactive mode for authentication.|false|false|
480480
|ClientId|The Azure AD application ID required for non-interactive authentication.|null|Required for non-interactive authentication.|
481-
|Secrete|The secrete or password for non-interactive authentication. It should be used only in a trusted and secure environment.|null|Required for non-interactive authentication, or else use SecreteFile.|
482-
|SecreteFile|The file saves the secrete or password for non-interactive authentication. Make sure to keep it readable only by the current user.|null|Required for non-interactive authentication, or else use Secrete.|
483-
|CertFile|The file saves X.509 certification for non-interactive authentication. The default is to use client secrete authentication.|null|false|
481+
|Secret|The secret or password for non-interactive authentication. It should be used only in a trusted and secure environment.|null|Required for non-interactive authentication, or else use SecreteFile.|
482+
|SecretFile|The file saves the secret or password for non-interactive authentication. Make sure to keep it readable only by the current user.|null|Required for non-interactive authentication, or else use Secret.|
483+
|CertFile|The file saves X.509 certification for non-interactive authentication. The default is to use client secret authentication.|null|false|
484484
| JobPrefix | The prefix for database deployment of a U-SQL DDL job. | Deploy_ + DateTime.Now | false |
485485
486486
## Next steps

articles/data-lake-analytics/data-lake-analytics-cicd-test.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: How to test your Azure Data Lake Analytics code
33
description: 'Learn how to add test cases for U-SQL and extended C# code for Azure Data Lake Analytics.'
44
ms.service: data-lake-analytics
55
ms.topic: how-to
6-
ms.date: 08/30/2019
6+
ms.date: 01/20/2023
77
---
88
# Test your Azure Data Lake Analytics code
99

@@ -136,7 +136,7 @@ For a C# UDO test, make sure to reference the following assemblies, which are ne
136136
- Microsoft.Analytics.Types
137137
- Microsoft.Analytics.UnitTest
138138

139-
If you reference them through [the Nuget package Microsoft.Azure.DataLake.USQL.Interfaces](https://www.nuget.org/packages/Microsoft.Azure.DataLake.USQL.Interfaces/), make sure you add a NuGet Restore task in your build pipeline.
139+
If you reference them through [the NuGet package Microsoft.Azure.DataLake.USQL.Interfaces](https://www.nuget.org/packages/Microsoft.Azure.DataLake.USQL.Interfaces/), make sure you add a NuGet Restore task in your build pipeline.
140140
141141
## Next steps
142142

0 commit comments

Comments
 (0)