[JBoss JIRA] Updated: (TEIIDDES-767) Staging tables performance appears to be sub-par - should allow for key/index information
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-767?page=com.atlassian.jira.plug... ]
Steven Hawkins updated TEIIDDES-767:
------------------------------------
Summary: Staging tables performance appears to be sub-par - should allow for key/index information (was: Staging tables performance appears to be sub-par)
Designer should allow for pk/index metadata on staging tables. The engine will use this to enhance performance.
> Staging tables performance appears to be sub-par - should allow for key/index information
> -----------------------------------------------------------------------------------------
>
> Key: TEIIDDES-767
> URL: https://issues.jboss.org/browse/TEIIDDES-767
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.0
> Reporter: Steven Hawkins
>
> Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly noticed the performance was fairly even between docs using staging tables and docs not using staging tables. I did further research and found the queries ran faster without staging tables. The email thread is attached (zipped in case the Trakka doesn't like it).
> The Model Project Set is also attached. The VDB's lone binding is defined.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Moved: (TEIIDDES-767) Staging tables performance appears to be sub-par
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-767?page=com.atlassian.jira.plug... ]
Steven Hawkins moved TEIID-123 to TEIIDDES-767:
-----------------------------------------------
Project: Teiid Designer (was: Teiid)
Key: TEIIDDES-767 (was: TEIID-123)
Issue Type: Feature Request (was: Bug)
Affects Version/s: 7.0
(was: 8.x)
Component/s: Modeling
(was: Query Engine)
Fix Version/s: (was: 8.x)
> Staging tables performance appears to be sub-par
> ------------------------------------------------
>
> Key: TEIIDDES-767
> URL: https://issues.jboss.org/browse/TEIIDDES-767
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.0
> Reporter: Steven Hawkins
>
> Defect Tracker #20207: While working on the E2E Staging Tables Test Script, Mark Donnelly noticed the performance was fairly even between docs using staging tables and docs not using staging tables. I did further research and found the queries ran faster without staging tables. The email thread is attached (zipped in case the Trakka doesn't like it).
> The Model Project Set is also attached. The VDB's lone binding is defined.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years
[JBoss JIRA] Created: (TEIIDDES-765) SalesForce importer is not displaying existing profiles in the combo.
by John Doyle (JIRA)
SalesForce importer is not displaying existing profiles in the combo.
---------------------------------------------------------------------
Key: TEIIDDES-765
URL: https://issues.jboss.org/browse/TEIIDDES-765
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1.1, 7.2
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
Fix For: 7.1.1, 7.2
If you have SalesForce connection profiles defined, the importer is not displaying them. This defect is a regression caused by the fix for TEIIDDES-761.
Prior to the fix for 761, the importer used the "Teiid Importer" category of profiles to load the combo and create 'New" profiles. This worked for the combo but not for the "New" button. For new you needed to use a profile ID, not a category ID. 761 changed the importer to use the profile ID instead, but this does not work for the combo.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years