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

Large transformation SQL is not exported to INDEX file.

XMLWordPrintable

    • Hide

      1. copy the attached test.csv somewhere you like
      2. run Import From Flat File Source wizard to create a data source for the test.csv.
      (Right click the project >Import >File Source (Flat) >>Source and View Model)
      3. create vdb and put the models to the vdb.
      4. See $WORKSPACE/.metadata/.plugins/org.teiid.designer.core/XXXXXXXXXXXX.INDEX. There is no transformation SQL in it.

      Show
      1. copy the attached test.csv somewhere you like 2. run Import From Flat File Source wizard to create a data source for the test.csv. (Right click the project >Import >File Source (Flat) >>Source and View Model) 3. create vdb and put the models to the vdb. 4. See $WORKSPACE/.metadata/.plugins/org.teiid.designer.core/XXXXXXXXXXXX.INDEX. There is no transformation SQL in it.

      A large transformation SQL of a view model is not exported to INDEX file.

      I have a large transformation SQL > 8192 bytes in my view model. TDesigner fails to convert the xmi to XXXXXXXXXX.INDEX file. There is no transformation SQL in the INDEX file, therefore, deploying my vdb fails and the vdb is inactivated. When you deploy the vdb, you can see the following message in a log file:-

      17:16:11,632 WARN  [org.teiid.PLANNER.RESOLVER] (teiid-async-threads - 2) TEIID31079 View ViewModel.new_table is not defined by a query expression.
      17:16:11,636 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40073 The metadata for the VDB test.1 is loaded, however it is not valid. Check models for errors. Correct the metadata and re-deploy.
      17:16:11,637 INFO  [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID40003 VDB test.1 is set to FAILED
      

            parichar@redhat.com Paul Richardson
            rhn-support-hokuda Hisanobu Okuda
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: