Re: Review Request 63284: RANGER-1857:The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[Qiang Zhang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63284/#review189143
---


Ship it!




Ship It!

- Qiang Zhang


On Oct. 25, 2017, 2:58 a.m., pengjianhua wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63284/
> ---
> 
> (Updated Oct. 25, 2017, 2:58 a.m.)
> 
> 
> Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
> Neethiraj, Velmurugan Periasamy, and Qiang Zhang.
> 
> 
> Bugs: RANGER-1857
> https://issues.apache.org/jira/browse/RANGER-1857
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> The value of RANGER_KMS_HOME logic in dba_script.py is as following:
> 
> if is_unix:
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
>   if RANGER_KMS_HOME is None:
>   RANGER_KMS_HOME = os.getcwd()
> elif os_name == "WINDOWS":
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
> 
> The value of RANGER_ADMIN_HOME logic in admin is as following:
> 
> RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
> if RANGER_ADMIN_HOME is None:
>   RANGER_ADMIN_HOME = os.getcwd()
> 
> 
> Diffs
> -
> 
>   kms/scripts/db_setup.py fb891983 
>   kms/scripts/dba_script.py c471f59c 
> 
> 
> Diff: https://reviews.apache.org/r/63284/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> pengjianhua
> 
>

Re: Review Request 63283: RANGER-1856:Installation and access logic are inconsistent for the pid of kms program. Like security admin, they should be consistent.

[Qiang Zhang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63283/#review189140
---


Ship it!




- Qiang Zhang


On Oct. 25, 2017, 2:27 a.m., pengjianhua wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/63283/
> ---
> 
> (Updated Oct. 25, 2017, 2:27 a.m.)
> 
> 
> Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
> Neethiraj, Velmurugan Periasamy, and Qiang Zhang.
> 
> 
> Bugs: RANGER-1856
> https://issues.apache.org/jira/browse/RANGER-1856
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> The directory for the kms pid is constant path in installer.
> 
> pidFolderName='/var/run/ranger_kms'
> if [ ! -d "${pidFolderName}" ]; then
> mkdir -p "${pidFolderName}"
> fi
> 
> The directory for the kms pid is configurable in ranger-kms and 
> ranger-kms-initd.
> 
> if [ -z "${RANGER_KMS_PID_DIR_PATH}" ]
> then
>   RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
> fi
> if [ ! -d "${RANGER_KMS_PID_DIR_PATH}" ]
> then
>   mkdir -p  $RANGER_KMS_PID_DIR_PATH
>   chmod 660 $RANGER_KMS_PID_DIR_PATH
> fi
> pidf=${RANGER_KMS_PID_DIR_PATH}/${RANGER_KMS_PID_NAME}
> 
> The directory for the kms pid can be configured in install.properties.
> 
> #PID file path
> RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
> 
> 
> Diffs
> -
> 
>   kms/scripts/setup.sh 0b13ab4a 
> 
> 
> Diff: https://reviews.apache.org/r/63283/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> pengjianhua
> 
>

Review Request 63284: RANGER-1857:The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[pengjianhua]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63284/
---

Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
Neethiraj, Velmurugan Periasamy, and Qiang Zhang.


Bugs: RANGER-1857
https://issues.apache.org/jira/browse/RANGER-1857


Repository: ranger


Description
---

The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
db_setup.py, Like db_setup.py in admin, we should optimize them.
The value of RANGER_KMS_HOME logic in dba_script.py is as following:

if is_unix:
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
if RANGER_KMS_HOME is None:
RANGER_KMS_HOME = os.getcwd()
elif os_name == "WINDOWS":
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")

The value of RANGER_ADMIN_HOME logic in admin is as following:

RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
if RANGER_ADMIN_HOME is None:
RANGER_ADMIN_HOME = os.getcwd()


Diffs
-

  kms/scripts/db_setup.py fb891983 
  kms/scripts/dba_script.py c471f59c 


Diff: https://reviews.apache.org/r/63284/diff/1/


Testing
---


Thanks,

pengjianhua

[jira] [Updated] (RANGER-1857) The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[peng.jianhua (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peng.jianhua updated RANGER-1857:
-
Attachment: 0001-RANGER-1857-The-value-of-RANGER_KMS_HOME-logic-is-no.patch

> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> ---
>
> Key: RANGER-1857
> URL: https://issues.apache.org/jira/browse/RANGER-1857
> Project: Ranger
>  Issue Type: Bug
>  Components: kms
>Affects Versions: 0.7.1
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
> Attachments: 
> 0001-RANGER-1857-The-value-of-RANGER_KMS_HOME-logic-is-no.patch
>
>
> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> The value of RANGER_KMS_HOME logic in dba_script.py is as following:
> {code}
> if is_unix:
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
>   if RANGER_KMS_HOME is None:
>   RANGER_KMS_HOME = os.getcwd()
> elif os_name == "WINDOWS":
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
> {code}
> The value of RANGER_ADMIN_HOME logic in admin is as following:
> {code}
> RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
> if RANGER_ADMIN_HOME is None:
>   RANGER_ADMIN_HOME = os.getcwd()
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Review Request 63283: RANGER-1856:Installation and access logic are inconsistent for the pid of kms program. Like security admin, they should be consistent.

[pengjianhua]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63283/
---

Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
Neethiraj, Velmurugan Periasamy, and Qiang Zhang.


Bugs: RANGER-1856
https://issues.apache.org/jira/browse/RANGER-1856


Repository: ranger


Description
---

The directory for the kms pid is constant path in installer.

pidFolderName='/var/run/ranger_kms'
if [ ! -d "${pidFolderName}" ]; then
mkdir -p "${pidFolderName}"
fi

The directory for the kms pid is configurable in ranger-kms and 
ranger-kms-initd.

if [ -z "${RANGER_KMS_PID_DIR_PATH}" ]
then
RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
fi
if [ ! -d "${RANGER_KMS_PID_DIR_PATH}" ]
then
mkdir -p  $RANGER_KMS_PID_DIR_PATH
chmod 660 $RANGER_KMS_PID_DIR_PATH
fi
pidf=${RANGER_KMS_PID_DIR_PATH}/${RANGER_KMS_PID_NAME}

The directory for the kms pid can be configured in install.properties.

#PID file path
RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms


Diffs
-

  kms/scripts/setup.sh 0b13ab4a 


Diff: https://reviews.apache.org/r/63283/diff/1/


Testing
---


Thanks,

pengjianhua

[jira] [Updated] (RANGER-1856) Installation and access logic are inconsistent for the pid of kms program. Like security admin, they should be consistent.

[peng.jianhua (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peng.jianhua updated RANGER-1856:
-
Attachment: 0001-RANGER-1856-Installation-and-access-logic-are-incons.patch

> Installation and access logic are inconsistent for the pid of kms program. 
> Like security admin, they should be consistent.
> --
>
> Key: RANGER-1856
> URL: https://issues.apache.org/jira/browse/RANGER-1856
> Project: Ranger
>  Issue Type: Bug
>  Components: kms
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>  Labels: patch
> Attachments: 
> 0001-RANGER-1856-Installation-and-access-logic-are-incons.patch
>
>
> The directory for the kms pid is constant path in installer.
> {code}
> pidFolderName='/var/run/ranger_kms'
> if [ ! -d "${pidFolderName}" ]; then
> mkdir -p "${pidFolderName}"
> fi
> {code}
> The directory for the kms pid is configurable in ranger-kms and 
> ranger-kms-initd.
> {code}
> if [ -z "${RANGER_KMS_PID_DIR_PATH}" ]
> then
>   RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
> fi
> if [ ! -d "${RANGER_KMS_PID_DIR_PATH}" ]
> then
>   mkdir -p  $RANGER_KMS_PID_DIR_PATH
>   chmod 660 $RANGER_KMS_PID_DIR_PATH
> fi
> pidf=${RANGER_KMS_PID_DIR_PATH}/${RANGER_KMS_PID_NAME}
> {code}
> The directory for the kms pid  can be configured in install.properties.
> {code}
> #PID file path
> RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (RANGER-1857) The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[peng.jianhua (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peng.jianhua updated RANGER-1857:
-
Description: 
The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
db_setup.py, Like db_setup.py in admin, we should optimize them.
The value of RANGER_KMS_HOME logic in dba_script.py is as following:
{code}
if is_unix:
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
if RANGER_KMS_HOME is None:
RANGER_KMS_HOME = os.getcwd()
elif os_name == "WINDOWS":
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
{code}
The value of RANGER_ADMIN_HOME logic in admin is as following:
{code}
RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
if RANGER_ADMIN_HOME is None:
RANGER_ADMIN_HOME = os.getcwd()
{code}

  was:
The value of RANGER_KMS_HOME logic is not correct in dba_script.py, Like 
db_setup.py in kms, we should optimize it.
The value of RANGER_KMS_HOME logic in dba_script.py is as following:
{code}
if is_unix:
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
if RANGER_KMS_HOME is None:
RANGER_KMS_HOME = os.getcwd()
elif os_name == "WINDOWS":
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
{code}
The value of RANGER_KMS_HOME logic in db_setup.py is as following:
{code}
RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
if RANGER_ADMIN_HOME is None:
RANGER_ADMIN_HOME = os.getcwd()
{code}


> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> ---
>
> Key: RANGER-1857
> URL: https://issues.apache.org/jira/browse/RANGER-1857
> Project: Ranger
>  Issue Type: Bug
>  Components: kms
>Affects Versions: 0.7.1
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
>
> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> The value of RANGER_KMS_HOME logic in dba_script.py is as following:
> {code}
> if is_unix:
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
>   if RANGER_KMS_HOME is None:
>   RANGER_KMS_HOME = os.getcwd()
> elif os_name == "WINDOWS":
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
> {code}
> The value of RANGER_ADMIN_HOME logic in admin is as following:
> {code}
> RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
> if RANGER_ADMIN_HOME is None:
>   RANGER_ADMIN_HOME = os.getcwd()
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (RANGER-1857) The value of RANGER_KMS_HOME logic is not correct in dba_script.py and db_setup.py, Like db_setup.py in admin, we should optimize them.

[peng.jianhua (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peng.jianhua updated RANGER-1857:
-
Summary: The value of RANGER_KMS_HOME logic is not correct in dba_script.py 
and db_setup.py, Like db_setup.py in admin, we should optimize them.  (was: The 
value of RANGER_KMS_HOME logic is not correct in dba_script.py, Like 
db_setup.py in kms, we should optimize it.)

> The value of RANGER_KMS_HOME logic is not correct in dba_script.py and 
> db_setup.py, Like db_setup.py in admin, we should optimize them.
> ---
>
> Key: RANGER-1857
> URL: https://issues.apache.org/jira/browse/RANGER-1857
> Project: Ranger
>  Issue Type: Bug
>  Components: kms
>Affects Versions: 0.7.1
>Reporter: peng.jianhua
>Assignee: peng.jianhua
>Priority: Minor
>  Labels: patch
>
> The value of RANGER_KMS_HOME logic is not correct in dba_script.py, Like 
> db_setup.py in kms, we should optimize it.
> The value of RANGER_KMS_HOME logic in dba_script.py is as following:
> {code}
> if is_unix:
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
>   if RANGER_KMS_HOME is None:
>   RANGER_KMS_HOME = os.getcwd()
> elif os_name == "WINDOWS":
>   RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
> {code}
> The value of RANGER_KMS_HOME logic in db_setup.py is as following:
> {code}
> RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
> if RANGER_ADMIN_HOME is None:
>   RANGER_ADMIN_HOME = os.getcwd()
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (RANGER-1857) The value of RANGER_KMS_HOME logic is not correct in dba_script.py, Like db_setup.py in kms, we should optimize it.

[peng.jianhua (JIRA)]

peng.jianhua created RANGER-1857:


 Summary: The value of RANGER_KMS_HOME logic is not correct in 
dba_script.py, Like db_setup.py in kms, we should optimize it.
 Key: RANGER-1857
 URL: https://issues.apache.org/jira/browse/RANGER-1857
 Project: Ranger
  Issue Type: Bug
  Components: kms
Affects Versions: 0.7.1
Reporter: peng.jianhua
Assignee: peng.jianhua
Priority: Minor


The value of RANGER_KMS_HOME logic is not correct in dba_script.py, Like 
db_setup.py in kms, we should optimize it.
The value of RANGER_KMS_HOME logic in dba_script.py is as following:
{code}
if is_unix:
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
if RANGER_KMS_HOME is None:
RANGER_KMS_HOME = os.getcwd()
elif os_name == "WINDOWS":
RANGER_KMS_HOME = os.getenv("RANGER_KMS_HOME")
{code}
The value of RANGER_KMS_HOME logic in db_setup.py is as following:
{code}
RANGER_ADMIN_HOME = os.getenv("RANGER_ADMIN_HOME")
if RANGER_ADMIN_HOME is None:
RANGER_ADMIN_HOME = os.getcwd()
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (RANGER-1856) Installation and access logic are inconsistent for the pid of kms program. Like security admin, they should be consistent.

[peng.jianhua (JIRA)]

peng.jianhua created RANGER-1856:


 Summary: Installation and access logic are inconsistent for the 
pid of kms program. Like security admin, they should be consistent.
 Key: RANGER-1856
 URL: https://issues.apache.org/jira/browse/RANGER-1856
 Project: Ranger
  Issue Type: Bug
  Components: kms
Reporter: peng.jianhua
Assignee: peng.jianhua


The directory for the kms pid is constant path in installer.
{code}
pidFolderName='/var/run/ranger_kms'
if [ ! -d "${pidFolderName}" ]; then
mkdir -p "${pidFolderName}"
fi
{code}
The directory for the kms pid is configurable in ranger-kms and 
ranger-kms-initd.
{code}
if [ -z "${RANGER_KMS_PID_DIR_PATH}" ]
then
RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
fi
if [ ! -d "${RANGER_KMS_PID_DIR_PATH}" ]
then
mkdir -p  $RANGER_KMS_PID_DIR_PATH
chmod 660 $RANGER_KMS_PID_DIR_PATH
fi
pidf=${RANGER_KMS_PID_DIR_PATH}/${RANGER_KMS_PID_NAME}
{code}
The directory for the kms pid  can be configured in install.properties.
{code}
#PID file path
RANGER_KMS_PID_DIR_PATH=/var/run/ranger_kms
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62882: Good coding practice-add additional headers in ranger

[Alejandro Fernandez]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62882/#review189112
---


Ship it!




Ship It!

- Alejandro Fernandez


On Oct. 17, 2017, 10:54 a.m., Nikhil P wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62882/
> ---
> 
> (Updated Oct. 17, 2017, 10:54 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Gautam Borad, Abhay 
> Kulkarni, Madhan Neethiraj, Pradeep Agrawal, Ramesh Mani, Selvamohan 
> Neethiraj, Sailaja Polavarapu, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1828
> https://issues.apache.org/jira/browse/RANGER-1828
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Good coding practice-add additional headers in ranger.
> 
> 
> Diffs
> -
> 
>   
> security-admin/src/main/java/org/apache/ranger/security/web/filter/RangerSecurityContextFormationFilter.java
>  721dd44 
> 
> 
> Diff: https://reviews.apache.org/r/62882/diff/2/
> 
> 
> Testing
> ---
> 
> 1)Verified if response contains additional headers on simple ranger(http).
> 2)Verified if response contains additional headers on kerberized ranger.
> 3)Verified if response contains additional headers on SSL ranger(https).
> 4)Verified if response contains additional headers on kerberized+SSL ranger.
> 
> 
> Thanks,
> 
> Nikhil P
> 
>

[jira] [Updated] (RANGER-1850) Impersonation/proxy user support for gaiandb ranger plugin

[Nigel Jones (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nigel Jones updated RANGER-1850:

Attachment: GaianDBAuth.docx

very initial draft. For reference. Will add more info here once ready for review

> Impersonation/proxy user support for gaiandb ranger plugin
> --
>
> Key: RANGER-1850
> URL: https://issues.apache.org/jira/browse/RANGER-1850
> Project: Ranger
>  Issue Type: Sub-task
>  Components: plugins
>Reporter: Nigel Jones
> Attachments: GaianDBAuth.docx
>
>
> Applications/users could connect to gaianDB using their own authentication 
> information - for example userid/password in the simple case. Here the ranger 
> plugin will use that id for policy checks.
> However in a multi tiered architecture a service id (aka non personal 
> account) may be used, and somehow the user to be impersonated is passed via 
> an additional property. This has a number of implications to the system 
> configuration, derby/gaiandb configuration & the plugin implementation. 
> Opening this Jira as a placeholder and will add a document soon (++days) on 
> the same to capture some of the discussion around this area in recent days.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62710: RANGER-1810:Ranger supports plugin to enable, monitor and manage apache Sqoop2

[Nitin Galave]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62710/#review189038
---




security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js
Lines 85 (patched)


I think adding individual conditions for the components to add text field 
with an icon( i.e information) on service form page instead we should provide 
text field with icon option itself in the service definition.
For example :
"configs":
[
{
"itemId": 2,
"name": "sqoop.url",
"type": "string",
"mandatory": true,
"defaultValue": "",
"validationRegEx":"",
"validationMessage": "",
"uiHint":"{ \"infoIcon\":true , \"info\": \"Enter 
information about configuration param\"}",
"label": "Sqoop URL"
}
]


- Nitin Galave


On Oct. 24, 2017, 9:02 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62710/
> ---
> 
> (Updated Oct. 24, 2017, 9:02 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1810
> https://issues.apache.org/jira/browse/RANGER-1810
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Apache Sqoop is a tool designed for efficiently transferring bulk data 
> between Apache Hadoop and structured datastores such as relational databases. 
> You can use Sqoop to import data from external structured datastores into 
> Hadoop Distributed File System or related systems like Hive and HBase. 
> Conversely, Sqoop can be used to extract data from Hadoop and export it to 
> external structured datastores such as relational databases and enterprise 
> data warehouses.It successfully graduated from the Incubator in March of 2012 
> and is now a Top-Level Apache project.
> The Ranger will further expand the influence in the hadoop ecosystem if it 
> supports sqoop authorization. So we should develop sqoop plugin to enable, 
> monitor and manage apache Sqoop2.
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/enable-agent.sh d31a264 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
>  9463ab8 
>   agents-common/src/main/resources/service-defs/ranger-servicedef-sqoop.json 
> PRE-CREATION 
>   plugin-sqoop/.gitignore PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security.xml PRE-CREATION 
>   plugin-sqoop/pom.xml PRE-CREATION 
>   plugin-sqoop/scripts/install.properties PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/RangerServiceSqoop.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopClient.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopResourceMgr.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorResponse.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorsResponse.java
>  PRE-CREATION 
>   pom.xml 3958014 
>   ranger-sqoop-plugin-shim/.gitignore PRE-CREATION 
>   ranger-sqoop-plugin-shim/pom.xml PRE-CREATION 
>   
> ranger-sqoop-plugin-shim/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> afcc290 
>   security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
> 5900c55 
>   src/main/assembly/admin-web.xml 4dc52fd 
>   src/main/assembly/plugin-sqoop.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62710/diff/5/
> 
> 
> Testing
> ---
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

[jira] [Resolved] (RANGER-1831) Write install guide for RANGER-1810

[Qiang Zhang (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qiang Zhang resolved RANGER-1831.
-
   Resolution: Done
Fix Version/s: master
   1.0.0

> Write install guide for RANGER-1810
> ---
>
> Key: RANGER-1831
> URL: https://issues.apache.org/jira/browse/RANGER-1831
> Project: Ranger
>  Issue Type: Sub-task
>  Components: plugins
>Affects Versions: 1.0.0, master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
>Priority: Minor
>  Labels: newbie, patch
> Fix For: 1.0.0, master
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62710: RANGER-1810:Ranger supports plugin to enable, monitor and manage apache Sqoop2

[Qiang Zhang]

> On 十月 24, 2017, 8:30 a.m., pengjianhua wrote:
> > Please rebuild the patch.
> > error: patch failed: 
> > security-admin/src/main/webapp/scripts/modules/globalize/message/en.js:446
> > error: 
> > security-admin/src/main/webapp/scripts/modules/globalize/message/en.js: 
> > patch does not apply

OK, thanks.


- Qiang


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62710/#review189032
---


On 十月 24, 2017, 9:02 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62710/
> ---
> 
> (Updated 十月 24, 2017, 9:02 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1810
> https://issues.apache.org/jira/browse/RANGER-1810
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Apache Sqoop is a tool designed for efficiently transferring bulk data 
> between Apache Hadoop and structured datastores such as relational databases. 
> You can use Sqoop to import data from external structured datastores into 
> Hadoop Distributed File System or related systems like Hive and HBase. 
> Conversely, Sqoop can be used to extract data from Hadoop and export it to 
> external structured datastores such as relational databases and enterprise 
> data warehouses.It successfully graduated from the Incubator in March of 2012 
> and is now a Top-Level Apache project.
> The Ranger will further expand the influence in the hadoop ecosystem if it 
> supports sqoop authorization. So we should develop sqoop plugin to enable, 
> monitor and manage apache Sqoop2.
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/enable-agent.sh d31a264 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
>  9463ab8 
>   agents-common/src/main/resources/service-defs/ranger-servicedef-sqoop.json 
> PRE-CREATION 
>   plugin-sqoop/.gitignore PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security.xml PRE-CREATION 
>   plugin-sqoop/pom.xml PRE-CREATION 
>   plugin-sqoop/scripts/install.properties PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/RangerServiceSqoop.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopClient.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopResourceMgr.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorResponse.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorsResponse.java
>  PRE-CREATION 
>   pom.xml 3958014 
>   ranger-sqoop-plugin-shim/.gitignore PRE-CREATION 
>   ranger-sqoop-plugin-shim/pom.xml PRE-CREATION 
>   
> ranger-sqoop-plugin-shim/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> afcc290 
>   security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
> 5900c55 
>   src/main/assembly/admin-web.xml 4dc52fd 
>   src/main/assembly/plugin-sqoop.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62710/diff/5/
> 
> 
> Testing
> ---
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

Re: Review Request 62710: RANGER-1810:Ranger supports plugin to enable, monitor and manage apache Sqoop2

[Qiang Zhang]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62710/
---

(Updated 十月 24, 2017, 9:02 a.m.)


Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O hEigeartaigh, 
Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, Selvamohan Neethiraj, 
sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.


Changes
---

Update to the latest code.


Bugs: RANGER-1810
https://issues.apache.org/jira/browse/RANGER-1810


Repository: ranger


Description
---

Apache Sqoop is a tool designed for efficiently transferring bulk data between 
Apache Hadoop and structured datastores such as relational databases. You can 
use Sqoop to import data from external structured datastores into Hadoop 
Distributed File System or related systems like Hive and HBase. Conversely, 
Sqoop can be used to extract data from Hadoop and export it to external 
structured datastores such as relational databases and enterprise data 
warehouses.It successfully graduated from the Incubator in March of 2012 and is 
now a Top-Level Apache project.
The Ranger will further expand the influence in the hadoop ecosystem if it 
supports sqoop authorization. So we should develop sqoop plugin to enable, 
monitor and manage apache Sqoop2.

Our test specialists have rigorously tested this feature.


Diffs (updated)
-

  agents-common/scripts/enable-agent.sh d31a264 
  
agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
 9463ab8 
  agents-common/src/main/resources/service-defs/ranger-servicedef-sqoop.json 
PRE-CREATION 
  plugin-sqoop/.gitignore PRE-CREATION 
  plugin-sqoop/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
  plugin-sqoop/conf/ranger-policymgr-ssl.xml PRE-CREATION 
  plugin-sqoop/conf/ranger-sqoop-audit-changes.cfg PRE-CREATION 
  plugin-sqoop/conf/ranger-sqoop-audit.xml PRE-CREATION 
  plugin-sqoop/conf/ranger-sqoop-security-changes.cfg PRE-CREATION 
  plugin-sqoop/conf/ranger-sqoop-security.xml PRE-CREATION 
  plugin-sqoop/pom.xml PRE-CREATION 
  plugin-sqoop/scripts/install.properties PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
 PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/RangerServiceSqoop.java
 PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopClient.java
 PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopResourceMgr.java
 PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorResponse.java
 PRE-CREATION 
  
plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorsResponse.java
 PRE-CREATION 
  pom.xml 3958014 
  ranger-sqoop-plugin-shim/.gitignore PRE-CREATION 
  ranger-sqoop-plugin-shim/pom.xml PRE-CREATION 
  
ranger-sqoop-plugin-shim/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
 PRE-CREATION 
  security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js afcc290 
  security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
5900c55 
  src/main/assembly/admin-web.xml 4dc52fd 
  src/main/assembly/plugin-sqoop.xml PRE-CREATION 


Diff: https://reviews.apache.org/r/62710/diff/5/

Changes: https://reviews.apache.org/r/62710/diff/4-5/


Testing
---

Our test specialists have rigorously tested this feature.


Thanks,

Qiang Zhang

Re: Review Request 63145: This JAVA_VERSION_REQUIRED configuration item is invalid in security admin installer, we should enable it to control the necessary java version.

[pengjianhua]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/63145/
---

(Updated 十月 24, 2017, 8:39 a.m.)


Review request for ranger, Alok Lal, Ankita Sinha, Don Bosco Durai, Colm O 
hEigeartaigh, Gautam Borad, Madhan Neethiraj, Ramesh Mani, Selvamohan 
Neethiraj, Velmurugan Periasamy, and Qiang Zhang.


Bugs: RANGER-1846
https://issues.apache.org/jira/browse/RANGER-1846


Repository: ranger


Description
---

The java version must be equal to or more than 1.8 when we set db_ssl_enabled 
equal to true.
This JAVA_VERSION_REQUIRED configuration item is invalid in security admin 
installer, we should enable it to control the necessary java version.


Diffs (updated)
-

  security-admin/scripts/setup.sh 468e8a0b 


Diff: https://reviews.apache.org/r/63145/diff/4/

Changes: https://reviews.apache.org/r/63145/diff/3-4/


Testing
---


Thanks,

pengjianhua

Re: Review Request 62710: RANGER-1810:Ranger supports plugin to enable, monitor and manage apache Sqoop2

[pengjianhua]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/62710/#review189032
---



Please rebuild the patch.
error: patch failed: 
security-admin/src/main/webapp/scripts/modules/globalize/message/en.js:446
error: security-admin/src/main/webapp/scripts/modules/globalize/message/en.js: 
patch does not apply

- pengjianhua


On 十月 23, 2017, 9 a.m., Qiang Zhang wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62710/
> ---
> 
> (Updated 十月 23, 2017, 9 a.m.)
> 
> 
> Review request for ranger, Ankita Sinha, Don Bosco Durai, Colm O 
> hEigeartaigh, Gautam Borad, Madhan Neethiraj, pengjianhua, Ramesh Mani, 
> Selvamohan Neethiraj, sam  rome, Venkat Ranganathan, and Velmurugan Periasamy.
> 
> 
> Bugs: RANGER-1810
> https://issues.apache.org/jira/browse/RANGER-1810
> 
> 
> Repository: ranger
> 
> 
> Description
> ---
> 
> Apache Sqoop is a tool designed for efficiently transferring bulk data 
> between Apache Hadoop and structured datastores such as relational databases. 
> You can use Sqoop to import data from external structured datastores into 
> Hadoop Distributed File System or related systems like Hive and HBase. 
> Conversely, Sqoop can be used to extract data from Hadoop and export it to 
> external structured datastores such as relational databases and enterprise 
> data warehouses.It successfully graduated from the Incubator in March of 2012 
> and is now a Top-Level Apache project.
> The Ranger will further expand the influence in the hadoop ecosystem if it 
> supports sqoop authorization. So we should develop sqoop plugin to enable, 
> monitor and manage apache Sqoop2.
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Diffs
> -
> 
>   agents-common/scripts/enable-agent.sh d31a264 
>   
> agents-common/src/main/java/org/apache/ranger/plugin/store/EmbeddedServiceDefsUtil.java
>  9463ab8 
>   agents-common/src/main/resources/service-defs/ranger-servicedef-sqoop.json 
> PRE-CREATION 
>   plugin-sqoop/.gitignore PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-policymgr-ssl.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-audit.xml PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security-changes.cfg PRE-CREATION 
>   plugin-sqoop/conf/ranger-sqoop-security.xml PRE-CREATION 
>   plugin-sqoop/pom.xml PRE-CREATION 
>   plugin-sqoop/scripts/install.properties PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/RangerServiceSqoop.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopClient.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/SqoopResourceMgr.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorResponse.java
>  PRE-CREATION 
>   
> plugin-sqoop/src/main/java/org/apache/ranger/services/sqoop/client/json/model/SqoopConnectorsResponse.java
>  PRE-CREATION 
>   pom.xml 3958014 
>   ranger-sqoop-plugin-shim/.gitignore PRE-CREATION 
>   ranger-sqoop-plugin-shim/pom.xml PRE-CREATION 
>   
> ranger-sqoop-plugin-shim/src/main/java/org/apache/ranger/authorization/sqoop/authorizer/RangerSqoopAuthorizer.java
>  PRE-CREATION 
>   security-admin/src/main/webapp/scripts/models/BackboneFormDataType.js 
> 3f8697e 
>   security-admin/src/main/webapp/scripts/modules/globalize/message/en.js 
> 811db0c 
>   src/main/assembly/admin-web.xml 4dc52fd 
>   src/main/assembly/plugin-sqoop.xml PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62710/diff/4/
> 
> 
> Testing
> ---
> 
> Our test specialists have rigorously tested this feature.
> 
> 
> Thanks,
> 
> Qiang Zhang
> 
>

[jira] [Resolved] (RANGER-1844) Ranger admin support hdfs HA configuration when creating hdfs service.

[peng.jianhua (JIRA)]

 [ 
https://issues.apache.org/jira/browse/RANGER-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

peng.jianhua resolved RANGER-1844.
--
   Resolution: Fixed
Fix Version/s: master
   1.0.0

> Ranger admin support hdfs HA configuration when creating hdfs service.
> --
>
> Key: RANGER-1844
> URL: https://issues.apache.org/jira/browse/RANGER-1844
> Project: Ranger
>  Issue Type: New Feature
>  Components: plugins, Ranger
>Affects Versions: master
>Reporter: Qiang Zhang
>Assignee: Qiang Zhang
> Fix For: 1.0.0, master
>
> Attachments: 
> 0001-RANGER-1844-Ranger-admin-support-hdfs-HA-configurati.patch
>
>
> In ranger admin, when creating a hdfs service, if hdfs cluster is in HA 
> mode,you have to config a lot of configs in hdfs_dev,such as:
> Namenode URL *=hdfs://hdfscluster
> ===Add New Configurations===
> dfs.nameservices=hdfscluster
> dfs.client.failover.proxy.provider.hdfscluster=org.apache.hadoop.hdfs.server.namenode.ha.ConfiguredFailoverProxyProvider
> dfs.ha.namenodes.hdfscluster=nn1,nn2
> dfs.namenode.rpc-address.hdfscluster.nn1=hdfs://10.43.159.240:9000
> dfs.namenode.rpc-address.hdfscluster.nn2=hdfs://10.43.159.245:9000
> ===End of add New Configurations===
> And other big data components such as hbase,hive and so on can support HA 
> without config
> lots of "Add New Configurations",it is easy to config a url. like zk queue 
> configuration in hbase,like jdbc url in hive.  In hdfs service, only need 
> to config "fs.default.name" :
> Namenode URL *=hdfs://hdfscluster 
>  【old】 
> Namenode URL *=hdfs://dap230-183:9000,hdfs://dap229-183:9000【new】
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)