phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2817) Phoenix-Spark plugin doesn't work in secured env
Date Mon, 04 Apr 2016 05:59:25 GMT


Hadoop QA commented on PHOENIX-2817:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 8916eb791b37a2444135abba7c4b640630eb859c.
  ATTACHMENT ID: 12796771

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:red}-1 javadoc{color}.  The javadoc tool appears to have generated 24 warning messages.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 lineLengths{color}.  The patch does not introduce lines longer than 100

    {color:green}+1 core tests{color}.  The patch passed unit tests in .

Test results:
Javadoc warnings:
Console output:

This message is automatically generated.

> Phoenix-Spark plugin doesn't work in secured env
> ------------------------------------------------
>                 Key: PHOENIX-2817
>                 URL:
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.4.0, 4.7.0
>            Reporter: Sergey Soldatov
>            Assignee: Sergey Soldatov
>         Attachments: PHOENIX-2817-1.patch
> When phoenix spark plugin is used with secured setup any attempt to perform operation
with PhoenixRDD cause an exception : 
> {noformat}
> Caused by: Login failure for 2181 from keytab /hbase:
Unable to obtain password from user
> 	at
> 	at
> 	at$SecureHadoopUser.login(
> 	at
> 	at org.apache.phoenix.query.ConnectionQueryServicesImpl.openConnection(
> 	... 107 more
> Caused by: Unable to obtain password from user
> 	at
> 	at
> 	at
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at
> 	at$000(
> 	at$
> 	at$
> 	at Method)
> 	at
> 	at
> 	at
> 	... 111 more
> {noformat}
> The reason is the how zkUrl is handled in PhoenixRDD: 
> {noformat}
> config.set(HConstants.ZOOKEEPER_QUORUM, url )
> {noformat}
> At the same time the {{ConnectionUtil.getInputConnection}} expects to see all parameters
(quorum address, port, znodeParent) in different Configuration properties. As the result it
gets default values for port and znodeParent and adds it to the provided url, so the {{PhoenixEmbededDriver.create}}
receives something like that:
> {noformat}
> jdbc:phoenix:quorum:2181:/hbase-secure:2181:/hbase
> {noformat}
> and consider 2 fields as kerberos principal and keytab.  

This message was sent by Atlassian JIRA

View raw message