[JBoss JIRA] (TEIIDDES-2986) Staging table in the JDG source model has wrong property
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2986?page=com.atlassian.jira.plu... ]
Matej Kralik reassigned TEIIDDES-2986:
--------------------------------------
Assignee: Matej Kralik
> Staging table in the JDG source model has wrong property
> --------------------------------------------------------
>
> Key: TEIIDDES-2986
> URL: https://issues.jboss.org/browse/TEIIDDES-2986
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Assignee: Matej Kralik
> Priority: Critical
> Attachments: JDGproject.zip
>
>
> Primary table property is set wrongly when JDG class name have another name as view model.
> I have a project with JDG materialization. When I was setting materialization for view table (viewBooks) I set class name for POJO to 'Book' (from viewBooks). However, generated staging table in the JDG source model have infinispan:Primary Table properties set to BookJDGSource.viewBooks but correctly is BookJDGSource.Book. I think that designer set this property according to name of view model which will be materialized (viewBooks) but it should according to materialized table (Book) in the JDG source model
> Actual property:
> {code:java}
> viewBooksJDGSource.viewBooks
> {code}
> Correctly property:
> {code:java}
> viewBooksJDGSource.Book
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2986) Staging table in the JDG source model has wrong property
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2986?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2986:
-----------------------------------
Priority: Critical (was: Major)
> Staging table in the JDG source model has wrong property
> --------------------------------------------------------
>
> Key: TEIIDDES-2986
> URL: https://issues.jboss.org/browse/TEIIDDES-2986
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Priority: Critical
> Attachments: JDGproject.zip
>
>
> Primary table property is set wrongly when JDG class name have another name as view model.
> I have a project with JDG materialization. When I was setting materialization for view table (viewBooks) I set class name for POJO to 'Book' (from viewBooks). However, generated staging table in the JDG source model have infinispan:Primary Table properties set to BookJDGSource.viewBooks but correctly is BookJDGSource.Book. I think that designer set this property according to name of view model which will be materialized (viewBooks) but it should according to materialized table (Book) in the JDG source model
> Actual property:
> {code:java}
> viewBooksJDGSource.viewBooks
> {code}
> Correctly property:
> {code:java}
> viewBooksJDGSource.Book
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2986) Staging table in the JDG source model has wrong property
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2986?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2986:
-----------------------------------
Summary: Staging table in the JDG source model has wrong property (was: Staging table in the JDG source model have set wrong properties)
> Staging table in the JDG source model has wrong property
> --------------------------------------------------------
>
> Key: TEIIDDES-2986
> URL: https://issues.jboss.org/browse/TEIIDDES-2986
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Reporter: Matej Kralik
> Attachments: JDGproject.zip
>
>
> Primary table property is set wrongly when JDG class name have another name as view model.
> I have a project with JDG materialization. When I was setting materialization for view table (viewBooks) I set class name for POJO to 'Book' (from viewBooks). However, generated staging table in the JDG source model have infinispan:Primary Table properties set to BookJDGSource.viewBooks but correctly is BookJDGSource.Book. I think that designer set this property according to name of view model which will be materialized (viewBooks) but it should according to materialized table (Book) in the JDG source model
> Actual property:
> {code:java}
> viewBooksJDGSource.viewBooks
> {code}
> Correctly property:
> {code:java}
> viewBooksJDGSource.Book
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2986) Staging table in the JDG source model have set wrong properties
by Matej Kralik (JIRA)
Matej Kralik created TEIIDDES-2986:
--------------------------------------
Summary: Staging table in the JDG source model have set wrong properties
Key: TEIIDDES-2986
URL: https://issues.jboss.org/browse/TEIIDDES-2986
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 10.0.2
Reporter: Matej Kralik
Attachments: JDGproject.zip
Primary table property is set wrongly when JDG class name have another name as view model.
I have a project with JDG materialization. When I was setting materialization for view table (viewBooks) I set class name for POJO to 'Book' (from viewBooks). However, generated staging table in the JDG source model have infinispan:Primary Table properties set to BookJDGSource.viewBooks but correctly is BookJDGSource.Book. I think that designer set this property according to name of view model which will be materialized (viewBooks) but it should according to materialized table (Book) in the JDG source model
Actual property:
{code:java}
viewBooksJDGSource.viewBooks
{code}
Correctly property:
{code:java}
viewBooksJDGSource.Book
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2953) Static VDB with JDG materialization has a warning after deploy
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2953?page=com.atlassian.jira.plu... ]
Matej Kralik updated TEIIDDES-2953:
-----------------------------------
Workaround Description: Create dynamic VDB (-vdb.xml) and deploy it.
> Static VDB with JDG materialization has a warning after deploy
> --------------------------------------------------------------
>
> Key: TEIIDDES-2953
> URL: https://issues.jboss.org/browse/TEIIDDES-2953
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Priority: Critical
> Fix For: 10.0.3
>
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. When I want to deploy static VDB, server shows me error that:
> {code:java}
> 15:47:10,347 WARN [org.teiid.MATVIEWS] (Worker1_QueryProcessorQueue9) org.teiid.jdbc.TeiidSQLException: TEIID30168 Couldn't execute the dynamic SQL command "EXECUTE IMMEDIATE array_get(strings, index)" with the SQL statement "execute BookCacheSource.native('truncate cache')" due to: TEIID30357 BookCacheSource.native does not exist.
> {code}
> But when I deploy dynamic VDB, which is generated from that staticVDB, server doesn't shows any errors and materialization works fine.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2954) Dynamic VDB doesn't contains apostrophe around procedure
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2954?page=com.atlassian.jira.plu... ]
Van Halbert commented on TEIIDDES-2954:
---------------------------------------
This maybe less of an issue now that the materialize wizard will set the extension property.
> Dynamic VDB doesn't contains apostrophe around procedure
> --------------------------------------------------------
>
> Key: TEIIDDES-2954
> URL: https://issues.jboss.org/browse/TEIIDDES-2954
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 10.0.2
> Environment: Fedora 24
> Reporter: Matej Kralik
> Attachments: completeJDGproject2.zip
>
>
> I have a project with JDG materialization. I have set
> After load script to: execute BookCacheSource.native('swap cache names');
> and
> Before load script to: execute BookCacheSource.native('truncate cache');
> When I generated Dynamic VDB and I want to deploy it, server shows me error that:
> {code:java}
> org.teiid.api.exception.query.QueryParserException: TEIID31100 Parsing error: Encountered ", \"teiid_rel:MATVIEW_AFTER_LOAD_SCRIPT\" 'execute BookCacheSource.native('[*]swap[*] cache names" at line 10, column 188.
> Was expecting: "," | ")"
> {code}
> When I added another apostrophe to procedures in the DDL,
> execute BookCacheSource.native(''truncate cache'');
> execute BookCacheSource.native(''swap cache names'');
> deploy was successful.
> I think that DDL parser should add it automatically.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (TEIIDDES-2810) Import/Export Dynamic VDB utility doesn't transfer model descriptions
by Matej Kralik (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2810?page=com.atlassian.jira.plu... ]
Matej Kralik reopened TEIIDDES-2810:
------------------------------------
Exported VDB (dynamic vdb -vdb.xml) contains all descriptions and when I generated models from dynamic vdb, the descriptions were set correctly.
However, when I change the description in any models, save and synchronized VDB, in the VDB is still the old description.
Step to reproduce:
# set description on model ( 'description 1' )
# create VDB (in the VDB editor the descirption was set on model)
# change description ( to 'description 2' and save model)
# synchronize model in the VDB editor (description is still set to 'description 1')
> Import/Export Dynamic VDB utility doesn't transfer model descriptions
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-2810
> URL: https://issues.jboss.org/browse/TEIIDDES-2810
> Project: Teiid Designer
> Issue Type: Bug
> Components: Dynamic VDBs
> Affects Versions: 9.2
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 10.0, 9.0.7, 10.0.2
>
> Attachments: DynamicVdb.patch
>
>
> import a dynamic vdb in Teid designer, the vdb and related models are generated, however, the descriptions are not taken into account properly. We expect to see the description in the Teiid designer.
> Same goes when we export a Teiid vdb to a vdb xml: the descriptions are not generated as xml elements.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months