[JBoss JIRA] (TEIIDDES-1444) 'Always open editor without prompting' dialog box inconsistency
by B Long (JIRA)
B Long created TEIIDDES-1444:
--------------------------------
Summary: 'Always open editor without prompting' dialog box inconsistency
Key: TEIIDDES-1444
URL: https://issues.jboss.org/browse/TEIIDDES-1444
Project: Teiid Designer
Issue Type: Bug
Components: Views
Affects Versions: 7.7.1
Environment: Fedora 16; JBDS Version: 5.0.0.GA Build id: v20120615-1714-H213-GA; Teiid 7.7.1.v20120619-2152-H6-CR1-SOA
Reporter: B Long
Priority: Minor
When a user attempts to modify a value from Properties View, dialog box "You must open this model in an editor tab before you can modify the property value. Do you want to open the editor?" does not present checkbox option "Always open editor without prompting" as expected.
The dialog box seems to present different behavior depending on whether the user is viewing properties for an .xmi model or a table. The issue presents itself when the user is viewing properties for an .xmi model.
--
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
[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, 4 months
[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, 4 months
[JBoss JIRA] (TEIIDDES-1461) Elapsed Time in the JBoss developer studio shows incorrect timestamps
by Hisanobu Okuda (JIRA)
Hisanobu Okuda created TEIIDDES-1461:
----------------------------------------
Summary: Elapsed Time in the JBoss developer studio shows incorrect timestamps
Key: TEIIDDES-1461
URL: https://issues.jboss.org/browse/TEIIDDES-1461
Project: Teiid Designer
Issue Type: Bug
Components: Data Preview
Affects Versions: 7.4.2
Environment: JBDS 4.1.2
Reporter: Hisanobu Okuda
When you run the query in the JBoss developer studio, it is NOT showing correct elapsed timestamp.
For example, I know that it is taking more than 55 seconds for the below query when I run in the SQL Scrapbook window in the designer against VDB but it is showing as 0 hr, 0 min, 0 sec, 0 ms as shown below.
select * from "Salesforce_Source"."salesforce"."RecordType"
Elapsed Time: 0 hr, 0 min, 0 sec, 0 ms.
--
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, 4 months
[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, 4 months