March 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2357) max buffer space is not honored

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2357?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2357. --------------------------------- > max buffer space is not honored > ------------------------------- > > Key: TEIID-2357 > URL: https://issues.jboss.org/browse/TEIID-2357 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.3, 7.7.6 > > > The introduction of the ensureLength logic in the split file handling effectively by-passes the check for disk utilization. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2285) Enhance Loopback Translator to retrieve custom data

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2285?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2285. --------------------------------- > 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: 8.3 > > > 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2294) Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2294?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2294. --------------------------------- > Allow to use alias name to lookup the certificate from keysore at jdbc ssl transport layer > ------------------------------------------------------------------------------------------ > > Key: TEIID-2294 > URL: https://issues.jboss.org/browse/TEIID-2294 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Labels: CR2 > Fix For: 8.2 > > > From the teiid 8.1 schema (jboss-teiid.xsd) under docs, there is no "alias" attribute defined for jdbc transport layer. Here is the question: in the case of there are multiple certificates defined at keysore, what certificate jdbc ssl will use? How to specify correct one to use? > > Here is the sample teiid jdbc configuration used: > <transport name="jdbc" socket-binding="teiid-jdbc"> > <authentication security-domain="mysecuritydomain"/> > <ssl mode="enabled" keymanagement-algorithm="SunX509"> > <keystore name="/opt/test.keystore" password="password"/> > </ssl> > </transport> -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2254) Avoid name conflicts with source_name column

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2254?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2254. --------------------------------- > Avoid name conflicts with source_name column > -------------------------------------------- > > Key: TEIID-2254 > URL: https://issues.jboss.org/browse/TEIID-2254 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > Allow the multi-source column name to be configurable, or something more teiid specific, or use extension metadata, etc. to avoid name conflicts with source columns named source_name. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2154) Infrastructure tasks

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2154?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2154. --------------------------------- > Infrastructure tasks > -------------------- > > Key: TEIID-2154 > URL: https://issues.jboss.org/browse/TEIID-2154 > Project: Teiid > Issue Type: Task > Reporter: Steven Hawkins > Assignee: Ramesh Reddy > Fix For: 8.2 > > > We should begin the switch to a git repository and convert to jboss downloads to remove the need of sf.net hosting. > With the downloads copied over, we should be able to use http://www.jboss.org/help/projectpageguide/paragraphguide/directoryListing > To mimic sf downloads. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1992) Create Connector/Translator to support Infinispan as a data source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1992?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1992. --------------------------------- > Create Connector/Translator to support Infinispan as a data source > ------------------------------------------------------------------ > > Key: TEIID-1992 > URL: https://issues.jboss.org/browse/TEIID-1992 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.2 > > Attachments: ispn-integration.zip > > > Create a Connector/Translator in order for Teiid to support Infinispan as a read-only data source on its initial release. Read Only because if someone is building an object cache, the primary means for updating the cache would not be thru relational means. However, if someone is wanting to add an object cache as a disparate data source for data integration for exposing the content, then this connector/translator will enable that. > A goal here is to build an object translator framework that can easily plug in other object cache sources. Example, add support for Coherence. There was a Coherence connector/translator already created in the sandbox, for which, it will provide direction for the object translator. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2315) Multi-source metadata wrapper needs to distinguish between physical/virtual

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2315?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2315. --------------------------------- > Multi-source metadata wrapper needs to distinguish between physical/virtual > --------------------------------------------------------------------------- > > Key: TEIID-2315 > URL: https://issues.jboss.org/browse/TEIID-2315 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 8.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3 > > > With TEIID-2136 it was allowable to mix virtual entries on a physical model. The multi-source metadata wrapper is not aware of that distinction and will put a pseudo column on even the virtual entries. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2319) Default socket encryption for JDBC transport using mode=login is not being set in configuration file

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2319?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2319. --------------------------------- > Default socket encryption for JDBC transport using mode=login is not being set in configuration file > ---------------------------------------------------------------------------------------------------- > > Key: TEIID-2319 > URL: https://issues.jboss.org/browse/TEIID-2319 > Project: Teiid > Issue Type: Bug > Components: Build/Kits > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Critical > > Referencing TEIID-2108, the login traffic should be encrypted by default. The standalone-teiid-xml does not specify <ssl mode="login" />, nor does the teiid-domain-mode-install.cli show to be adding this setting. -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2273) org.teiid.query.sql.lang.SubqueryFromClause does not quote keywords in the alias

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2273?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2273. --------------------------------- > org.teiid.query.sql.lang.SubqueryFromClause does not quote keywords in the alias > -------------------------------------------------------------------------------- > > Key: TEIID-2273 > URL: https://issues.jboss.org/browse/TEIID-2273 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Mark Addleman > Assignee: Steven Hawkins > Fix For: 8.2 > > > new SubqueryFromClause("user", QueryParser.getQueryParser() .parseCommand("select 1")).toString() > yields > (SELECT 1) AS user > it should be > (SELECT 1) AS "user" > Briefly looking at the code, I think the problem is in org.teiid.query.sql.visitor.SQLStringVisitor.escapeSinglePart(String).escape. > Shouldn't it check SQLStringVisitor.isReservedWord(String)? -- 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

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2085) Additional feature to TEIID-1726

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2085?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2085. --------------------------------- > Additional feature to TEIID-1726 > -------------------------------- > > Key: TEIID-2085 > URL: https://issues.jboss.org/browse/TEIID-2085 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.2 > > > Specifying the aliases in the hints added in https://issues.jboss.org/browse/TEIID-1726 do not work with even the full table name (fdm.wh_gl_daily_balances_f). However, if you were to specify g_0 and g_1 as the aliases for the tables, the hints take effect. The teiid engine has rewritten the query with its own internal aliases and the only way to find out what has been specified is to actually look at the source system sql send to Oracle. > Can we specify the table aliases of the main query in the source > hints rather than looking at what Teiid engine has rewritten to? It > is quite confusing for developers to use the source hints feature > and if the developer does not have access to the Oracle database > they wont be able to tell what has been used in the source query to > reflect the aliases in the source hints. > -- 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

11 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues March 2013