[JBoss JIRA] Created: (TEIIDDES-715) Oracle metadata import using Designer takes long time for large schemas
by Ramesh Reddy (JIRA)
Oracle metadata import using Designer takes long time for large schemas
-----------------------------------------------------------------------
Key: TEIIDDES-715
URL: https://jira.jboss.org/browse/TEIIDDES-715
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Reporter: Ramesh Reddy
Importing metadata from Oracle database seems to take longer than any other database, when the underlying the schema is large. This may be because the default settings with Oracle Driver tries to get lot more metadata then needed. Should explore ways to minimize the time to take import.
Teiid in the Dynamic VDB import uses "Table Types" and "schema" name to limit the number of tables it imports, may be we should adopt similar thing in Designer. It is possible that Designer is already doing such settings.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-126) Add a warning for the use of a model supports property
by Steven Hawkins (JIRA)
Add a warning for the use of a model supports property
------------------------------------------------------
Key: TEIIDDES-126
URL: https://jira.jboss.org/jira/browse/TEIIDDES-126
Project: Teiid Designer
Issue Type: Quality Risk
Components: Modeling
Affects Versions: 6.0.0
Reporter: Steven Hawkins
See TEIID-131. Model support properties that are simply overrides for connector binding properties are no longer checked by the Teiid runtime, rather TEIID-205 is used to control specific capabilities through the connector binding without requiring the creation of a custom capabilities class.
Usage of 'Set Criteria Max Size', Supports "Distinct', Supports "Join", Supports "Order By", Supports "Outer Join", and Supports "Where all" should generate a warning stating that the connector binding should be used instead.
--
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
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-417) Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
by Paul Nittel (JIRA)
Metadata from Text File importer requires use of file Browse button even though file can be entered manually - Finish button is enabled
---------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-417
URL: https://jira.jboss.org/jira/browse/TEIIDDES-417
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 6.3
Environment: Iced Tea, Teiid Designer 6.3
Reporter: Paul Nittel
Attachments: IMFTF.jpg
I was writing a SWTBot test to create a view model's tables when I ran into this.
Knowing SWTBot can't handle the File Chooser, I was delighted to see I could enter the text file's path and name directly into the importer dialog. It wasn't until some time later that I realized merely typing in the name does nothing; you MUST enter the name using the File Chooser. (Once that's been done, it appears you can use the drop-down to re-select that file, but you need that first time entry.)
What's really bad/confusing is manually entering the file and target location enables the Finish button. Clicking it appears to work, but no tables were added to the model.
--
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
14 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-683) JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.
by John Doyle (JIRA)
JDBC Importer cannot connect with DB unless the ConnectionProfile has username and password.
--------------------------------------------------------------------------------------------
Key: TEIIDDES-683
URL: https://jira.jboss.org/browse/TEIIDDES-683
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Reporter: John Doyle
Assignee: John Doyle
The UI in the JDBC importer allows a user to provide a password at import time, rather than keep it in the ConnectionProfile, for security purposes. In theory DTP supports this use and has a connect() method that allows a user to pass the username and password. In practice there is a defect in the ConnectionProfiles provided in the DTP enablement project. The username and password are not used.
This means that when a Teiid Designer user selects a ConnectionProfile w/o a password in the JDBC importer and supplies the password in our UI, the connection will fail.
Here's the eclipse bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=328738
Targeted to be fixed in DTP 1.9.
For our purposes the JDBC importer should validate that the profile has a password before attempting to connect, and inform the user that Teiid Designer can only use profiles with full credentials.
--
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, 10 months
[JBoss JIRA] Created: (TEIIDDES-717) Designer whoudl provide option to create datasources during the VDB deploy
by Ramesh Reddy (JIRA)
Designer whoudl provide option to create datasources during the VDB deploy
--------------------------------------------------------------------------
Key: TEIIDDES-717
URL: https://jira.jboss.org/browse/TEIIDDES-717
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Affects Versions: 7.1
Reporter: Ramesh Reddy
Currently when a VDB is deployed, vdb is deployed but process does not check if the required data sources in the server exist or not. Designer should provide an option to the user to select to decide to create data sources or not in the same deploy action. This could be wizard driven if needed to. That way when a VDB is deployed all the required artifacts are also available in the server.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (TEIIDDES-768) Criteria Builder may insert crieria inside object names if user not careful
by Paul Nittel (JIRA)
Criteria Builder may insert crieria inside object names if user not careful
---------------------------------------------------------------------------
Key: TEIIDDES-768
URL: https://issues.jboss.org/browse/TEIIDDES-768
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.1.1
Environment: JBDS 4.0 Beta2
Reporter: Paul Nittel
I start with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PARTS;
END
At this point the Criteria Builder (and Expression Builder) button is disabled. So I click in the SELECT clause to enable the button. Let's say I click between the P and the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR = PartsView.getPartsByColor.colorInRTS;
END
Regardless of where in the SELECT I click, the WHERE clause should be inserted in a syntactically correct location.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (TEIIDDES-710) Add Ability to Create Translator Overrides in Designer
by Ted Jones (JIRA)
Add Ability to Create Translator Overrides in Designer
-------------------------------------------------------
Key: TEIIDDES-710
URL: https://jira.jboss.org/browse/TEIIDDES-710
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 7.1
Reporter: Ted Jones
Assignee: Ted Jones
Need the ability to ad translator overrides for a VDB. Currently overrides have to be manually added to the vdb.xml.
After talking with Barry, the best place for such and editor would be from the Translator field of the models table from within the VDB editor. There is a context menu that allows you to change the translator from that field.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years