You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ranger.apache.org by "zhangxiong (JIRA)" <ji...@apache.org> on 2017/02/08 09:26:41 UTC

[jira] [Updated] (RANGER-1364) MySQLPLRunner take wrong start index when traverse the resultSet metadata

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

zhangxiong updated RANGER-1364:
-------------------------------
    Summary: MySQLPLRunner take wrong start index when traverse the resultSet metadata  (was: MySQLPLRunner take wrong start index when traverse then resultSet metadata)

> MySQLPLRunner take wrong start index when traverse the resultSet metadata
> -------------------------------------------------------------------------
>
>                 Key: RANGER-1364
>                 URL: https://issues.apache.org/jira/browse/RANGER-1364
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: Ranger
>            Reporter: zhangxiong
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> when we install the admin,the dba_script.py would call MySQLRunner to run some sqls from file or input string.But MySQLRunner take wrong start index when traverse then resultSet colname.According to jdbc specification,we should get the rs first column name with index 1 NOT 0. But take 0 as start index is what ranger does.



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