May 2012 - teiid-issues - Jboss List Archives

[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

11 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1280) Add parameters to procedure definition

by Steven Hawkins (JIRA)

Add parameters to procedure definition -------------------------------------- Key: TEIID-1280 URL: https://jira.jboss.org/browse/TEIID-1280 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Critical Fix For: 8.0 Our procedure syntax needs to add parameter definition to be independent of Designer. -- 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

11 years, 6 months

3
4
0 / 0

[JBoss JIRA] (TEIID-2040) Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init>

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2040: ------------------------------------ Summary: Failed Assertion during org.teiid.query.processor.relational.SortUtility.<init> Key: TEIID-2040 URL: https://issues.jboss.org/browse/TEIID-2040 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.7 Reporter: Johnathon Lee Assignee: Steven Hawkins -- 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

11 years, 6 months

2
7
0 / 0

[JBoss JIRA] (TEIID-2014) Add logic to the base ExecutionFactory for handling the getMetadata for non-annotated classes

by Van Halbert (JIRA)

Van Halbert created TEIID-2014: ---------------------------------- Summary: Add logic to the base ExecutionFactory for handling the getMetadata for non-annotated classes Key: TEIID-2014 URL: https://issues.jboss.org/browse/TEIID-2014 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 7.7.1 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.7.1 The base ExecutionFactory needs logic when the getMetadata(..) method is called, to introspect the java classes and build the metadata. -- 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

11 years, 6 months

3
5
0 / 0

[JBoss JIRA] (TEIID-1950) teiid client settings properties overrides don't work with signed jars

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-1950: ------------------------------------- Summary: teiid client settings properties overrides don't work with signed jars Key: TEIID-1950 URL: https://issues.jboss.org/browse/TEIID-1950 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 7.6 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.7.1 With a signed jar modifing a property file in place or using a different version in the classpath results in an exception. It would be best to remove overridable properties files from the client jar. -- 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

11 years, 6 months

2
3
0 / 0

[JBoss JIRA] (TEIID-2029) Allow defining multiple dependencies with "lib" property in the vdb.xml

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2029: ----------------------------------- Summary: Allow defining multiple dependencies with "lib" property in the vdb.xml Key: TEIID-2029 URL: https://issues.jboss.org/browse/TEIID-2029 Project: Teiid Issue Type: Enhancement Components: Server Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.1 Currently "lib" property allows single module dependency, allow to define multiple modules with comma as the delimiter. Also allow the JAR or EAR/WAR based dependencies. -- 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

11 years, 6 months

3
4
0 / 0

[JBoss JIRA] (TEIID-1884) COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets

by Johnathon Lee (Created) (JIRA)

COMMAND Logging incorrectly reporting END USER COMMAND record count in EDS for forward only resultsets ------------------------------------------------------------------------------------------------------ Key: TEIID-1884 URL: https://issues.jboss.org/browse/TEIID-1884 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.6, 7.5, 7.4, 7.3, 7.2, 7.1 Reporter: Johnathon Lee Assignee: Steven Hawkins Running a query [1] that returns 406 rows in sql client, near the end of my log I get this output [2]. [1] select * from CIS_Test.GetListOfLanguageNames [2] 2011-12-28 12:34:34,169 DEBUG [org.teiid.COMMAND_LOG] (Worker0_QueryProcessorQueue26) END USER COMMAND: endTime=2011-12-28 12:34:34.169 requestID=EED0CMZyYmnc.7 txID=null sessionID=EED0CMZyYmnc principal=teiid@teiid-security vdbName=CIStest vdbVersion=1 finalRowCount=0 -- 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

11 years, 6 months

4
7
0 / 0

[JBoss JIRA] Created: (TEIID-1600) Exact numerical literal parsing

by Steven Hawkins (JIRA)

Exact numerical literal parsing ------------------------------- Key: TEIID-1600 URL: https://issues.jboss.org/browse/TEIID-1600 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.0 Teiid diverges from the SQL spec by parsing numerical expressions of the form <integral value>.<integral value> as doubles rather than as an exact numeric type (which for us would be BigDecimal). I believe this was originally done to match Java parsing semantics and potentially to avoid performance overhead of using BigBecimal. However this can lead to a loss of precision that is not expected by ANSI SQL. inexact numeric values entered in scientific notation would not be affected by this change. They would still be parsed as doubles. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

3
5
0 / 0

[JBoss JIRA] (TEIID-1971) Provide delegating Metadata Repository implementation class

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-1971: ----------------------------------- Summary: Provide delegating Metadata Repository implementation class Key: TEIID-1971 URL: https://issues.jboss.org/browse/TEIID-1971 Project: Teiid Issue Type: Task Components: Connector API Affects Versions: 8.0 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.0 The Metadata Repository is interface defined to import metadata from variety of sources. It is useful to provide a base implementation of of delegating metadata repository such that it can be overridden by users to provide their own implementations, on top of already already available methods. -- 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

11 years, 6 months

2
2
0 / 0

[JBoss JIRA] (TEIID-2015) Create implementation to support calling remote Infinispan

by Van Halbert (JIRA)

Van Halbert created TEIID-2015: ---------------------------------- Summary: Create implementation to support calling remote Infinispan Key: TEIID-2015 URL: https://issues.jboss.org/browse/TEIID-2015 Project: Teiid Issue Type: Sub-task Components: Misc. Connectors Affects Versions: 7.7.1 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.7.1 Implement the classes in order to support calling Infinispan remotely. This will include: - an ExecutionFactory to support Infinispan features and building the metadata when getMetadata(..) is called. This will be needed so that the metadata can be imported using Designer to build the source model(s). - implement the query logic needed to take a command and submit it Infinispan -- 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

11 years, 6 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2012