You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hawq.apache.org by "Vineet Goel (JIRA)" <ji...@apache.org> on 2017/07/12 18:51:00 UTC
[jira] [Updated] (HAWQ-1469) Don't expose RPS warning messages to
command line
[ https://issues.apache.org/jira/browse/HAWQ-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vineet Goel updated HAWQ-1469:
------------------------------
Fix Version/s: (was: backlog)
2.3.0.0-incubating
> Don't expose RPS warning messages to command line
> -------------------------------------------------
>
> Key: HAWQ-1469
> URL: https://issues.apache.org/jira/browse/HAWQ-1469
> Project: Apache HAWQ
> Issue Type: Sub-task
> Components: Security
> Reporter: Lin Wen
> Assignee: Lin Wen
> Fix For: 2.3.0.0-incubating
>
>
> RPS service address exposing to end-user is not secure, and we should not expose it out.
> **Case 1: When master RPS is down, changing to standby RPS**
> Current behavior
> ```
> postgres=# select * from a;
> WARNING: ranger plugin service from http://test1:8432/rps is unavailable : Couldn't connect to server, try another http://test5:8432/rps
> ERROR: permission denied for relation(s): public.a
> ```
> Warning should be removed.
> Expected
> ```
> postgres=# select * from a;
> ERROR: permission denied for relation(s): public.a
> ```
> **Case 2: When both RPS are down, should only print that RPS is unavailable.**
> Current Behavior:
> ```
> postgres=# select * from a;
> WARNING: ranger plugin service from http://test5:8432/rps is unavailable : Couldn't connect to server, try another http://test1:8432/rps
> ERROR: ranger plugin service from http://test1:8432/rps is unavailable : Couldn't connect to server. (rangerrest.c:463)
> ```
> Expected
> ```
> postgres=# select * from a;
> ERROR: ranger plugin service is unavailable : Couldn't connect to server. (rangerrest.c:463)
> ```
> The warning message should be printed in cvs log file.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)