Skip to content

Commit 0474e95

Browse files
authored
Updated Release Date
Updated Release Date
1 parent a7d1d1f commit 0474e95

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/hdinsight/hdinsight-release-notes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ To subscribe, click the **watch** button in the banner and watch out for [HDInsi
2020

2121
## Release Information
2222

23-
### Release date: May 27, 2024
23+
### Release date: May 16, 2024
2424

2525
This release note applies to
2626

@@ -47,8 +47,8 @@ For workload specific versions, see [HDInsight 5.x component versions](./hdinsig
4747

4848
* Added API in gateway to get token for Keyvault, as part of the SFI initiative.
4949
* In the new Log monitor `HDInsightSparkLogs` table, for log type `SparkDriverLog`, some of the fields were missing. For example, `LogLevel & Message`. This release adds the missing fields to schemas and fixed formatting for `SparkDriverLog`.
50-
* Livy logs not available in Log Analytics monitoring `SparkDriverLog` table, which was due to an issue with livy log source path and log parsing regex in `SparkLivyLog` configs.
51-
* Any HDInsight cluster, using ADLS Gen2 as a primary storage account can leverrage MSI based access to any of the Azure resources (for example, SQl, Keywault) which is used within the application code.
50+
* Livy logs not available in Log Analytics monitoring `SparkDriverLog` table, which was due to an issue with Livy log source path and log parsing regex in `SparkLivyLog` configs.
51+
* Any HDInsight cluster, using ADLS Gen2 as a primary storage account can leverage MSI based access to any of the Azure resources (for example, SQL, Keyvaults) which is used within the application code.
5252

5353

5454
## :::image type="icon" border="false" source="./media/hdinsight-release-notes/clock.svg"::: Coming soon

0 commit comments

Comments
 (0)