[JBoss JIRA] (TEIIDDES-1209) Upgrade to use Teiid 8.0 Admin API
by Ramesh Reddy (Created) (JIRA)
Upgrade to use Teiid 8.0 Admin API
----------------------------------
Key: TEIIDDES-1209
URL: https://issues.jboss.org/browse/TEIIDDES-1209
Project: Teiid Designer
Issue Type: Task
Components: VDB & Execution
Reporter: Ramesh Reddy
Priority: Blocker
Fix For: 8.0
Teiid 8.0 has more or less has the same Admin API as it's 7.x releases. However the Admin connection ownership no longer held with the Teiid. i.e Teiid does not control which port the Admin connection nor the security that goes along, these are now core features from AS itself. However, usage for the purposes of the Teiid Designer is not changed.
Teiid Designer needs to be upgraded to use the 8.0 API and validate all the operations it provides.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (TEIIDDES-216) Designer removes parentheses around criteria in ansi join when using compound ON
by Marc Shirley (JIRA)
Designer removes parentheses around criteria in ansi join when using compound ON
--------------------------------------------------------------------------------
Key: TEIIDDES-216
URL: https://jira.jboss.org/jira/browse/TEIIDDES-216
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 6.1.0
Reporter: Marc Shirley
In Designer, when validating a transformation that has compound criteria in an ansi join statement's ON, the parentheses are removed and the order of operations is modified as a result. This does not appear to occur when using the same parentheses structure in WHERE criteria.
Before validation:
SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON (a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL OR a.INTNUM = 11)
After validation:
SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON a.INTKEY = b.INTKEY AND (a.INTNUM IS NULL) OR (a.INTNUM = 11)
After validating a second time:
SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON ((a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL)) OR (a.INTNUM = 11)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIIDDES-1408) Fix Teiid Designer's Unit Tests
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1408:
--------------------------------------
Summary: Fix Teiid Designer's Unit Tests
Key: TEIIDDES-1408
URL: https://issues.jboss.org/browse/TEIIDDES-1408
Project: Teiid Designer
Issue Type: Task
Components: Testing
Reporter: Barry LaFond
Priority: Critical
Fix For: 8.0
Teiid Designer's Unit test framework has not been completed converted to a full set of working tests.
There are a number of test plugins that are NOT part of the nightly build.
There are a number of tests that are even failing in the IDE
Some of our test plugins use PowerMock and/or Mockito. Need to decide if we continue with these or replace them.
Converting test-related JIRAs to sub-tasks
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1207) Merge the relational and function metamodels
by Steven Hawkins (Created) (JIRA)
Merge the relational and function metamodels
--------------------------------------------
Key: TEIIDDES-1207
URL: https://issues.jboss.org/browse/TEIIDDES-1207
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 8.0
Reporter: Steven Hawkins
Having the function and relational models is no longer necessary. We can add the needed function metadata (including TEIIDDES-152 vararg support, null-on-null, etc.) through either extension properties or a metamodel change. This is in the vain of PostgreSQL which uses the create function syntax to add what would be procedures in other dbmses. Virtual functions (procedures marked as functions in a view layer) could also still specify transformation sql if pushdown is not required - rather than forcing the use of a java class.
We could deprecate the old function model support of the Teiid side then.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (TEIIDDES-1403) Add a vdb reuse feature
by Steven Hawkins (JIRA)
Steven Hawkins created TEIIDDES-1403:
----------------------------------------
Summary: Add a vdb reuse feature
Key: TEIIDDES-1403
URL: https://issues.jboss.org/browse/TEIIDDES-1403
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Affects Versions: 7.0
Reporter: Steven Hawkins
See https://issues.jboss.org/browse/TEIID-1366, which not only replaces mergeVDB functionality, but provides a declarative way for vdbs to be reused at runtime. Designer will need to provide a representation of the reuse feature that includes:
- Optionally an artifact that represents a vdb to import, but that only contains the consumable metadata - not the transformations.
- A way to manage those imported artifacts in the context of a workspace
- A way to edit the imports in the vdb.xml to specify the name/version of what's expected at runtime
- preview would be broken unless a deployed version the
An expected flow should be available from GSS customer requests and at a high-level could be described as:
Team 1 develops a vdb and exports the "reuse vdb" without transformation metadata for use by Team 2
or Team 1 develops a vdb and provides it directly to Team 2
Team 2 develops a new vdb using the reuse vdb - no access is needed to the original vdb
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 3 months