Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. TEIIDDES-2182

Issues with Excel import

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 8.5
    • 8.5
    • Import/Export
    • None
    • Hide

      The excel ddl is attached. You can just use the DDL importer to reproduce the namespace issue.

      Show
      The excel ddl is attached. You can just use the DDL importer to reproduce the namespace issue.

      See comment on this community thread -
      https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable

      There are a couple of issues with this scenario in Designer:
      1)

      org.eclipse.core.runtime.CoreException: An exception occurred while performing an operation
          at org.teiid.designer.ui.util.ErrorHandler.toCoreException(ErrorHandler.java:68)
          at org.teiid.designer.ui.util.ErrorHandler.toExceptionDialog(ErrorHandler.java:115)
          at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportManager.saveUsingDdlDiffReport(TeiidImportManager.java:818)
          at org.teiid.designer.teiidimporter.ui.wizard.TeiidImportWizard.finish(TeiidImportWizard.java:197)
          at org.teiid.designer.ui.common.wizard.AbstractWizard.performFinish(AbstractWizard.java:356)
          at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:827)
          at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:432)
      

      This is a bug with the array init on line 791 of TeiidImportManager

      2) The "CELL_NUMBER" issue is due to Designer not processing the extension properties for excel properly. The incoming namespace on the DDL options (teiid_excel) does not match it's MED namespace in Designer (excel). Need to resolve this disconnect.

              mdrillin1@redhat.com Mark Drilling (Inactive)
              mdrillin1@redhat.com Mark Drilling (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: