[
https://issues.apache.org/jira/browse/AMBARI-12319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14618673#comment-14618673
]
Hudson commented on AMBARI-12319:
---------------------------------
FAILURE: Integrated in Ambari-branch-2.1 #186 (See
[https://builds.apache.org/job/Ambari-branch-2.1/186/])
AMBARI-12319 - Views : S020 Data storage error for Hive view (Mysql db)
(tbeerbower) (tbeerbower:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=21cef44b3e49f6d6ee4eb15fbf567c9fcf43eb5d)
*
ambari-server/src/test/java/org/apache/ambari/server/view/persistence/DataStoreImplTest.java
*
ambari-server/src/main/java/org/apache/ambari/server/view/persistence/DataStoreImpl.java
> Views : S020 Data storage error for Hive view (Mysql db)
> --------------------------------------------------------
>
> Key: AMBARI-12319
> URL: https://issues.apache.org/jira/browse/AMBARI-12319
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
> Fix For: 2.1.0
>
>
> Error setting up a Hive view instance.
> The underlying issue is this ...
> {code}
> Exception [EclipseLink-4002] (Eclipse Persistence Services -
> 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception:
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Row size too
> large. The maximum row size for the used table type, not counting BLOBs, is
> 65535. You have to change some columns to TEXT or BLOBs
> Error Code: 1118
> Call: CREATE TABLE DS_JOBIMPL_6 (DS_id VARCHAR(255) NOT NULL,
> DS_applicationId VARCHAR(4000), DS_confFile VARCHAR(4000), DS_dagId
> VARCHAR(4000), DS_dagName VARCHAR(4000), DS_dataBase VARCHAR(4000),
> DS_dateSubmitted BIGINT, DS_duration BIGINT, DS_forcedContent VARCHAR(4000),
> DS_globalSettings VARCHAR(4000), DS_logFile VARCHAR(4000), DS_owner
> VARCHAR(4000), DS_queryFile VARCHAR(4000), DS_queryId VARCHAR(4000),
> DS_referrer VARCHAR(4000), DS_sessionTag VARCHAR(4000), DS_sqlState
> VARCHAR(4000), DS_status VARCHAR(4000), DS_statusDir VARCHAR(4000),
> DS_statusMessage VARCHAR(4000), DS_title VARCHAR(4000), PRIMARY KEY (DS_id))
> Query: DataModifyQuery(sql="CREATE TABLE DS_JOBIMPL_6 (DS_id VARCHAR(255) NOT
> NULL, DS_applicationId VARCHAR(4000), DS_confFile VARCHAR(4000), DS_dagId
> VARCHAR(4000), DS_dagName VARCHAR(4000), DS_dataBase VARCHAR(4000),
> DS_dateSubmitted BIGINT, DS_duration BIGINT, DS_forcedContent VARCHAR(4000),
> DS_globalSettings VARCHAR(4000), DS_logFile VARCHAR(4000), DS_owner
> VARCHAR(4000), DS_queryFile VARCHAR(4000), DS_queryId VARCHAR(4000),
> DS_referrer VARCHAR(4000), DS_sessionTag VARCHAR(4000), DS_sqlState
> VARCHAR(4000), DS_status VARCHAR(4000), DS_statusDir VARCHAR(4000),
> DS_statusMessage VARCHAR(4000), DS_title VARCHAR(4000), PRIMARY KEY (DS_id))")
> {code}
> Unfortunately, the org.eclipse.persistence.tools.schemaframework makes the
> assumption that if an exception is thrown during table creation it just means
> that the table already exists and it is ignored.
> Need to see if there is a way to surface these exceptions and to adjust the
> default column size so that we don't exceed the MySQL total row size limit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
