Skip to content

Commit d6d760b

Browse files
committed
done with docs
1 parent f4abd1f commit d6d760b

10 files changed

+85
-72
lines changed

docs/en-US/Connect-Kusto.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -84,7 +84,9 @@ Connect-Kusto
8484

8585
## DESCRIPTION
8686

87-
The `Connect-Kusto` cmdlet is the main entry point for the cmdlets in this module and it's used to establish a connection with your Azure Data Explorer. The authentication methods offered by this cmdlet are:
87+
The `Connect-Kusto` cmdlet is the main entry point for the cmdlets in this module and it's used to establish a connection with your Azure Data Explorer Cluster.
88+
89+
The available authentication methods are:
8890

8991
- User prompt
9092
- System or User Managed Identity

docs/en-US/Invoke-KustoControlCommand.md

Lines changed: 22 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,7 @@ The `Invoke-KustoControlCommand` cmdlet allows you to invoke management commands
3131
### Example 1: Invoke a control command
3232

3333
```powershell
34-
Invoke-KustoControlCommand '
35-
.create table MyLogs(
34+
Invoke-KustoControlCommand '.create table MyLogs(
3635
Level:string,
3736
Timestamp:datetime,
3837
UserId:string,
@@ -41,30 +40,29 @@ Invoke-KustoControlCommand '
4140
ProcessId:int32)'
4241
```
4342

44-
This example shows how to create a new Table on a database specified by [`Connect-Kusto`](Connect-Kusto.md).
43+
This example shows how to create a new Table on a database specified by [`Connect-Kusto`](Connect-Kusto.md#-database).
4544

4645
### Example 2: Invoke a control command over a specified Database
4746

4847
```powershell
49-
Invoke-KustoControlCommand -Database myDb '
50-
.show tables details
51-
| where TotalRowCount > 0
52-
| extend TotalExtentSize = format_bytes(TotalExtentSize)
53-
| extend TotalOriginalSize = format_bytes(TotalOriginalSize)
54-
| extend HotExtentSize = format_bytes(HotExtentSize)
55-
| extend HotOriginalSize = format_bytes(HotOriginalSize)
56-
| project-away
57-
Folder,
58-
DocString,
59-
AuthorizedPrincipals,
60-
RetentionPolicy,
61-
CachingPolicy,
62-
ShardingPolicy,
63-
MergePolicy,
64-
StreamingIngestionPolicy,
65-
IngestionBatchingPolicy,
66-
RowOrderPolicy,
67-
TableId'
48+
Invoke-KustoControlCommand -Database myDb '.show tables details
49+
| where TotalRowCount > 0
50+
| extend TotalExtentSize = format_bytes(TotalExtentSize)
51+
| extend TotalOriginalSize = format_bytes(TotalOriginalSize)
52+
| extend HotExtentSize = format_bytes(HotExtentSize)
53+
| extend HotOriginalSize = format_bytes(HotOriginalSize)
54+
| project-away
55+
Folder,
56+
DocString,
57+
AuthorizedPrincipals,
58+
RetentionPolicy,
59+
CachingPolicy,
60+
ShardingPolicy,
61+
MergePolicy,
62+
StreamingIngestionPolicy,
63+
IngestionBatchingPolicy,
64+
RowOrderPolicy,
65+
TableId'
6866
```
6967

7068
This example demonstrates how to get information on all tables in the `myDb` Database.
@@ -93,7 +91,7 @@ This non mandatory parameter determines which Database in your Cluster will be t
9391
9492
> [!NOTE]
9593
>
96-
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md).
94+
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
9795

