Uploaded image for project: 'Teiid Tools'
  1. Teiid Tools
  2. TEIIDTOOLS-997

Fuse Online DV requires schema field configured for MySQL connections

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: Q220
    • Component/s: teiid-syndesis
    • Labels:
      None
    • Sprint:
      DV Sprint 63
    • Story Points:
      0.1
    • Steps to Reproduce:
      Hide

      Create a Fuse Online MySQL DB connection without schema field populated (per documentation) and then try to access that connection in Fuse Online DV to create a view.

      Show
      Create a Fuse Online MySQL DB connection without schema field populated (per documentation) and then try to access that connection in Fuse Online DV to create a view.

      Description

      In Fuse Online (Red Hat Fuse 7.6) deployed via operator on OCP 4.3 when you configure a MySQL connection, the documentation states to NOT to populate the schema field and to instead add the schema value to the JDBC connection string.

      When you try to use this same MySQL connection in Fuse Online DV view, DV shows the connection as "FAILED" and reports errors when attempting to load the DB metadata.

      Errors produced in the DV pod log:

      ```3:50:54.429 [Asynch Worker1] WARN org.teiid.RUNTIME - TEIID50036 VDB EmployeesMySQL57conn-load.1 model "EmployeesMySQL57" metadata failed to load. Reason:TEIID11029 More than one schema was imported from. It is a best practice to import from only one schema - make sure the schemaPattern property is set or the schemaPattern import property is unique.
      org.teiid.translator.TranslatorException: TEIID11029 More than one schema was imported from. It is a best practice to import from only one schema - make sure the schemaPattern property is set or the schemaPattern import property is unique.
      at org.teiid.translator.jdbc.JDBCMetadataProcessor.getConnectorMetadata(JDBCMetadataProcessor.java:214)
      at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:309)
      at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:70)
      at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:89)
      at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:55)
      at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:51)
      at org.teiid.runtime.AbstractVDBDeployer$2.run(AbstractVDBDeployer.java:291)
      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
      at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      at java.lang.Thread.run(Thread.java:748)
      13:50:54.429 [Asynch Worker1] INFO o.teiid.RUNTIME.VDBLifeCycleListener - TEIID40003 VDB EmployeesMySQL57conn-load.1 is set to FAILED
      13:50:54.430 [Asynch Worker1] INFO o.teiid.RUNTIME.VDBLifeCycleListener - TEIID40120 VDB EmployeesMySQL57conn-load.1 will be removed from the repository
      13:50:54.430 [Asynch Worker1] INFO o.teiid.RUNTIME.VDBLifeCycleListener - TEIID40119 VDB EmployeesMySQL57conn-load.1 removed from the repository```

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                shawkins Steven Hawkins
                Reporter:
                mhockelb Monica Hockelberg
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 30 minutes
                  30m
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 30 minutes
                  30m