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

Teiid Designer randomly changes column names within transformations when migrating legacy MetaMatrix .xmi files

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • 7.4.2
    • 7.4.2
    • None
    • None
    • Hide

      I imported the customers 554 Model Project Set into my 554 Designer so that I can compare, then on the filesystem I unzipped the same 554 Model project set and within Teiid Designer 7.4 (JBDS 4.1) I created the new Teiid Model Projects and just drag and drop the .xmi files into them. The items the customer notes in his original case description are correct. Take for example item #3

      3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation.

      We do change the column name for Baseline_Text to ULN_POC_Name, what's even more strange is where do we even get that name from? If you go back to the Physical model for this column the name is ULN_POC_NM.

      I've attached my exported Teiid Model Project Set containing all the errors.

      Show
      I imported the customers 554 Model Project Set into my 554 Designer so that I can compare, then on the filesystem I unzipped the same 554 Model project set and within Teiid Designer 7.4 (JBDS 4.1) I created the new Teiid Model Projects and just drag and drop the .xmi files into them. The items the customer notes in his original case description are correct. Take for example item #3 3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation. We do change the column name for Baseline_Text to ULN_POC_Name, what's even more strange is where do we even get that name from? If you go back to the Physical model for this column the name is ULN_POC_NM. I've attached my exported Teiid Model Project Set containing all the errors.

    Description

      Customer is using JBDS 4.1 (Teiid Designer 7.4) and is migrating his legacy MetaMatrix models (attached his 554Model project set). And have seen strange things:
      1) In a VBL layer, the SQL transformation dropped the _PL reference to the Physical (source) layer. In another VBL layer, the middle part of the PL table name was simply gone.
      2) A table named STATE_ALPHA_CD in the source models (PL) was changed in the SQL transform at the VBL to STATE_ALPHA_Code.
      3) In Plans_VML, a field named 'Baseline_Text' was changed in two queries to ULN_POC_NAME which naturally did not exist in the source tables of the transformation.
      4) In at least one query, the name of the layer was changed...instead of Transportation_VML, it appeared in the SQL transformation of the query as Transportation_Procs_VML.

      Attachments

        Activity

          People

            mdrillin1@redhat.com Mark Drilling (Inactive)
            rhn-support-dsteigner Deborah Steigner (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: