[jira] [Updated] (HAWQ-1437) Hadoop enabled Kerberos,HAWQ occurs errors

2017-04-19 Thread lynn (JIRA)

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

lynn updated HAWQ-1437:
---
Issue Type: Bug  (was: Wish)

> Hadoop enabled Kerberos,HAWQ occurs errors
> --
>
> Key: HAWQ-1437
> URL: https://issues.apache.org/jira/browse/HAWQ-1437
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: lynn
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> When kerberos enabled with Hadoop , HAWQ create external table from hdfs need 
> principal information, what should I do can create it success?
> postgres=# 
> postgres=# 
> postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month 
> text, num_orders int, total_sales float8)
> postgres-# LOCATION 
> ('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
> postgres-#   FORMAT 'TEXT' (delimiter=E',');
> ERROR:  Invalid URI 
> pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple 
> : missing authority section



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Updated] (HAWQ-1437) Hadoop enabled Kerberos,HAWQ occurs errors

2017-04-19 Thread lynn (JIRA)

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

lynn updated HAWQ-1437:
---
Description: 
When kerberos enabled with Hadoop , HAWQ create external table from hdfs need 
principal information, what should I do can create it success?

postgres=# 
postgres=# 
postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month text, 
num_orders int, total_sales float8)
postgres-# LOCATION 
('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
postgres-#   FORMAT 'TEXT' (delimiter=E',');
ERROR:  Invalid URI 
pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple : 
missing authority section


postgres=# 
postgres=# 
postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month text, 
num_orders int, total_sales float8)
postgres-# LOCATION 
('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA')
postgres-#   FORMAT 'TEXT' (delimiter=E',');
ERROR:  Invalid URI 
pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA
 : missing authority section

  was:
When kerberos enabled with Hadoop , HAWQ create external table from hdfs need 
principal information, what should I do can create it success?

postgres=# 
postgres=# 
postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month text, 
num_orders int, total_sales float8)
postgres-# LOCATION 
('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
postgres-#   FORMAT 'TEXT' (delimiter=E',');
ERROR:  Invalid URI 
pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple : 
missing authority section


> Hadoop enabled Kerberos,HAWQ occurs errors
> --
>
> Key: HAWQ-1437
> URL: https://issues.apache.org/jira/browse/HAWQ-1437
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: lynn
>Assignee: Ed Espino
> Fix For: 2.2.0.0-incubating
>
>
> When kerberos enabled with Hadoop , HAWQ create external table from hdfs need 
> principal information, what should I do can create it success?
> postgres=# 
> postgres=# 
> postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month 
> text, num_orders int, total_sales float8)
> postgres-# LOCATION 
> ('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
> postgres-#   FORMAT 'TEXT' (delimiter=E',');
> ERROR:  Invalid URI 
> pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple 
> : missing authority section
> postgres=# 
> postgres=# 
> postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month 
> text, num_orders int, total_sales float8)
> postgres-# LOCATION 
> ('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA')
> postgres-#   FORMAT 'TEXT' (delimiter=E',');
> ERROR:  Invalid URI 
> pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple&principal=hdfs-bigdatacenter@BIGDATA
>  : missing authority section



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (HAWQ-1437) Hadoop enabled Kerberos,HAWQ occurs errors

2017-04-19 Thread lynn (JIRA)
lynn created HAWQ-1437:
--

 Summary: Hadoop enabled Kerberos,HAWQ occurs errors
 Key: HAWQ-1437
 URL: https://issues.apache.org/jira/browse/HAWQ-1437
 Project: Apache HAWQ
  Issue Type: Wish
  Components: PXF
Reporter: lynn
Assignee: Ed Espino
 Fix For: 2.2.0.0-incubating


When kerberos enabled with Hadoop , HAWQ create external table from hdfs need 
principal information, what should I do can create it success?

postgres=# 
postgres=# 
postgres=# CREATE EXTERNAL TABLE pxf_hdfs_textsimple(location text, month text, 
num_orders int, total_sales float8)
postgres-# LOCATION 
('pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple')
postgres-#   FORMAT 'TEXT' (delimiter=E',');
ERROR:  Invalid URI 
pxf:///mycluster/data/pxf_examples/pxf_hdfs_simple.txt?PROFILE=HdfsTextSimple : 
missing authority section



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (HAWQ-1433) ALTER RESOURCE QUEUE DDL does not check the format of attribute MEMORY_CLUSTER_LIMIT and CORE_CLUSTER_LIMIT

2017-04-19 Thread Shubham Sharma (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975973#comment-15975973
 ] 

Shubham Sharma commented on HAWQ-1433:
--

That appears to be a better solution, thank you for the explanation [~xsheng]

> ALTER RESOURCE QUEUE DDL does not check the format of attribute 
> MEMORY_CLUSTER_LIMIT and CORE_CLUSTER_LIMIT
> ---
>
> Key: HAWQ-1433
> URL: https://issues.apache.org/jira/browse/HAWQ-1433
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Xiang Sheng
> Fix For: 2.3.0.0-incubating
>
>
> Shubham Sharma 
> 2:11 PM (2 hours ago)
> to user, sebastiao.gone. 
> Hello Sebastio, I think you have encountered the following issue - 
> 1 - Problem -  alter resource queue pg_default with 
> (CORE_LIMIT_CLUSTER/MEMORY_LIMIT_CLUSTER=90);
> gpadmin=# select * from pg_resqueue;
>   rsqname   | parentoid | activestats | memorylimit | corelimit | 
> resovercommit | allocpolicy | vsegresourcequota | nvsegupperlimit | 
> nvseglowerlimit | nvseg
> upperlimitperseg | nvseglowerlimitperseg | creationtime |  updatetime 
>   | status 
> +---+-+-+---+---+-+---+-+-+--
> -+---+--+---+
>  pg_root| 0 |  -1 | 100%| 100%  | 
> 2 | even|   |   0 |   0 | 
>  
>0 | 0 |  | 
>   | branch
>  pg_default |  9800 |  20 | 50% | 50%   | 
> 2 | even| mem:256mb |   0 |   0 | 
>  
>0 | 0 |  | 2017-04-12 
> 22:45:55.056102+01 | 
> (2 rows)
> gpadmin=# alter resource queue pg_default with (CORE_LIMIT_CLUSTER=90);
> ALTER QUEUE
> gpadmin=# select * from test;
>  a 
> ---
> (0 rows)
> gpadmin=# \q
> 2 - restart hawq cluster
> 3 - ERROR
> [gpadmin@hdp3 ~]$ psql
> psql (8.2.15)
> Type "help" for help.
> gpadmin=# select * from test;
> WARNING:  FD 31 having errors raised. errno 104
> ERROR:  failed to register in resource manager, failed to receive content 
> (pquery.c:787)
> 3 - alter resource queue pg_default with 
> (CORE_LIMIT_CLUSTER/MEMORY_LIMIT_CLUSTER=50%); --Let's switch back
> ! Not allowed !
> alter resource queue pg_default with (CORE_LIMIT_CLUSTER=50%);
> WARNING:  FD 33 having errors raised. errno 104
> ERROR:  failed to register in resource manager, failed to receive content 
> (resqueuecommand.c:364)
> 4 -  How to fix - Please be extra careful while using this.
> gpadmin=# begin;
> BEGIN
> gpadmin=# set allow_system_table_mods='dml';
> SET
> gpadmin=# select * from pg_resqueue where corelimit=90;
>   rsqname   | parentoid | activestats | memorylimit | corelimit | 
> resovercommit | allocpolicy | vsegresourcequota | nvsegupperlimit | 
> nvseglowerlimit | nvseg
> upperlimitperseg | nvseglowerlimitperseg | creationtime |  updatetime 
>   | status 
> +---+-+-+---+---+-+---+-+-+--
> -+---+--+---+
>  pg_default |  9800 |  20 | 50% | 90| 
> 2 | even| mem:256mb |   0 |   0 | 
>  
>0 | 0 |  | 2017-04-12 
> 22:59:30.092823+01 | 
> (1 row)
> gpadmin=# update pg_resqueue set corelimit='50%' where corelimit=90;
> UPDATE 1
> gpadmin=# commit;
> COMMIT
> 5 - System should be back to normal
> gpadmin=# select * from test;
>  a 
> ---
> (0 rows)
> Regards,
> Shubh



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (HAWQ-1433) ALTER RESOURCE QUEUE DDL does not check the format of attribute MEMORY_CLUSTER_LIMIT and CORE_CLUSTER_LIMIT

