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

Import VDB not redeployed after backing and changing import properties

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.6
    • Fix Version/s: 8.6
    • Component/s: Import/Export
    • Labels:
      None
    • Steps to Reproduce:
      Hide
      1. Open the Teiid Connection import dialog, select some JDBC datasource
      2. Set Schema Pattern and Table Name Pattern properties to match only one table
      3. Click Next twice, notice the DDL contains only one table as expected
      4. Go Back twice, delete the Table Name Pattern property
      5. Click Next twice, notice the import VDB is not redeployed and the DDL still contains only one table
      Show
      Open the Teiid Connection import dialog, select some JDBC datasource Set Schema Pattern and Table Name Pattern properties to match only one table Click Next twice, notice the DDL contains only one table as expected Go Back twice, delete the Table Name Pattern property Click Next twice, notice the import VDB is not redeployed and the DDL still contains only one table

      Description

      In Teiid Connection import, once the import VDB is deployed, going back in the dialog and changing import properties does not cause the VDB to redeploy – clicking Next in the "Select the target model for the import" step moves directly to the next step, which shows the old DDL.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                blafond Barry LaFond
                Reporter:
                asmigala Andrej Smigala
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: