Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When importing jobs from Talend 6.5 into Talend Open Studio for Big Data 7.0 import process aborts and we see the following messages on the log file.
!ENTRY org.talend.platform.logging 2 0 2018-06-05 12:13:05.164
!MESSAGE 2018-06-05 12:13:05,163 WARN org.talend.migrationtool.MigrationToolService - Incomplete import item su_edt_gen (migration task NewJDBCMigrationTask failed)
!STACK 0
java.lang.NumberFormatException: For input string: "(-1)"
at sun.misc.FloatingDecimal.readJavaFormatString(Unknown Source)
at sun.misc.FloatingDecimal.parseDouble(Unknown Source)
at java.lang.Double.parseDouble(Unknown Source)
at org.talend.core.model.metadata.MetadataToolAvroHelper.convertToAvro(MetadataToolAvroHelper.java:176)
at org.talend.core.model.metadata.MetadataToolAvroHelper.convertToAvro(MetadataToolAvroHelper.java:67)
at org.talend.designer.core.generic.utils.SchemaUtils.convertTalendSchemaIntoComponentSchema(SchemaUtils.java:260)
at org.talend.designer.core.generic.model.migration.NewComponentFrameworkMigrationTask$1.transform(NewComponentFrameworkMigrationTask.java:202)
at org.talend.core.model.components.ModifyComponentsAction.searchAndModify(ModifyComponentsAction.java:101)
at org.talend.designer.core.generic.model.migration.NewComponentFrameworkMigrationTask.execute(NewComponentFrameworkMigrationTask.java:249)
at org.talend.core.model.migration.AbstractItemMigrationTask.execute(AbstractItemMigrationTask.java:108)
at org.talend.migrationtool.MigrationToolService.delegateExecuteMigrationTasksForImport(MigrationToolService.java:151)
at org.talend.migrationtool.MigrationToolService.executeMigrationTasksForImport(MigrationToolService.java:116)
at org.talend.repository.items.importexport.handlers.imports.ImportBasicHandler.applyMigrationTasks(ImportBasicHandler.java:1266)
at org.talend.repository.items.importexport.handlers.imports.ImportBasicHandler.doImport(ImportBasicHandler.java:751)
at org.talend.repository.items.importexport.handlers.ImportExportHandlersManager$3$1.importItemRecordsWithRelations(ImportExportHandlersManager.java:697)
at org.talend.repository.items.importexport.handlers.ImportExportHandlersManager$3$1.run(ImportExportHandlersManager.java:556)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313)
at org.talend.repository.items.importexport.handlers.ImportExportHandlersManager$3.run(ImportExportHandlersManager.java:749)
at org.talend.repository.RepositoryWorkUnit.executeRun(RepositoryWorkUnit.java:99)
at org.talend.core.repository.model.AbstractRepositoryFactory.executeRepositoryWorkUnit(AbstractRepositoryFactory.java:258)
at org.talend.repository.localprovider.model.LocalRepositoryFactory.executeRepositoryWorkUnit(LocalRepositoryFactory.java:3420)
at org.talend.core.repository.model.ProxyRepositoryFactory.executeRepositoryWorkUnit(ProxyRepositoryFactory.java:2247)
at org.talend.repository.items.importexport.handlers.ImportExportHandlersManager.importItemRecords(ImportExportHandlersManager.java:761)
at org.talend.repository.items.importexport.ui.wizard.imports.ImportItemsWizardPage$21.run(ImportItemsWizardPage.java:1013)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Can anyone help with this issue?
I had the same issue but the string in my case was "NULL". I found that some integer columns in a schema had the default "NULL". Removing the default allowed the jobs to import.
Check your schemas for the value "(-1)".
This is a bug on talend open studio for big data 7.0. I created issue TUP-20239 on talendforge regarding this. It is fixed on TOS 7.1.2