[
https://issues.jboss.org/browse/TEIID-2285?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2285:
----------------------------------
Issue Type: Enhancement (was: Feature Request)
Fix Version/s: Open To Community
Priority: Minor (was: Major)
Loopback is good a performance testing row through-put (which used to comprise a fair
amount of the performance tests). As you and Van point out, it is not ideal for a Teiid
query plan of anything more complicated than a simple query.
There is a balance to be struck through between putting too much effort into this and just
using a low-overhead in-memory database, such as h2.
If anything I would advocate refining loopback into a delegating translator (so that it
can proxy the actual instances to report back the proper capabilities) and also allow it
to have hard coded results - see the test class
org.teiid.jdbc.HardCodededExecutionFactory. For targeted testing with a limited set of
possible queries/results, that would be far less work than developing more logic to
effectively generate a database.
Enhance Loopback Translator to retrieve custom data
---------------------------------------------------
Key: TEIID-2285
URL:
https://issues.jboss.org/browse/TEIID-2285
Project: Teiid
Issue Type: Enhancement
Components: Misc. Connectors
Affects Versions: 8.2
Reporter: Filip Nguyen
Assignee: Filip Nguyen
Priority: Minor
Fix For: Open To Community
Loopback Translator was identified as suitable way of testing Teiid engine performance.
It would be nice if the Translator would mimic database behavior better in some aspects:
* Possibility to define what data will be retrieved in the columns
* Possibility of Unique data in column to mimic database generator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira