Repo sync for protected branch

data-explorer/docfx.json

@@ -128,8 +128,8 @@
         "sdwheeler",
         "meganbradley"
       ],
-      "author": "shsagir",
-      "ms.author": "shsagir",
+      "author": "spelluru",
+      "ms.author": "spelluru",
       "ms.service": "azure-data-explorer",
       "services": "data-explorer",
       "titleSuffix": "Azure Data Explorer"

data-explorer/includes/iot-hub-get-started-create-device-identity.md

@@ -2,11 +2,11 @@
  title: include file
  description: include file
  services: iot-hub
- author: shsagir
+ author: spelluru
  ms.service: iot-hub
  ms.topic: include
  ms.date: 09/07/2018
- ms.author: shsagir
+ ms.author: spelluru
  ms.custom: include file, devx-track-azurecli
 ---
 

data-explorer/index.yml

@@ -8,8 +8,8 @@ metadata:
   description: Azure Data Explorer is a log analytics cloud platform optimized for ad hoc big data queries.
   ms.service: azure-data-explorer
   ms.topic: landing-page
-  author: shsagir
-  ms.author: shsagir
+  author: spelluru
+  ms.author: spelluru
   ms.date: 01/15/2023
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new

data-explorer/kusto/docfx.json

@@ -118,8 +118,8 @@
         "sdwheeler",
         "meganbradley"
       ],
-      "author": "shsagir",
-      "ms.author": "shsagir",
+      "author": "spelluru",
+      "ms.author": "spelluru",
       "ms.service": "kusto",
       "services": "kusto",
       "titleSuffix": "Kusto"

data-explorer/kusto/index.yml

@@ -8,8 +8,8 @@ metadata:
   description: Kusto Query Language (KQL) is a dynamic and intuitive tool for querying all types of data, designed for easy authoring and clear query comprehension.
   ms.service: kusto
   ms.topic: landing-page
-  author: shsagir
-  ms.author: shsagir
+  author: spelluru
+  ms.author: spelluru
   ms.date: 08/11/2024
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | sample | tutorial | video | whats-new

data-explorer/kusto/management/graph/graph-model-overview.md

@@ -239,7 +239,9 @@ graph("SocialNetwork")
 ```kusto
 // Find people who both work with and are friends with each other
 graph("ProfessionalNetwork") 
-| graph-match (p1:Person)-[:WORKS_WITH]->(p2:Person)-[:FRIENDS_WITH]->(p1)
+| graph-match (p1)-[worksWith]->(p2)-[friendsWith]->(p1)
+    where labels(worksWith) has "WORKS_WITH" and labels(friendsWith) has "FRIENDS_WITH" and
+      labels(p1) has "Person" and labels(p2) has "Person"
     project p1.name, p2.name, p1.department
 ```
 
@@ -248,10 +250,10 @@ graph("ProfessionalNetwork")
 ```kusto
 // Find potential influence paths up to 3 hops away
 graph("InfluenceNetwork") 
-| graph-match (influencer)-[:INFLUENCES*1..3]->(target)
-    where influencer.id == "user123"
-    project influencePath = INFLUENCES, 
-         pathLength = array_length(INFLUENCES), 
+| graph-match (influencer)-[influences*1..3]->(target)
+    where influencer.id == "user123" and all(influences, labels() has "INFLUENCES")
+    project influencePath = influences, 
+         pathLength = array_length(influences), 
          target.name
 ```
 
@@ -300,13 +302,15 @@ Example:
 ```kusto
 // Query the first graph model
 graph("EmployeeNetwork") 
-| graph-match (person:Employee)-[:MANAGES]->(team)
-| project manager=person.name, teamId=team.id
+| graph-match (person)-[manages]->(team)
+    where labels(manages) has "MANAGES" and labels(person) has "Employee"
+    project manager=person.name, teamId=team.id
 // Use these results to query another graph model
 | join (
 	graph("ProjectNetwork")
-	| graph-match (project)-[:ASSIGNED_TO]->(team)
-	| project projectName=project.name, teamId=team.id
+	| graph-match (project)-[assignedTo]->(team)
+        where labels(assignedTo) has "ASSIGNED_TO"
+	    project projectName=project.name, teamId=team.id
 ) on teamId
 ```
 

data-explorer/kusto/management/graph/graph-persistent-overview.md

@@ -94,15 +94,15 @@ Once a graph snapshot is created, it can be queried using the [`graph`](../../qu
 ```kusto
 graph("MyGraphModel")
 | graph-match (n)-[e]->(m)
-| project n, e, m
+    project n, e, m
 ```
 
 To query a specific snapshot, provide the snapshot name:
 
 ```kusto
 graph("MyGraphModel", "MyGraphSnapshot")
 | graph-match (n)-[e]->(m)
-| project n, e, m
+    project n, e, m
 ```
 
 The [`graph-match`](../../query/graph-match-operator.md) operator enables pattern matching and traversal operations, while [`graph-shortest-paths`](../../query/graph-shortest-paths-operator.md) helps find optimal connections between entities. The [`graph-to-table`](../../query/graph-to-table-operator.md) operator converts graph results back to tabular format.

data-explorer/kusto/query/graph-function.md

@@ -63,9 +63,9 @@ The following example uses the named parameter syntax to specify a snapshot:
 
 ```kusto
 graph("SecurityGraph", snapshot="Snapshot_2025_05_01")
-| graph-shortest-paths (start)-[*]->(end)
+| graph-shortest-paths (start)-[e*1..20]->(end)
   where start.name == "Alice" and end.name == "Database"
-  project PathLength = path_length, Path = path_nodes
+  project PathLength = array_length(e), Path = e
 ```
 
 ## Related content

data-explorer/monitor-data-explorer-reference.md

@@ -4,8 +4,8 @@ description: This article contains important reference material you need when yo
 ms.date: 12/09/2024
 ms.custom: horz-monitor
 ms.topic: reference
-author: shsagir
-ms.author: shsagir
+author: spelluru
+ms.author: spelluru
 ms.service: azure-data-explorer
 ---
 

data-explorer/monitor-data-explorer.md

@@ -4,8 +4,8 @@ description: Learn how to monitor Azure Data Explorer using Azure Monitor, inclu
 ms.date: 12/09/2024
 ms.custom: horz-monitor
 ms.topic: conceptual
-author: shsagir
-ms.author: shsagir
+author: spelluru
+ms.author: spelluru
 ms.service: azure-data-explorer
 ---