[JBoss JIRA] (TEIIDDES-2931) Dynamic VDB doesn't contains updateble option
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2931?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2931:
-----------------------------------
Fix Version/s: 10.0.2
> Dynamic VDB doesn't contains updateble option
> ---------------------------------------------
>
> Key: TEIIDDES-2931
> URL: https://issues.jboss.org/browse/TEIIDDES-2931
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.2
>
> Attachments: updateProject.zip
>
>
> 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
> {code:java}
> OPTIONS(NAMEINSOURCE '"BOOKS"."AUTHORS"', CARDINALITY '60')
> {code}
> expected:
> {code:java}
> OPTIONS(UPDATABLE 'TRUE',NAMEINSOURCE '"BOOKS"."AUTHORS"', CARDINALITY '60')
> {code}
> 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.
> {code:java}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2960) Synchronized button doesn't work correctly
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2960?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2960:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.3 (was: )
> Synchronized button doesn't work correctly
> ------------------------------------------
>
> Key: TEIIDDES-2960
> URL: https://issues.jboss.org/browse/TEIIDDES-2960
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Labels: release_notes, verified_jbdsis-9.0.3
> Attachments: test.mkv
>
>
> When I have VDB and I change something in any model, VDB editor shows that the model is not synchronized. I click on the "Synchronize All" and model looks synchronized. When I close VDB editor and open it again, the model is synchronized. It works but when I change something in the model again and I do previous steps (open VDB editor,synchronize,close VDBeditor and open it again), the model is still not synchronized.
> I noticed that only first time it works properly. So when I change something after that I had already synchronized the vdb, I have to delete VDB and create new because any new changes aren't saved. This is very annoying when I have set some properties and overriding translator in the vdb and I have to set it again.
> I attach the video
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2960) Synchronized button doesn't work correctly
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2960?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2960.
----------------------------------
> Synchronized button doesn't work correctly
> ------------------------------------------
>
> Key: TEIIDDES-2960
> URL: https://issues.jboss.org/browse/TEIIDDES-2960
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Labels: release_notes, verified_jbdsis-9.0.3
> Attachments: test.mkv
>
>
> When I have VDB and I change something in any model, VDB editor shows that the model is not synchronized. I click on the "Synchronize All" and model looks synchronized. When I close VDB editor and open it again, the model is synchronized. It works but when I change something in the model again and I do previous steps (open VDB editor,synchronize,close VDBeditor and open it again), the model is still not synchronized.
> I noticed that only first time it works properly. So when I change something after that I had already synchronized the vdb, I have to delete VDB and create new because any new changes aren't saved. This is very annoying when I have set some properties and overriding translator in the vdb and I have to set it again.
> I attach the video
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2935) Teiid designer doesn't generate materialization staging table correctly
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2935?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2935.
----------------------------------
> Teiid designer doesn't generate materialization staging table correctly
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2935
> URL: https://issues.jboss.org/browse/TEIIDDES-2935
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: project.zip
>
>
> I have generated JDG module and materialization table. When I created dynamic vdb and deploy to server, server shows me warning that:
> {code:java}
> TEIID21005 Registered Class not found for table ST_Book1, check table name matches a registered class
> {code}
> I noticed that staging table doesn't contain primary_table parameter in the options.
> I think that Teiid designer should add this parameter automatically after generated this tables.
> Actual ddl:
> {code:java}
> <![CDATA[
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> ]]>
> {code}
> Expected ddl:
> {code:java}
> <![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/object/2016' AS tns;
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE',"tns:primary_table" 'BookCacheSource.Book')
> ]]>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2935) Teiid designer doesn't generate materialization staging table correctly
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2935?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2935:
-----------------------------------
Labels: verified_jbdsis-9.0.3 (was: )
> Teiid designer doesn't generate materialization staging table correctly
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2935
> URL: https://issues.jboss.org/browse/TEIIDDES-2935
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: project.zip
>
>
> I have generated JDG module and materialization table. When I created dynamic vdb and deploy to server, server shows me warning that:
> {code:java}
> TEIID21005 Registered Class not found for table ST_Book1, check table name matches a registered class
> {code}
> I noticed that staging table doesn't contain primary_table parameter in the options.
> I think that Teiid designer should add this parameter automatically after generated this tables.
> Actual ddl:
> {code:java}
> <![CDATA[
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> ]]>
> {code}
> Expected ddl:
> {code:java}
> <![CDATA[
> SET NAMESPACE 'http://www.teiid.org/translator/object/2016' AS tns;
> CREATE FOREIGN TABLE Book (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE')
> CREATE FOREIGN TABLE ST_Book1 (
> isbn string(255) NOT NULL,
> title string(255),
> publisher integer OPTIONS(FIXED_LENGTH 'TRUE'),
> publishyear integer OPTIONS(FIXED_LENGTH 'TRUE'),
> edition integer OPTIONS(FIXED_LENGTH 'TRUE'),
> type string(255),
> CONSTRAINT PK_ISBN PRIMARY KEY(isbn)
> )OPTIONS(UPDATABLE 'TRUE',"tns:primary_table" 'BookCacheSource.Book')
> ]]>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2812) Add ability to reverse engineer into a Pojo object from a table or view
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2812?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2812.
----------------------------------
[~blafond] Suffix is added to JDG source model and createVDB wizard create overriding translator automatically so I closed this bug. However, user still has to set overriding translator to model [TEIIDDES-2959 | https://issues.jboss.org/browse/TEIIDDES-2959]
> Add ability to reverse engineer into a Pojo object from a table or view
> -----------------------------------------------------------------------
>
> Key: TEIIDDES-2812
> URL: https://issues.jboss.org/browse/TEIIDDES-2812
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling, Usability
> Affects Versions: 9.0.6
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Priority: Blocker
> Labels: release_notes, verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: Infinispan_Materialization.mxd, jdg-module-generated-files.png, materialize-action.png, materialize-wizard-page-1.png, materialize-wizard-page-2.png, materialized-table-property-value.png
>
>
> The scenario is: select table/view, right mouse click select Create Pojo, present dialog, need a file chooser to select location to save output.
> Label of action: Create Pojo (or something to indicates the process)
> Dialog title: Create Pojo from Table [tableName]
> Message: This will create a Pojo class, and packaged in a jar, that is meant to be used when JDG will be used in materialization or accessed as a data source.
> Options:
> - file chooser option to select folder to save pojo jar
> - drop-down: <select option>
> Access JDG in Library Mode
> Access JDG via Hot Rod Client
> - pojo package name (default = org.teiid.pojo)
> - pojo jar name (default = pojo.jar)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2925:
-----------------------------------
Labels: verified_jbdsis-9.0.3 (was: )
> Designer doesn't change java class name in the generated POJO module
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2925
> URL: https://issues.jboss.org/browse/TEIIDDES-2925
> Project: Teiid Designer
> Issue Type: Bug
> Components: Build
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: create-pojo-warning.png, screenshot1.png, screenshot2.png
>
>
> I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2925) Designer doesn't change java class name in the generated POJO module
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2925?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2925.
----------------------------------
> Designer doesn't change java class name in the generated POJO module
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2925
> URL: https://issues.jboss.org/browse/TEIIDDES-2925
> Project: Teiid Designer
> Issue Type: Bug
> Components: Build
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Assignee: Barry LaFond
> Labels: verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
> Attachments: create-pojo-warning.png, screenshot1.png, screenshot2.png
>
>
> I have a table (for example PersonMatView) and I want to create materialization. I set 'create POJO' and set java class name to Person (screenshot1). After that in the generated JDG module is Person.jar but in the jar, the class has name same like the table (Personmatview.class). (screenshot2). Is it required to have class name same as materialized table?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2970) Set default MatView Extension Properties for JDG materialization
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2970?page=com.atlassian.jira.plu... ]
Matej Kralik closed TEIIDDES-2970.
----------------------------------
> Set default MatView Extension Properties for JDG materialization
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2970
> URL: https://issues.jboss.org/browse/TEIIDDES-2970
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
>
> When a view is being materialized for JDG, set the following extension properties:
> teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT -
> {code}
> execute {jdgsourcemodelname}.native(''swap cache names'');
> {code}
> teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT -
> {code}
> execute {jdgsourcemodelname}.native(''truncate cache'');
> {code}
> teiid_rel:MATERIALIZED_STAGE_TABLE -
> {code}
> {jdgsourcemodelname}.{stagingTable}
> {code}
> where {jdgsourcemodelname} as the new JDG Source Model that is created.
> note: do not add tic's around these, like 'execute......),'
> but do add the double tic's inside the native call
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2970) Set default MatView Extension Properties for JDG materialization
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2970?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2970:
-----------------------------------
Labels: release_notes verified_jbdsis-9.0.3 (was: )
> Set default MatView Extension Properties for JDG materialization
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2970
> URL: https://issues.jboss.org/browse/TEIIDDES-2970
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling
> Affects Versions: 10.0.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Labels: release_notes, verified_jbdsis-9.0.3
> Fix For: 10.0.2
>
>
> When a view is being materialized for JDG, set the following extension properties:
> teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT -
> {code}
> execute {jdgsourcemodelname}.native(''swap cache names'');
> {code}
> teiid_rel:MATVIEW_BEFORE_LOAD_SCRIPT -
> {code}
> execute {jdgsourcemodelname}.native(''truncate cache'');
> {code}
> teiid_rel:MATERIALIZED_STAGE_TABLE -
> {code}
> {jdgsourcemodelname}.{stagingTable}
> {code}
> where {jdgsourcemodelname} as the new JDG Source Model that is created.
> note: do not add tic's around these, like 'execute......),'
> but do add the double tic's inside the native call
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months