You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "Hung Tran (JIRA)" <ji...@apache.org> on 2019/02/21 17:12:00 UTC
[jira] [Resolved] (GOBBLIN-666) Data too long for column
'property_key'
[ https://issues.apache.org/jira/browse/GOBBLIN-666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hung Tran resolved GOBBLIN-666.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.15.0
Issue resolved by pull request #2539
[https://github.com/apache/incubator-gobblin/pull/2539]
> Data too long for column 'property_key'
> ---------------------------------------
>
> Key: GOBBLIN-666
> URL: https://issues.apache.org/jira/browse/GOBBLIN-666
> Project: Apache Gobblin
> Issue Type: Bug
> Components: state-management
> Affects Versions: 0.14.0
> Reporter: Francis Laforge
> Assignee: Hung Tran
> Priority: Major
> Fix For: 0.15.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We may have following error :
> {noformat}
> com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'property_key' at row 1
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3876)
> at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3814)
> at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2478)
> at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2625)
> at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2551)
> at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
> at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2073)
> at com.mysql.jdbc.PreparedStatement.executeUpdateInternal(PreparedStatement.java:2009)
> at com.mysql.jdbc.PreparedStatement.executeLargeUpdate(PreparedStatement.java:5094)
> at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1994)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
> at org.apache.gobblin.metastore.database.DatabaseJobHistoryStoreV100.updateProperty(DatabaseJobHistoryStoreV100.java:523)
> at org.apache.gobblin.metastore.database.DatabaseJobHistoryStoreV100.put(DatabaseJobHistoryStoreV100.java:244)
> at org.apache.gobblin.metastore.DatabaseJobHistoryStore.put(DatabaseJobHistoryStore.java:77)
> at org.apache.gobblin.runtime.JobContext.storeJobExecutionInfo(JobContext.java:406)
> at org.apache.gobblin.runtime.AbstractJobLauncher.launchJob(AbstractJobLauncher.java:490)
> at org.apache.gobblin.scheduler.JobScheduler.runJob(JobScheduler.java:479)
> at org.apache.gobblin.scheduler.JobScheduler.runJob(JobScheduler.java:435)
> at org.apache.gobblin.scheduler.JobScheduler$GobblinJob.executeImpl(JobScheduler.java:598)
> at org.apache.gobblin.scheduler.BaseGobblinJob.execute(BaseGobblinJob.java:58)
> at org.quartz.core.JobRunShell.run(JobRunShell.java:202)
> at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573){noformat}
> when property_key is too long. Unfortunately, some keys are automatically generated and can be very long. For example when using parquet with partitionning we may have this type of key :
> {noformat}
> construct.final.state.FORK_OPERATOR.0.WRITER.RecordsWritten_partition1=val_name_1/partition2=2017-12-08/partition3=8/partition4=22812
> {noformat}
> which is more than 128 char given in the mysql table definition.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)