Hi Mohammad, I'm using 2.3.2-cdh3u4. Is there a work around for this version?
Thanks, Tim On Thu, Mar 21, 2013 at 12:33 AM, Mohammad Islam <[email protected]> wrote: > Hi Tim, > Which Oozie version are you using? > We knew this was common for earlier versions such as 2.x. > > Regards, > Mohammad > > > ________________________________ > From: Tim Chan <[email protected]> > To: [email protected] > Sent: Wednesday, March 20, 2013 3:36 PM > Subject: org.apache.openjpa.persistence.PersistenceException: Data > truncation: Data too long for column 'action_xml' at row 1 > > I'm using a dataset that goes creates a unique path for a given day: > > <uri-template>${nameNode}/blah/${YEAR}/${MONTH}/${DAY}</uri-template> > > > I'm passing in start/end instance dates that are 230 days apart. > > I'm receiving this error in the oozie logs: > > > 2013-03-20 15:12:42,939 INFO CoordActionInputCheckCommand:525 - USER[?] > GROUP[users] TOKEN[] APP[vehicle-recommender-coord] > JOB[0010238-130305114927051-oozie-oozi-C] ACTION[-] > [0010238-130305114927051-oozie-oozi-C@1]::ActionInputCheck:: > > File:hdfs://namenode:8020/dwh-data/pre-processed/userevent/2012/07/31/apachelogline_event_eventdata_entries_values, > Exists? :true > 2013-03-20 15:12:42,970 WARN CoordActionInputCheckCommand:528 - USER[?] > GROUP[users] TOKEN[] APP[vehicle-recommender-coord] > JOB[0010238-130305114927051-oozie-oozi-C] ACTION[-] > 0010238-130305114927051-oozie-oozi-C@1: Exception occurs: > org.apache.oozie.store.StoreException: E0607: Other error in operation > [updateCoordinatorAction], The transaction has been rolled back. See the > nested exceptions for details on the errors that occurred. STORE is active > true > org.apache.oozie.store.StoreException: E0607: Other error in operation > [updateCoordinatorAction], The transaction has been rolled back. See the > nested exceptions for details on the errors that occurred. > at > > org.apache.oozie.store.CoordinatorStore.doOperation(CoordinatorStore.java:440) > at > > org.apache.oozie.store.CoordinatorStore.updateCoordActionMin(CoordinatorStore.java:372) > at > > org.apache.oozie.command.coord.CoordActionInputCheckCommand.call(CoordActionInputCheckCommand.java:180) > at > > org.apache.oozie.command.coord.CoordActionInputCheckCommand.execute(CoordActionInputCheckCommand.java:426) > at > > org.apache.oozie.command.coord.CoordActionInputCheckCommand.execute(CoordActionInputCheckCommand.java:50) > at org.apache.oozie.command.Command.call(Command.java:202) > at > > org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:132) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) > at java.lang.Thread.run(Thread.java:662) > Caused by: <openjpa-1.2.1-r752877:753278 fatal general error> > org.apache.openjpa.persistence.PersistenceException: The transaction has > been rolled back. See the nested exceptions for details on the errors that > occurred. > at > > org.apache.openjpa.kernel.BrokerImpl.newFlushException(BrokerImpl.java:2163) > at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:2010) > at > org.apache.openjpa.kernel.BrokerImpl.flushSafe(BrokerImpl.java:1908) > at org.apache.openjpa.kernel.BrokerImpl.flush(BrokerImpl.java:1679) > at > org.apache.openjpa.kernel.QueryImpl.isInMemory(QueryImpl.java:956) > at org.apache.openjpa.kernel.QueryImpl.execute(QueryImpl.java:838) > at > org.apache.openjpa.kernel.QueryImpl.updateAll(QueryImpl.java:888) > at > > org.apache.openjpa.kernel.DelegatingQuery.updateAll(DelegatingQuery.java:581) > at > org.apache.openjpa.persistence.QueryImpl.executeUpdate(QueryImpl.java:338) > at > org.apache.oozie.store.CoordinatorStore$10.call(CoordinatorStore.java:380) > at > org.apache.oozie.store.CoordinatorStore$10.call(CoordinatorStore.java:372) > at > > org.apache.oozie.store.CoordinatorStore.doOperation(CoordinatorStore.java:425) > ... 9 more > Caused by: <openjpa-1.2.1-r752877:753278 nonfatal general error> > org.apache.openjpa.persistence.PersistenceException: Data truncation: Data > too long for column 'action_xml' at row 1 > FailedObject: prepstmnt 1355041833 UPDATE COORD_ACTIONS SET action_xml = ?, > missing_dependencies = ?, last_modified_time = ?, status = ? WHERE id = ? > [org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement] > at > org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232) > at > > org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197) > at > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102) > at > org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72) > at > > org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushBatch(BatchingPreparedStatementManagerImpl.java:195) > at > > org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:63) > at > > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89) > at > > org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72) > at > > org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717) > > > I do not receive this error when the start/end instance dates are 120 days > apart. > > Is not reasonable to be able to accomodate 230 input paths? > -- [image: Monkey] Tim Chan // [email protected] // 213.784.2523
