[JBoss JIRA] Created: (TEIIDDES-452) Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function.
by Van Halbert (JIRA)
Fundamental rework of existing MetaMatrix materialization will become mainly a Designer function.
-------------------------------------------------------------------------------------------------
Key: TEIIDDES-452
URL: https://jira.jboss.org/browse/TEIIDDES-452
Project: Teiid Designer
Issue Type: Feature Request
Reporter: Van Halbert
Fundamental rework of existing MetaMatrix materialized views functionality to make mat views first class objects in the system.
The changes for this feature include:
1.Moving away from the automagic creation of materialized view source/physical model and ddl scripts upon VDB deployment
2.Making mat view source/physical models explictly modeled objects in Designer tooling.
3.Support external scripts to pull data from live sources and populate mat views.
4.Support virtual procedure logic to pull data from live sources and populate mat views. This will required DDL execution capabilities such that virtual procedures can perform the swap of staged data.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months
[JBoss JIRA] Created: (TEIIDDES-490) Validation of transformation SQL with sub-select and alias incorrectly adds model name to alias.column name
by Paul Nittel (JIRA)
Validation of transformation SQL with sub-select and alias incorrectly adds model name to alias.column name
-----------------------------------------------------------------------------------------------------------
Key: TEIIDDES-490
URL: https://jira.jboss.org/browse/TEIIDDES-490
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.0
Environment: Fedora 12, OpenJDK, Designer 6/28
Reporter: Paul Nittel
This is from teh TPCR metadata text import test. A series of transformations is built for query testing. When I ran it, several transformations were affected similarly. The Hawkman looked at it and believes the issue lies within the Designer. Here's a simplified version of the SQL:
SELECT supp_nation, cust_nation
FROM (SELECT n1.N_NAME AS supp_nation, n2.N_NAME AS cust_nation FROM TPCR.SUPPLIER, TPCR.NATION AS n1, TPCR.NATION AS n2
WHERE (S_NATIONKEY = n1.N_NATIONKEY) ) AS shipping
Upon validation, it changes to:
SELECT
SHIPPING.supp_nation, SHIPPING.cust_nation
FROM
(SELECT n1.TPCR.NATION.N_NAME AS supp_nation, n2.TPCR.NATION.N_NAME AS cust_nation FROM TPCR.SUPPLIER, TPCR.NATION AS n1, TPCR.NATION AS n2 WHERE TPCR.SUPPLIER.S_NATIONKEY = n1.TPCR.NATION.N_NATIONKEY) AS shipping
The error is:
The query is parsable but not resolvable.
Resolver Error: Symbol n1.TPCR.NATION.N_NATIONKEY is specified with an unknown group context
The element in question should be referred to as: n1.N_NATIONKEY. (I'll attach the model project set.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 4 months