9896
```yaml
9997
Type: String
@@ -161,7 +159,7 @@ For more information, see [about_CommonParameters](http://go.microsoft.com/fwlin
161159

162160
### System.Data.DataTable
163161

164-
The output type from this cmdlet is determined by the `-OutputType` parameter.
162+
The output type from this cmdlet is determined by the [`-OutputType` parameter](#-outputtype).
165163
By default, this cmdlet outputs `PSObject`.
166164

167165
## NOTES

docs/en-US/Invoke-KustoIngestFromStorage.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,6 +31,7 @@ Invoke-KustoIngestFromStorage
3131
The `Invoke-KustoIngestFromStorage` cmdlet can be used to ingest local or blob storage files into a table
3232
on your Azure Data Explorer Cluster.
3333
For ingestion from a [__Stream__](https://learn.microsoft.com/en-us/dotnet/api/system.io.stream) see [`Invoke-KustoIngestFromStream`](Invoke-KustoIngestFromStream.md).
34+
3435
For more details on Kusto ingestion, checkout
3536
[__Ingest from storage__](https://learn.microsoft.com/en-us/kusto/management/data-ingestion/ingest-from-storage?view=microsoft-fabric).
3637

@@ -65,7 +66,7 @@ Invoke-KustoIngestFromStorage .\myJson.json -Table MyJsonTable -Database myDb -F
6566

6667
> [!NOTE]
6768
>
68-
> This example specifies a format of `multijson` instead `json` because a _JSON Array_ is classified as multijson, while _JSON Lines_ adhere to the `json` format.
69+
> This example specifies a format of `multijson` instead `json` because a _JSON Array_ is classified as `multijson`, while _JSON Lines_ adhere to the `json` format.
6970
> See [__The JSON format__](https://learn.microsoft.com/en-us/azure/data-explorer/ingest-json-formats?tabs=kusto-query-language#the-json-format) for more details.
7071
7172
## PARAMETERS
@@ -76,7 +77,7 @@ This non mandatory parameter determines which Database in your Cluster will be t
7677

7778
> [!NOTE]
7879
>
79-
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md).
80+
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
8081
8182
```yaml
8283
Type: String
@@ -92,7 +93,7 @@ Accept wildcard characters: False
9293
9394
### -Format
9495
95-
This parameter determines the format of the file to be ingested. The default value is __`csv`__.
96+
This parameter determines the format of the file to be ingested. __The default value is `csv`__.
9697

9798
```yaml
9899
Type: DataSourceFormat
@@ -110,7 +111,7 @@ Accept wildcard characters: False
110111
### -IgnoreFirstRecord
111112

112113
This switch indicates that ingestion should ignore the first record of a file.
113-
This property is useful for files in `CSV` and similar formats,
114+
This property is useful for files in CSV and similar formats,
114115
if the first record in the file are the column names.
115116

116117
```yaml

docs/en-US/Invoke-KustoIngestFromStream.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ Invoke-KustoIngestFromStream
2929

3030
## DESCRIPTION
3131

