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

Pradeep Agrawal updated RANGER-1378:
------------------------------------
    Summary: Update MySQL Schema to fix issues related to only_full_group_by 
restriction of MySQL 5.7 version  (was: There is Page not found (404) error 
when clicking Admin tab in Audit.)

> Update MySQL Schema to fix issues related to only_full_group_by restriction 
> of MySQL 5.7 version
> ------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1378
>                 URL: https://issues.apache.org/jira/browse/RANGER-1378
>             Project: Ranger
>          Issue Type: Bug
>          Components: admin
>            Reporter: Qiang Zhang
>            Assignee: Pradeep Agrawal
>              Labels: patch
>         Attachments: 
> 0001-RANGER-1378-There-is-Page-not-found-404-error-when-c.patch, 
> Audit-Admin-error.png, RANGER-1378-1.patch
>
>
> There is Page not found (404) error when clicking Admin tab in Audit.
> Wrong reason: There is no vx_trx_log table in ranger database.
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: 
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #1 of 
> SELECT list is not in GROUP BY clause and contains nonaggregated column 
> 'ranger.x_trx_log.id' which is not functionally dependent on columns in GROUP 
> BY clause; this is incompatible with sql_mode=only_full_group_by
> Error Code: 1055
> Call: SELECT ID AS a1, ACTION AS a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, 
> CREATE_TIME AS a5, NEW_VAL AS a6, CLASS_TYPE AS a7, OBJECT_ID AS a8, 
> OBJECT_NAME AS a9, PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, 
> PARENT_OBJECT_NAME AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, 
> SESS_TYPE AS a16, TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM 
> vx_trx_log ORDER BY CREATE_TIME DESC LIMIT ?, ?
>       bind => [2 parameters bound]
> Query: ReadAllQuery(referenceClass=VXXTrxLog sql="SELECT ID AS a1, ACTION AS 
> a2, ADDED_BY_ID AS a3, ATTR_NAME AS a4, CREATE_TIME AS a5, NEW_VAL AS a6, 
> CLASS_TYPE AS a7, OBJECT_ID AS a8, OBJECT_NAME AS a9, 
> PARENT_OBJECT_CLASS_TYPE AS a10, PARENT_OBJECT_ID AS a11, PARENT_OBJECT_NAME 
> AS a12, PREV_VAL AS a13, REQ_ID AS a14, SESS_ID AS a15, SESS_TYPE AS a16, 
> TRX_ID AS a17, UPDATE_TIME AS a18, UPD_BY_ID AS a19 FROM vx_trx_log ORDER BY 
> CREATE_TIME DESC LIMIT ?, ?")



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

Reply via email to