Skip to content

Commit 41fb8c4

Browse files
Merge pull request #262387 from v-akarnase/patch-27
Update troubleshoot-rest-api.md
2 parents 22e9259 + e1a0bd8 commit 41fb8c4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/hdinsight/hbase/troubleshoot-rest-api.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: REST API to query Apache HBase in Azure HDInsight
33
description: This article describes troubleshooting steps when interacting with Apache HBase components on Azure HDInsight clusters.
44
ms.service: hdinsight
55
ms.topic: troubleshooting
6-
ms.date: 12/31/2022
6+
ms.date: 01/04/2024
77
---
88

99
# REST API to query Apache HBase in Azure HDInsight
@@ -16,7 +16,7 @@ Using Apache HBase REST interface to query a table under a namespace other than
1616

1717
## Cause
1818

19-
HBase REST API is only supported when using the default namespace. This is a known issue with regards to using HBase namespaces or making calls that refer to specific GETs on columns with column families with REST server on HDInsight. This is because of a security issue with HDInsight Gateway. When using the API to create a table with a namespace, accessing columns via column families, you need specify the `:` character, which is considered a security problem in the IIS Gateway module.
19+
HBase REST API is only supported when using the default namespace. This is a known issue with regard to use HBase namespaces or making calls that refer to specific GETs on columns with column families with REST server on HDInsight. This is because of a security issue with HDInsight Gateway. When using the API to create a table with a namespace, accessing columns via column families, you need specify the `:` character, which is considered a security problem in the IIS Gateway module.
2020

2121
## Mitigation
2222

0 commit comments

Comments
 (0)