2017-04-19 Thread Xiang Sheng (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975968#comment-15975968
 ] 

Xiang Sheng commented on HAWQ-1433:
---

[~outofmemory]
Yes this is the reason why the resqueue ddl fails, but the real reason is that 
the resqueueMgr allow percentage and value when checking format, but only 
support percentage when update. So the ddl passed the format check but cannot 
be executed right. 
So, I remove the format checking part when it's not percentage. It won't pass 
format check now and we will change the format checking and this update else 
block when we support value in the resqueue ddl. 

> ALTER RESOURCE QUEUE DDL does not check the format of attribute 
> MEMORY_CLUSTER_LIMIT and CORE_CLUSTER_LIMIT
> ---
>
> Key: HAWQ-1433
> URL: https://issues.apache.org/jira/browse/HAWQ-1433
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: Resource Manager
>Reporter: Yi Jin
>Assignee: Xiang Sheng
> Fix For: 2.3.0.0-incubating
>
>
> Shubham Sharma 
> 2:11 PM (2 hours ago)
> to user, sebastiao.gone. 
> Hello Sebastio, I think you have encountered the following issue - 
> 1 - Problem -  alter resource queue pg_default with 
> (CORE_LIMIT_CLUSTER/MEMORY_LIMIT_CLUSTER=90);
> gpadmin=# select * from pg_resqueue;
>   rsqname   | parentoid | activestats | memorylimit | corelimit | 
> resovercommit | allocpolicy | vsegresourcequota | nvsegupperlimit | 
> nvseglowerlimit | nvseg
> upperlimitperseg | nvseglowerlimitperseg | creationtime |  updatetime 
>   | status 
> +---+-+-+---+---+-+---+-+-+--
> -+---+--+---+
>  pg_root| 0 |  -1 | 100%| 100%  | 
> 2 | even|   |   0 |   0 | 
>  
>0 | 0 |  | 
>   | branch
>  pg_default |  9800 |  20 | 50% | 50%   | 
> 2 | even| mem:256mb |   0 |   0 | 
>  
>0 | 0 |  | 2017-04-12 
> 22:45:55.056102+01 | 
> (2 rows)
> gpadmin=# alter resource queue pg_default with (CORE_LIMIT_CLUSTER=90);
> ALTER QUEUE
> gpadmin=# select * from test;
>  a 
> ---
> (0 rows)
> gpadmin=# \q
> 2 - restart hawq cluster
> 3 - ERROR
> [gpadmin@hdp3 ~]$ psql
> psql (8.2.15)
> Type "help" for help.
> gpadmin=# select * from test;
> WARNING:  FD 31 having errors raised. errno 104
> ERROR:  failed to register in resource manager, failed to receive content 
> (pquery.c:787)
> 3 - alter resource queue pg_default with 
> (CORE_LIMIT_CLUSTER/MEMORY_LIMIT_CLUSTER=50%); --Let's switch back
> ! Not allowed !
> alter resource queue pg_default with (CORE_LIMIT_CLUSTER=50%);
> WARNING:  FD 33 having errors raised. errno 104
> ERROR:  failed to register in resource manager, failed to receive content 
> (resqueuecommand.c:364)
> 4 -  How to fix - Please be extra careful while using this.
> gpadmin=# begin;
> BEGIN
> gpadmin=# set allow_system_table_mods='dml';
> SET
> gpadmin=# select * from pg_resqueue where corelimit=90;
>   rsqname   | parentoid | activestats | memorylimit | corelimit | 
> resovercommit | allocpolicy | vsegresourcequota | nvsegupperlimit | 
> nvseglowerlimit | nvseg
> upperlimitperseg | nvseglowerlimitperseg | creationtime |  updatetime 
>   | status 
> +---+-+-+---+---+-+---+-+-+--
> -+---+--+---+
>  pg_default |  9800 |  20 | 50% | 90| 
> 2 | even| mem:256mb |   0 |   0 | 
>  
>0 | 0 |  | 2017-04-12 
> 22:59:30.092823+01 | 
> (1 row)
> gpadmin=# update pg_resqueue set corelimit='50%' where corelimit=90;
> UPDATE 1
> gpadmin=# commit;
> COMMIT
> 5 - System should be back to normal
> gpadmin=# select * from test;
>  a 
> ---
> (0 rows)
> Regards,
> Shubh



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Assigned] (HAWQ-1436) Implement RPS High availability on HAWQ

