[JBoss JIRA] Created: (TEIID-1598) translator scoped result set caching
by Mark Addleman (JIRA)
translator scoped result set caching
------------------------------------
Key: TEIID-1598
URL: https://issues.jboss.org/browse/TEIID-1598
Project: Teiid
Issue Type: Feature Request
Reporter: Mark Addleman
Assignee: Steven Hawkins
Priority: Minor
Something Steven mentioned in Teiid-1589 got me thinking: It would be helpful for individual translators to request that Teiid cache results sets that match the query as presented to the execution factory (after the planner is done rewriting the query based on the translator's capabilities).
I envision a new method on an Execution getCacheTtlMs() where zero or negative indicates that Teiid shouldn't cache the results.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (TEIID-2011) Develope a JPA Translator
by Ramesh Reddy (JIRA)
Ramesh Reddy created TEIID-2011:
-----------------------------------
Summary: Develope a JPA Translator
Key: TEIID-2011
URL: https://issues.jboss.org/browse/TEIID-2011
Project: Teiid
Issue Type: Feature Request
Components: Misc. Connectors
Reporter: Ramesh Reddy
Assignee: Ramesh Reddy
Fix For: 8.1
Provide a JPA based translator in Teiid. The main driving force for this is to support Hibernate OGM, which in turn uses big data stores like infinispan, EhCache as backing stores. Hibernate OGM also looking to expanding to other stores like Cassendra, MongoDB etc.
By providing JPA translator (think reverse hibernate), which provides
- Metadata
- Query API (JPQL)
which makes much easier for Teiid to identify data in big data stores and gives ways to integrate with other kinds of sources, both relational and non-relational. This usecase is limited to users who has defined their data using JPA and would like to use big data stores. Additional benefit of this is to provides full Relational access to a JPA store with JDBC/ODBC and SQL.
if the data in big data store is not in JPA objects, then see https://issues.jboss.org/browse/TEIID-1992
--
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] (TEIID-2094) Projecting node issue
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-2094:
-------------------------------------
Summary: Projecting node issue
Key: TEIID-2094
URL: https://issues.jboss.org/browse/TEIID-2094
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 6.0.0
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Critical
Fix For: 8.1
If a non-pushed source node (inline view) is located over a projected node that needs to perform projection, a join node, or a select node, the resulting construction of the projection indexes will be incorrect or fail - as the input elements will not match the output elements that have been set to the views elements.
--
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