32-
Similar to [`Invoke-KustoIngestFromStorage`](Invoke-KustoIngestFromStorage.md), the `Invoke-KustoIngestFromStream` cmdlet allows you to ingest data into a table on your Azure Data Explorer Cluster, the only difference is the source being a [__Stream__](https://learn.microsoft.com/en-us/dotnet/api/system.io.stream) instead of a path or URI.
32+
Similar to [`Invoke-KustoIngestFromStorage`](Invoke-KustoIngestFromStorage.md), the `Invoke-KustoIngestFromStream` cmdlet allows you to ingest data into a table on your Azure Data Explorer Cluster, the only difference is the source being a [__Stream__](https://learn.microsoft.com/en-us/dotnet/api/system.io.stream) instead of a Path or URI.
3333

3434
## EXAMPLES
3535

@@ -49,7 +49,7 @@ Invoke-KustoIngestFromStream $fs -Table myTable -Database myDb -Format multijson
4949

5050
> [!NOTE]
5151
>
52-
> This example specifies a format of `multijson` instead `json` because a _JSON Array_ is classified as multijson, while _JSON Lines_ adhere to the `json` format.
52+
> This example specifies a format of `multijson` instead `json` because a _JSON Array_ is classified as `multijson`, while _JSON Lines_ adhere to the `json` format.
5353
> See [__The JSON format__](https://learn.microsoft.com/en-us/azure/data-explorer/ingest-json-formats?tabs=kusto-query-language#the-json-format) for more details.
5454
5555
## PARAMETERS
@@ -60,7 +60,7 @@ This non mandatory parameter determines which Database in your Cluster will be t
6060

6161
> [!NOTE]
6262
>
63-
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md).
63+
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
6464
6565
```yaml
6666
Type: String
@@ -94,7 +94,7 @@ Accept wildcard characters: False
9494
### -IgnoreFirstRecord
9595

9696
This switch indicates that ingestion should ignore the first record of a file.
97-
This property is useful for files in `CSV` and similar formats,
97+
This property is useful for files in CSV and similar formats,
9898
if the first record in the file are the column names.
9999

100100
```yaml

docs/en-US/Invoke-KustoQuery.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Invoke-KustoQuery
2626

2727
The `Invoke-KustoQuery` cmdlet allows you to run
2828
[Kusto Query Language (KQL)](https://learn.microsoft.com/en-us/kusto/query/?view=microsoft-fabric) queries or
29-
[T-SQL](https://learn.microsoft.com/en-us/kusto/query/t-sql?view=microsoft-fabric) queries on the tables on a
29+
[T-SQL](https://learn.microsoft.com/en-us/kusto/query/t-sql?view=microsoft-fabric) queries on a
3030
specified Database of your Azure Data Explorer Cluster.
3131

3232
## EXAMPLES
@@ -39,6 +39,10 @@ Invoke-KustoQuery 'search * | summarize count() by $table'
3939

4040
This examples shows how to get the log count summarized by each table.
4141

42+
> [!TIP]
43+
>
44+
> In this example, the database is specified by the database used when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
45+
4246
### Example 2: Run a KQL Query on specified Database
4347

4448
```powershell
@@ -62,11 +66,11 @@ See also [`New-KustoClientRequestProperties`](New-KustoClientRequestProperties.m
6266

6367
### -Database
6468

65-
This non mandatory parameter determines which Database in your Cluster will be targetted by your ingest command.
69+
This non mandatory parameter determines which Database in your Cluster will be targetted by your query command.
6670

6771
> [!NOTE]
6872
>
69-
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md).
73+
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
7074
7175
```yaml
7276
Type: String
@@ -150,7 +154,7 @@ For more information, see [about_CommonParameters](http://go.microsoft.com/fwlin
150154

151155
### System.Data.DataTable
152156

153-
The output type from this cmdlet is determined by the `-OutputType` parameter.
157+
The output type from this cmdlet is determined by the [`-OutputType` parameter](#-outputtype).
154158
By default, this cmdlet outputs `PSObject`.
155159

156160
## NOTES

docs/en-US/New-KustoClientRequestProperties.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
Creates a `ClientRequestProperties` object.
12+
Creates a new `ClientRequestProperties` object.
1313

1414
## SYNTAX
1515

@@ -64,8 +64,8 @@ Invoke-KustoQuery 'SELECT top(10) * FROM MyTable' -RequestProperties $requestPro
6464

6565
> [!TIP]
6666
>
67-
> Out of the supported request properties, this cmdlet only offers `-NoTruncation` (`notruncation`) and `-ServerTimeout` (`servertimeout`).
68-
> The `-Options` parameters is used to add extra options to your request that aren't by default available as a Parameter.
67+
> Out of the supported request properties, this cmdlet offers `-NoTruncation` (`notruncation`) and `-ServerTimeout` (`servertimeout`) as a Parameter.
68+
> The `-Options` Parameter is used to add extra options to your request that aren't by default available.
6969
> See [__Supported request properties__](https://learn.microsoft.com/en-us/kusto/api/rest/request-properties?view=microsoft-fabric#supported-request-properties) for the additional options.
7070
7171
## PARAMETERS

docs/en-US/New-KustoColumnMapping.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
Creates a `ColumnMapping` object.
12+
Creates a new `ColumnMapping` object.
1313

1414
## SYNTAX
1515

@@ -23,7 +23,9 @@ New-KustoColumnMapping
2323

2424
## DESCRIPTION
2525

26-
The `New-KustoColumnMapping` cmdlet is used to create a new object of type `ColumnMapping`, this object can be later on passed as argument to the [`New-KustoIngestionMapping`](New-KustoIngestionMapping.md) cmdlet. See [__Ingestion mappings__](https://learn.microsoft.com/en-us/kusto/management/mappings?view=microsoft-fabric) for more details.
26+
The `New-KustoColumnMapping` cmdlet is used to create a new object of type `ColumnMapping`, this object can be later on passed as argument to the [`New-KustoIngestionMapping`](New-KustoIngestionMapping.md) cmdlet.
27+
28+
See [__Ingestion mappings__](https://learn.microsoft.com/en-us/kusto/management/mappings?view=microsoft-fabric) for more details.
2729

2830
## EXAMPLES
2931

docs/en-US/New-KustoIngestionMapping.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
Creates a `IngestionMapping` object.
12+
Creates a new `IngestionMapping` object.
1313

1414
## SYNTAX
1515

@@ -23,7 +23,7 @@ New-KustoIngestionMapping
2323

2424
## DESCRIPTION
2525

26-
The `New-KustoIngestionMapping` is used to create a new object of type `IngestionMapping` that can be later on passed as argument to the [`Invoke-KustoIngestFromStorage`](Invoke-KustoIngestFromStorage.md), [`Invoke-KustoIngestFromStream`](Invoke-KustoIngestFromStream.md) and [`Set-KustoIngestionMapping`](Set-KustoIngestionMapping.md) commands.
26+
The `New-KustoIngestionMapping` cmdlet is used to create a new object of type `IngestionMapping` that can be later on passed as argument to the [`Invoke-KustoIngestFromStorage`](Invoke-KustoIngestFromStorage.md), [`Invoke-KustoIngestFromStream`](Invoke-KustoIngestFromStream.md) and [`Set-KustoIngestionMapping`](Set-KustoIngestionMapping.md) commands.
2727

2828
## EXAMPLES
2929

docs/en-US/Set-KustoBatchingPolicy.md

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ schema: 2.0.0
99

1010
## SYNOPSIS
1111

12-
Sets ingestion batching policy on a Kusto Database or Table.
12+
Sets the ingestion batching policy on a Kusto Database or Table.
1313

1414
## SYNTAX
1515

@@ -27,7 +27,9 @@ Set-KustoBatchingPolicy
2727

2828
## DESCRIPTION
2929

30-
The `Set-KustoBatchingPolicy` cmdlet is used to alter the batching policy of a Database or specific Table on an Azure Data Explorer Cluster. See [__Ingestion batching policy__](https://learn.microsoft.com/en-us/kusto/management/batching-policy?view=microsoft-fabric) for more details.
30+
The `Set-KustoBatchingPolicy` cmdlet is used to alter the batching policy of a Database or specific Table on an Azure Data Explorer Cluster.
31+
32+
See [__Ingestion batching policy__](https://learn.microsoft.com/en-us/kusto/management/batching-policy?view=microsoft-fabric) for more details.
3133

3234
## EXAMPLES
3335

@@ -52,12 +54,13 @@ $params = @{
5254
MaximumNumberOfItems = 500
5355
MaximumRawDataSizeMB = 1024
5456
}
55-
Set-KustoBatchingPolicy -Database myDb @params
57+
Set-KustoBatchingPolicy @params
5658
```
5759

5860
> [!TIP]
5961
>
60-
> When `-Table` isn't specified, the ingestion batching policy is altered at Database level.
62+
> - When `-Table` isn't specified, the ingestion batching policy is altered at Database level.
63+
> - In this example, the database is specified by the database used when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
6164
6265
## PARAMETERS
6366

@@ -67,7 +70,7 @@ Specifies the name of the Database for which to alter the ingestion batching pol
6770

6871
> [!NOTE]
6972
>
70-
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md).
73+
> If not supplied, the Database used will be the one specified when you called [`Connect-Kusto`](Connect-Kusto.md#-database).
7174
7275
```yaml
7376
Type: String

0 commit comments

Comments
 (0)