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

Dynamic VDB doesn't contains updateble option

XMLWordPrintable

      1. imrpot project
      2. create vdb
      3. generate dynamic vdb

      I have source model which have a table which has support updatable to 'true' and all its columns have updatable to 'true'.
      I create vdb, deploy and execute insert query. The query is successful but when I create dynamicVDB and deploy, insert query doesn't pass and server shows error: Metadata does not allow updates on the group

      current

       OPTIONS(NAMEINSOURCE '"BOOKS"."AUTHORS"', CARDINALITY '60')
      

      expected:

      OPTIONS(UPDATABLE 'TRUE',NAMEINSOURCE '"BOOKS"."AUTHORS"', CARDINALITY '60')
      

      This influence JDG metadata because when I deploy dynamic vdb with materialization, the server shows an error that status table (and others tables which should be updatable) don't allow updates.

      TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE ((updateStmt || ' AND loadNumber = ') || matcursor.loadNumber) USING loadNumber = (matcursor.loadNumber + 1), vdbName = VARIABLES.vdbName, vdbVersion = VARIABLES.vdbVersion, schemaName = schemaName, viewName = loadMatView.viewName, updated = now(), LoadState = 'LOADING', valid = (matcursor.valid) AND (NOT (invalidate)), cardinality = matcursor.cardinality" with the SQL statement "UPDATE sourceMSQmodel.testJDG.status SET LoadNumber = DVARS.LoadNumber, LoadState = DVARS.LoadState, valid = DVARS.valid, Updated = DVARS.updated, Cardinality = DVARS.cardinality WHERE VDBName = DVARS.vdbName AND VDBVersion = DVARS.vdbVersion AND schemaName = DVARS.schemaName AND Name = DVARS.viewName AND loadNumber = 59" due to: TEIID30492 Metadata does not allow updates on the group: sourceMSQmodel.testJDG.status
      

              Unassigned Unassigned
              mkralik@redhat.com Matej Kralik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: