[jira] [Commented] (RANGER-1788) Install Ranger admin failure.

["bhavik patel (JIRA)" <ji...@apache.org>]

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

bhavik patel commented on RANGER-1788:
--------------------------------------

[~peng.jianhua] "IGNORE" keyword will work for mysql 5.6 version. For generic solution you can remove ignore keyword or un-comment line below that statement and remove the current line. 
Also provide same fix for ranger-0.7 branch.

> Install Ranger admin failure.
> -----------------------------
>
>                 Key: RANGER-1788
>                 URL: https://issues.apache.org/jira/browse/RANGER-1788
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>    Affects Versions: 1.0.0, master
>            Reporter: peng.jianhua
>            Assignee: peng.jianhua
>            Priority: Critical
>              Labels: patch
>         Attachments: 0001-RANGER-1788-Install-Ranger-admin-failure.patch
>
>
> 1. Fetch latest source using "git clone https://git-wip-us.apache.org/repos/asf/ranger.git" command.
> 2. Build.
> 3. Install Ranger admin.
> Error information is as following:
> {code}
> 2017-09-16 23:39:54,695  [E] 028-add-unique-constraint-on-table-x_group.sql import failed!
> {code}
> Execute 028-add-unique-constraint-on-table-x_group.sql file separately, there are following:
> {code}
> 1. error code:1314
> ALTER VIEW is not allowed in stored procedures
> 2. error code:1305
> PROCEDURE ranger.create_unique_constraint_on_groupname does not exist
> {code}
> This issue was introduced by the RANGER-1765.
> {code}
> mysql> source /diskc/installranger/run/ranger-1.0.0-admin/db/mysql/patches/028-add-unique-constraint-on-table-x_group.sql
> Query OK, 0 rows affected, 1 warning (0.00 sec)
> ERROR 1314 (0A000): ALTER VIEW is not allowed in stored procedures
> ERROR 1305 (42000): PROCEDURE ranger.create_unique_constraint_on_groupname does not exist
> Query OK, 0 rows affected, 1 warning (0.00 sec)
> {code}
> Reason:
> {code}
> As of MySQL 5.7.4, the IGNORE clause for ALTER TABLE is removed and its use produces an error.
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)