2017-04-19 Thread Hongxu Ma (JIRA)

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

Hongxu Ma reassigned HAWQ-1436:
---

Assignee: Hongxu Ma  (was: Ed Espino)

> Implement RPS High availability on HAWQ
> ---
>
> Key: HAWQ-1436
> URL: https://issues.apache.org/jira/browse/HAWQ-1436
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Security
>Reporter: Hongxu Ma
>Assignee: Hongxu Ma
> Fix For: backlog
>
>
> Once Ranger is configured, HAWQ will rely on RPS to connect to Ranger. A 
> single point RPS may influence the robustness of HAWQ. Thus We need to 
> investigate and design out the way to implement RPS High availability. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Created] (HAWQ-1436) Implement RPS High availability on HAWQ

2017-04-19 Thread Hongxu Ma (JIRA)
Hongxu Ma created HAWQ-1436:
---

 Summary: Implement RPS High availability on HAWQ
 Key: HAWQ-1436
 URL: https://issues.apache.org/jira/browse/HAWQ-1436
 Project: Apache HAWQ
  Issue Type: Sub-task
  Components: Security
Reporter: Hongxu Ma
Assignee: Ed Espino
 Fix For: backlog


Once Ranger is configured, HAWQ will rely on RPS to connect to Ranger. A single 
point RPS may influence the robustness of HAWQ. Thus We need to investigate and 
design out the way to implement RPS High availability. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Comment Edited] (HAWQ-1434) pxf jdbc plugin - case problems with mysql on linux

2017-04-19 Thread Michael Andre Pearce (IG) (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975691#comment-15975691
 ] 

Michael Andre Pearce (IG) edited comment on HAWQ-1434 at 4/19/17 10:49 PM:
---

Hi [~lisakowen],

I have raised a PR for addressing this, it seems there was a force uppercasing 
of the table name in JDBC plugin.
If someone with merge rights can do the honours/merge it for us? Seems 
something is up with the pr jenkins builds btw.

Cheers
Mike


was (Author: michael.andre.pearce):
Hi [~lisakowen],

I have raised a PR for addressing this, it seems there was a force uppercasing 
of the table name in JDBC plugin.
If someone with merge rights can do the honours? Seems something is up with the 
pr jenkins builds btw.

Cheers
Mike

