Uploaded image for project: 'Teiid'
  1. Teiid
  2. TEIID-5656

DDL based import statement incorrectly parses the foreign schema name

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 12.1
    • Component/s: VDB
    • Labels:
      None

      Description

      The DDL import statement like

      IMPORT FOREIGN SCHEMA public FROM SERVER sampledb INTO accounts OPTIONS("importer.useFullSchemaName" 'false');
      

      does not set the "importer.schemaPattern" to "public" instead it sets to "importer.schemaName" property to "public" in runtime thus invalidating its use.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                rareddy Ramesh Reddy
                Reporter:
                rareddy Ramesh Reddy
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: