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/hdinsight/hdinsight-ranger-5-1-migration.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,10 +14,11 @@ HDInsight 5.1 has Apache Ranger version 2.3.0, which is major version upgrade fr
14
14
15
15
Hive Ranger permissions - In 5.1 stack for hive, default hive ranger policies have been added which allow all users to
16
16
17
-
1. Create a database.
18
-
1. All privileges on default database tables and columns.
17
+
* Create a database.
18
+
* Provide all privileges on default database tables and columns.
19
19
20
-
This is different from 4.0 stack where these default policies aren't present.
20
+
This is different from 4.0 stack where these default policies aren't present.
21
+
21
22
This change has been introduced in OSS (open-source software) ranger: [Create Default Policies for Hive Databases - default, Information_schema](https://issues.apache.org/jira/browse/RANGER-2539).
22
23
23
24
Ranger User Interface in HDInsight 4.0 and earlier versions:
@@ -37,33 +38,33 @@ They'll start seeing that new users added to the cluster via LDAP sync via AADS
37
38
38
39
This behavior Is different from 4.0 clusters. Hence if they need to disallow this behavior and have the default permissions same as 4.0, it's required to:
39
40
40
-
1. Disable the **all-databases** policy on ranger UI or edit **all-database** policy to remove **public** group from policy.
41
-
1. Remove **public** group from **default database tables columns** policy on ranger UI.
41
+
* Disable the **all-databases** policy on ranger UI or edit **all-database** policy to remove **public** group from policy.
42
+
* Remove **public** group from **default database tables columns** policy on ranger UI.
42
43
43
44
44
45
Ranger UI is available by clicking on navigating to ranger component and clicking on ranger UI on right side.
45
46
46
47
### User Interface differences
47
48
48
-
* Ranger admin URL has new UI and looks & feel. There's option to switch to the classic Ranger 1.2.0 UI as well:
49
+
* Ranger admin URL has new UI and looks & feel. There's option to switch to the classic Ranger 1.2.0 UI as well.
49
50
50
-
* Root Service of Hive renamed to Hadoop SQL:
51
+
* Root Service of Hive renamed to Hadoop SQL.
51
52
52
-
* Hive/Hadoop SQL also has new capabilities of adding roles under Ranger:
53
+
* Hive/Hadoop SQL also has new capabilities of adding roles under Ranger.
53
54
54
55
## Migration method recommendations
55
56
56
-
As migration path to HDInsight 5.1, the Ranger policies migration between the clusters is recommended only through Ranger import/export options.
57
+
As migration path to HDInsight 5.1, the Ranger policies migration between the clusters is recommended only through Ranger import/export options.
57
58
58
59
> [!NOTE]
59
-
> Reuse of HDInsight 4.1 Ranger database in HDInsight 5.1 Ranger service configurations isn't recommended. Ranger service would fail to restart with following exception due to differences in db schema:
60
+
> Reuse of HDInsight 4.1 Ranger database in HDInsight 5.1 Ranger service configurations isn't recommended. Ranger service would fail to restart with following exception due to differences in db schema.
60
61
61
62
```
62
63
2023-11-01 12:47:20,295 [JISQL] /usr/lib/jvm/lib/mssql-jdbc-7.4.1.jre8.jar:/usr/hdp/current/ranger-admin/jisql/lib/\* org.apache.util.sql.Jisql -user ranger -p '\*\*\*\*\*\*\*\*' -driver mssql -cstring jdbc:sqlserver://xxx\;databaseName=ranger -noheader -trim -c \; -query "delete from x\_db\_version\_h where version = '040' and active = 'N' and updated\_by=xxx.com';"
0 commit comments