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

["Qiang Zhang (JIRA)" <ji...@apache.org>]

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

Qiang Zhang commented on RANGER-1364:
-------------------------------------

[~leslizhang], Please use solr to save Audit information. Audit DB support has been removed from RANGER-900. You can also refer to RANGER-1286.

> MySQLPLRunner take wrong start index when traverse then 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)