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: articles/cosmos-db/graph-introduction.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,7 +50,7 @@ The following are the differentiated features that Azure Cosmos DB Gremlin API o
50
50
51
51
***Compatibility with Apache TinkerPop**
52
52
53
-
Azure Cosmos DB supports the [open-source Apache TinkerPop standard](http://tinkerpop.apache.org/). The Tinkerpop standard has an ample ecosystem of applications and libraries that can be easily integrated with Azure Cosmos DB's Gremlin API.
53
+
Azure Cosmos DB supports the [open-source Apache TinkerPop standard](https://tinkerpop.apache.org/). The Tinkerpop standard has an ample ecosystem of applications and libraries that can be easily integrated with Azure Cosmos DB's Gremlin API.
Copy file name to clipboardExpand all lines: articles/cosmos-db/graph-modeling.md
+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
@@ -18,7 +18,7 @@ The following document is designed to provide graph data modeling recommendation
18
18
The process outlined in this guide is based on the following assumptions:
19
19
* The **entities** in the problem-space are identified. These entities are meant to be consumed _atomically_ for each request. In other words, the database system isn't designed to retrieve a single entity's data in multiple query requests.
20
20
* There is an understanding of **read and write requirements** for the database system. These requirements will guide the optimizations needed for the graph data model.
21
-
* The principles of the [Apache Tinkerpop property graph standard](http://tinkerpop.apache.org/docs/current/reference/#graph-computing) are well understood.
21
+
* The principles of the [Apache Tinkerpop property graph standard](https://tinkerpop.apache.org/docs/current/reference/#graph-computing) are well understood.
22
22
23
23
## When do I need a graph database?
24
24
@@ -36,7 +36,7 @@ The next step is to determine if the graph is going to be used for analytic or t
36
36
37
37
## How to use graph objects
38
38
39
-
The [Apache Tinkerpop property graph standard](http://tinkerpop.apache.org/docs/current/reference/#graph-computing) defines two types of objects **Vertices** and **Edges**.
39
+
The [Apache Tinkerpop property graph standard](https://tinkerpop.apache.org/docs/current/reference/#graph-computing) defines two types of objects **Vertices** and **Edges**.
40
40
41
41
The following are the best practices for the properties in the graph objects:
Copy file name to clipboardExpand all lines: articles/cosmos-db/graph-visualization.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ ms.date: 07/02/2019
11
11
12
12
# Visualize graph data stored in Azure Cosmos DB Gremlin API with data visualization solutions
13
13
14
-
You can visualize data stored in Azure Cosmos DB Gremlin API by using various data visualization solutions. The following solutions are recommended by the [Apache Tinkerpop community](http://tinkerpop.apache.org/#poweredby) for graph data visualization.
14
+
You can visualize data stored in Azure Cosmos DB Gremlin API by using various data visualization solutions. The following solutions are recommended by the [Apache Tinkerpop community](https://tinkerpop.apache.org/#poweredby) for graph data visualization.
****[Gremlin Bytecode](http://tinkerpop.apache.org/docs/current/tutorials/gremlin-language-variants/)*** is a programming language agnostic specification for graph traversals. Cosmos DB Graph doesn't support it yet. Use ```GremlinClient.SubmitAsync()``` and pass traversal as a text string.
21
+
****[Gremlin Bytecode](https://tinkerpop.apache.org/docs/current/tutorials/gremlin-language-variants/)*** is a programming language agnostic specification for graph traversals. Cosmos DB Graph doesn't support it yet. Use ```GremlinClient.SubmitAsync()``` and pass traversal as a text string.
22
22
23
23
****```property(set, 'xyz', 1)```*** set cardinality isn't supported today. Use ```property(list, 'xyz', 1)``` instead.
Copy file name to clipboardExpand all lines: articles/cosmos-db/gremlin-support.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ The following table lists the TinkerPop features that are implemented by Azure C
43
43
44
44
## Gremlin wire format: GraphSON
45
45
46
-
Azure Cosmos DB uses the [GraphSON format](http://tinkerpop.apache.org/docs/current/reference/#graphson) when returning results from Gremlin operations. Azure Cosmos DB currently supports "GraphSONv2" version. GraphSON is the Gremlin standard format for representing vertices, edges, and properties (single and multi-valued properties) using JSON.
46
+
Azure Cosmos DB uses the [GraphSON format](https://tinkerpop.apache.org/docs/current/reference/#graphson) when returning results from Gremlin operations. Azure Cosmos DB currently supports "GraphSONv2" version. GraphSON is the Gremlin standard format for representing vertices, edges, and properties (single and multi-valued properties) using JSON.
47
47
48
48
For example, the following snippet shows a GraphSON representation of a vertex *returned to the client* from Azure Cosmos DB.
|![ImanisData][1]|[Data migration](https://www.imanisdata.com/wp-content/uploads/2018/02/Imanis_DS_MongoDB_Azure_FINAL.pdf) from MongoDB to Azure Cosmos DB. <br/> Imanis Data enables global enterprises to quickly and easily migrate their on-premises or cloud MongoDB databases to Azure Cosmos DB. Imanis Data provides an agentless, incremental-forever cloud migration approach for MongoDB data stores that simplifies migration and significantly reduces downtime.| USA |[Website](http://www.imanisdata.com/)|
19
+
|![ImanisData][1]|[Data migration](https://www.imanisdata.com/wp-content/uploads/2018/02/Imanis_DS_MongoDB_Azure_FINAL.pdf) from MongoDB to Azure Cosmos DB. <br/> Imanis Data enables global enterprises to quickly and easily migrate their on-premises or cloud MongoDB databases to Azure Cosmos DB. Imanis Data provides an agentless, incremental-forever cloud migration approach for MongoDB data stores that simplifies migration and significantly reduces downtime.| USA |[Website](https://www.imanisdata.com/)|
20
20
|![Striim][2]|[Move real-time data to Azure Cosmos DB](https://www.striim.com/striim-for-azure-cosmos-db/) from a wide variety of data sources. <br/> Striim simplifies the real-time collection and movement of data from a wide variety of on-premises sources, including enterprise document and relational databases, sensors, and log files into Azure Cosmos DB. | USA |[Website](https://www.striim.com/)|
description: Learn how to create non-interactive authentication Microsoft .NET applications in Azure HDInsight.
4
-
ms.reviewer: jasonh
5
4
author: hrasheed-msft
6
-
5
+
ms.author: hrasheed
6
+
ms.reviewer: jasonh
7
7
ms.service: hdinsight
8
-
ms.custom: hdinsightactive
9
8
ms.topic: conceptual
10
-
ms.date: 05/14/2018
11
-
ms.author: hrasheed
12
-
9
+
ms.custom: hdinsightactive
10
+
ms.date: 12/23/2019
13
11
---
12
+
14
13
# Create a non-interactive authentication .NET HDInsight application
15
-
You can run your Microsoft .NET Azure HDInsight application either under the application's own identity (non-interactive) or under the identity of the signed-in user of the application (interactive). This article shows you how to create a non-interactive authentication .NET application to connect to Azure and manage HDInsight. For a sample of an interactive application, see [Connect to Azure HDInsight](hdinsight-administer-use-dotnet-sdk.md#connect-to-azure-hdinsight).
14
+
15
+
Run your Microsoft .NET Azure HDInsight application either under the application's own identity (non-interactive) or under the identity of the signed-in user of the application (interactive). This article shows you how to create a non-interactive authentication .NET application to connect to Azure and manage HDInsight. For a sample of an interactive application, see [Connect to Azure HDInsight](hdinsight-administer-use-dotnet-sdk.md#connect-to-azure-hdinsight).
16
16
17
17
From your non-interactive .NET application, you need:
18
18
@@ -21,20 +21,21 @@ From your non-interactive .NET application, you need:
21
21
* The Azure AD application secret key. See [Get application authentication key](../active-directory/develop/howto-create-service-principal-portal.md#get-values-for-signing-in).
22
22
23
23
## Prerequisites
24
-
* An HDInsight cluster. See the [getting started tutorial](hadoop/apache-hadoop-linux-tutorial-get-started.md#create-cluster).
24
+
25
+
An HDInsight cluster. See the [getting started tutorial](hadoop/apache-hadoop-linux-tutorial-get-started.md#create-cluster).
25
26
26
27
## Assign a role to the Azure AD application
27
-
Assign your Azure AD application a [role](../role-based-access-control/built-in-roles.md), to grant it permissions to perform actions. You can set the scope at the level of the subscription, resource group, or resource. The permissions are inherited to lower levels of scope. (For example, adding an application to the Reader role for a resource group means that the application can read the resource group and any resources in it.) In this article, you set the scope at the resource group level. For more information, see [Use role assignments to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.md).
28
+
29
+
Assign your Azure AD application a [role](../role-based-access-control/built-in-roles.md), to grant it permissions to perform actions. You can set the scope at the level of the subscription, resource group, or resource. The permissions are inherited to lower levels of scope. For example, adding an application to the Reader role for a resource group means that the application can read the resource group and any resources in it. In this article, you set the scope at the resource group level. For more information, see [Use role assignments to manage access to your Azure subscription resources](../role-based-access-control/role-assignments-portal.md).
28
30
29
31
**To add the Owner role to the Azure AD application**
30
32
31
33
1. Sign in to the [Azure portal](https://portal.azure.com).
32
-
2. In the left menu, select **Resource groups**.
33
-
3. Select the resource group that has the HDInsight cluster on which you will run your Hive query later in this article. If you have a large number of resource groups, you can use the filter to find the one you want.
34
-
4. On the resource group menu, select **Access control (IAM)**.
35
-
5. Select the **Role assignments** tab to see the current role assignments.
36
-
6. At the top of the page, select **Add role assignment**.
37
-
7. Follow the instructions to add the Owner role to your Azure AD application. After you successfully add the role, the application is listed under the Owner role.
34
+
1. Navigate to the resource group that has the HDInsight cluster on which you'll run your Hive query later in this article. If you have a large number of resource groups, you can use the filter to find the one you want.
35
+
1. On the resource group menu, select **Access control (IAM)**.
36
+
1. Select the **Role assignments** tab to see the current role assignments.
37
+
1. At the top of the page, select **+ Add**.
38
+
1. Follow the instructions to add the Owner role to your Azure AD application. After you successfully add the role, the application is listed under the Owner role.
38
39
39
40
## Develop an HDInsight client application
40
41
@@ -113,8 +114,8 @@ Assign your Azure AD application a [role](../role-based-access-control/built-in-
0 commit comments