> pxf jdbc plugin - case problems with mysql on linux
> ---
>
> Key: HAWQ-1434
> URL: https://issues.apache.org/jira/browse/HAWQ-1434
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Lisa Owen
>Assignee: Ed Espino
>
> i was trying out the pxf jdbc plug-in and ran into a problem.  mysql on linux 
> is case sensitive, and the jdbc plug-in appears to change the case of 
> dbname.tablename in LOCATION URI to uppercase.  if the db/table were created 
> with lowercase names, the query fails.
> to reproduce:
> login to mysql as root user and create 2 databases:
> $ mysql --user=root mysql -p
> create database mtestdb1;
> create database CAPDB1;
> grant all on mtestdb1.* to 'hawquser1'@'localhost' identified by 'hawquser1';
> grant all on CAPDB1.* to 'hawquser1'@'localhost' identified by 'hawquser1';
> log in to mysql as hawquser1 and create some tables:
> mysql -h localhost -u hawquser1 -p
> use mtestdb1;
> create table mysql_table1( id int );
> insert into mysql_table1 values (1);
> insert into mysql_table1 values (2);
> insert into mysql_table1 values (3);
> use CAPDB1;
> create table CAPTABLE( id int );
> insert into CAPTABLE values (1);
> insert into CAPTABLE values (2);
> insert into CAPTABLE values (3);
> create pxf external tables using jdbc plug-in and try to select from them:
> psql -d testdb
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_table1(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/mtestdb1.mysql_table1?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/mtestdb1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> select * from pxf_jdbc_mysql_table1;
> ERROR:  remote component error (500) from '192.168.64.101:51200':  type  
> Exception report   message   SELECT command denied to user 
> 'hawquser1'@'localhost' for table 'MYSQL_TABLE1'description   The server 
> encountered an internal error that prevented it from fulfilling this request. 
>exception   java.io.IOException: SELECT command denied to user 
> 'hawquser1'@'localhost' for table 'MYSQL_TABLE1' (libchurl.c:897)  (seg5 
> c6401.ambari.apache.org:4 pid=635675) (dispatcher.c:1801)
> DETAIL:  External table pxf_jdbc_mysql_table1
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_caps(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/CAPDB1.CAPTABLE?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/CAPDB1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> select * from pxf_jdbc_mysql_caps;
>  id 
> 
>   1
>   2
>   3
> (3 rows)
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_caps2(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/capdb1.captable?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/CAPDB1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> CREATE EXTERNAL TABLE
> testdb=# select * from pxf_jdbc_mysql_caps2;
>  id 
> 
>   1
>   2
>   3
> (3 rows)
> in this case, the jdbc plugin changes lowercase capdb1.captable to uppercase, 
> the case the table was originally created in in mysql, and the query works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[jira] [Commented] (HAWQ-1434) pxf jdbc plugin - case problems with mysql on linux

2017-04-19 Thread Michael Andre Pearce (IG) (JIRA)

[ 
https://issues.apache.org/jira/browse/HAWQ-1434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15975691#comment-15975691
 ] 

Michael Andre Pearce (IG) commented on HAWQ-1434:
-

Hi [~lisakowen],

I have raised a PR for addressing this, it seems there was a force uppercasing 
of the table name in JDBC plugin.
If someone with merge rights can do the honours? Seems something is up with the 
pr jenkins builds btw.

Cheers
Mike

> pxf jdbc plugin - case problems with mysql on linux
> ---
>
> Key: HAWQ-1434
> URL: https://issues.apache.org/jira/browse/HAWQ-1434
> Project: Apache HAWQ
>  Issue Type: Bug
>  Components: PXF
>Reporter: Lisa Owen
>Assignee: Ed Espino
>
> i was trying out the pxf jdbc plug-in and ran into a problem.  mysql on linux 
> is case sensitive, and the jdbc plug-in appears to change the case of 
> dbname.tablename in LOCATION URI to uppercase.  if the db/table were created 
> with lowercase names, the query fails.
> to reproduce:
> login to mysql as root user and create 2 databases:
> $ mysql --user=root mysql -p
> create database mtestdb1;
> create database CAPDB1;
> grant all on mtestdb1.* to 'hawquser1'@'localhost' identified by 'hawquser1';
> grant all on CAPDB1.* to 'hawquser1'@'localhost' identified by 'hawquser1';
> log in to mysql as hawquser1 and create some tables:
> mysql -h localhost -u hawquser1 -p
> use mtestdb1;
> create table mysql_table1( id int );
> insert into mysql_table1 values (1);
> insert into mysql_table1 values (2);
> insert into mysql_table1 values (3);
> use CAPDB1;
> create table CAPTABLE( id int );
> insert into CAPTABLE values (1);
> insert into CAPTABLE values (2);
> insert into CAPTABLE values (3);
> create pxf external tables using jdbc plug-in and try to select from them:
> psql -d testdb
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_table1(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/mtestdb1.mysql_table1?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/mtestdb1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> select * from pxf_jdbc_mysql_table1;
> ERROR:  remote component error (500) from '192.168.64.101:51200':  type  
> Exception report   message   SELECT command denied to user 
> 'hawquser1'@'localhost' for table 'MYSQL_TABLE1'description   The server 
> encountered an internal error that prevented it from fulfilling this request. 
>exception   java.io.IOException: SELECT command denied to user 
> 'hawquser1'@'localhost' for table 'MYSQL_TABLE1' (libchurl.c:897)  (seg5 
> c6401.ambari.apache.org:4 pid=635675) (dispatcher.c:1801)
> DETAIL:  External table pxf_jdbc_mysql_table1
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_caps(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/CAPDB1.CAPTABLE?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/CAPDB1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> select * from pxf_jdbc_mysql_caps;
>  id 
> 
>   1
>   2
>   3
> (3 rows)
> CREATE EXTERNAL TABLE pxf_jdbc_mysql_caps2(id int)
> LOCATION 
> ('pxf://c6401.ambari.apache.org:51200/capdb1.captable?PROFILE=JDBC&JDBC_DRIVER=com.mysql.jdbc.Driver&DB_URL=jdbc:mysql://localhost:3306/CAPDB1&USER=hawquser1&PASS=hawquser1')
> FORMAT 'CUSTOM' (FORMATTER='pxfwritable_import');
> CREATE EXTERNAL TABLE
> testdb=# select * from pxf_jdbc_mysql_caps2;
>  id 
> 
>   1
>   2
>   3
> (3 rows)
> in this case, the jdbc plugin changes lowercase capdb1.captable to uppercase, 
> the case the table was originally created in in mysql, and the query works.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[GitHub] incubator-hawq pull request #1221: HAWQ-1434

2017-04-19 Thread michaelandrepearce
GitHub user michaelandrepearce opened a pull request:

https://github.com/apache/incubator-hawq/pull/1221

HAWQ-1434

Remove forced upper casing on table name.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/michaelandrepearce/incubator-hawq patch-1

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-hawq/pull/1221.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #1221


commit 6e72e29362f1ec4014f32f85f59356a8e9a5bc15
Author: Michael André Pearce 
Date:   2017-04-19T22:38:28Z

HAWQ-1434

Remove forced upper casing on table name.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[jira] [Resolved] (HAWQ-1422) Provide user-group membership in RPS when requesting access

2017-04-19 Thread Alexander Denissov (JIRA)

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

Alexander Denissov resolved HAWQ-1422.
--
   Resolution: Fixed
Fix Version/s: (was: backlog)
   2.3.0.0-incubating

> Provide user-group membership in RPS when requesting access
> ---
>
> Key: HAWQ-1422
> URL: https://issues.apache.org/jira/browse/HAWQ-1422
> Project: Apache HAWQ
>  Issue Type: Sub-task
>  Components: Security
>Reporter: Alexander Denissov
>Assignee: Alexander Denissov
> Fix For: 2.3.0.0-incubating
>
>
> Currently user group membership is not provided to RangerBasePlugin when 
> access request is made, so group policies will not be applied.
> We need to lookup user group membership, one way to do it is using 
> HadoopCommon library.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


[GitHub] incubator-hawq pull request #1220: HAWQ-1422. Resolve user groups using Hado...

2017-04-19 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-hawq/pull/1220


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---