March 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2393) Insert columns should be displayed unqualified

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2393?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2393. --------------------------------- > Insert columns should be displayed unqualified > ---------------------------------------------- > > Key: TEIID-2393 > URL: https://issues.jboss.org/browse/TEIID-2393 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 7.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Minor > Fix For: 8.3 > > > For backwards compatibility we allow the parser to parse qualified insert columns, but we've also allowed the string logic to display them as qualified, which is unnecessary. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1674) Need documentation created for JON EDS/teiid plugin

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1674?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1674. --------------------------------- > Need documentation created for JON EDS/teiid plugin > --------------------------------------------------- > > Key: TEIID-1674 > URL: https://issues.jboss.org/browse/TEIID-1674 > Project: Teiid > Issue Type: Bug > Components: Documentation > Affects Versions: 7.4.1 > Reporter: Marc Shirley > Assignee: Ted Jones > > Need documentation for JON EDS/Teiid plugin describing available connection properties, configuration properties, metrics, operations, etc. for all resource types that the plugin monitors. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2205) Temp table and procedure block transactions issue

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2205?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2205. --------------------------------- > Temp table and procedure block transactions issue > ------------------------------------------------- > > Key: TEIID-2205 > URL: https://issues.jboss.org/browse/TEIID-2205 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.6 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.2, 7.7.5 > > > The Request class is not correctly setting the transactioncontext on the commandcontext, so downstream transaction logic in temp tables and procedure blocks will not work properly. > Block/temp table work will fail to isolate correctly and not rollback. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2371) Provide a callback when there are no results for a query incase of asynchronous queries

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2371?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2371. --------------------------------- > Provide a callback when there are no results for a query incase of asynchronous queries > --------------------------------------------------------------------------------------- > > Key: TEIID-2371 > URL: https://issues.jboss.org/browse/TEIID-2371 > Project: Teiid > Issue Type: Feature Request > Reporter: Vineela Gampa > Assignee: Steven Hawkins > Attachments: EmptyResultSetAsyncTest.java, ExecuteAsyncContinously.java > > > When a query doesn,t return results , please provide a callback method indicating end of results. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1757) Add Support for OData Data Sources

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1757?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1757. --------------------------------- > Add Support for OData Data Sources > ---------------------------------- > > Key: TEIID-1757 > URL: https://issues.jboss.org/browse/TEIID-1757 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Reporter: Ted Jones > Assignee: Ramesh Reddy > Labels: Beta2 > Fix For: 8.3 > > > OData data sources, like SAP Gateway, should be consumable by Teiid. I suggest either a new translator or extending the existing web service translator to enable the OData protocol. A new translator would be cleaner, but since OData uses REST, it may not make sense to to have another 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2409) To add execution id into data src command_log

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2409?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2409. --------------------------------- > To add execution id into data src command_log > --------------------------------------------- > > Key: TEIID-2409 > URL: https://issues.jboss.org/browse/TEIID-2409 > Project: Teiid > Issue Type: Enhancement > Affects Versions: 8.2 > Reporter: Jack Ma > Assignee: Ramesh Reddy > Priority: Trivial > Labels: CR1 > Fix For: 8.3 > > > When we try to analyze the command_log, for some user query, it push multiple data source queries to same data source, in this case, both request id and source command id are same, so it is impossible to pair those data source queries from the command_log (please see discussion: https://community.jboss.org/message/799183#799183). Adding the execution id into the data source command_log should make following combination key unique (request id + source command id + execution id) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2395) ReusableExecutions are created everytime after DataNotAvailable is thrown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2395?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2395. --------------------------------- > ReusableExecutions are created everytime after DataNotAvailable is thrown > ------------------------------------------------------------------------- > > Key: TEIID-2395 > URL: https://issues.jboss.org/browse/TEIID-2395 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.1 > Reporter: Sanjeev Gour > Assignee: Steven Hawkins > Attachments: Testcase.zip > > > We did a test with a simple ReusableExecution and found that new executions are being created every time after DataNotAvailableExecption is thrown. Here is the life cycle after the recent patch for issue https://issues.jboss.org/browse/TEIID-2322 was applied- > TimerExecution.TimerExecution() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:41:03.421 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.TimerExecution() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:41:03.556 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.TimerExecution() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:41:03.661 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.TimerExecution() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:41:03.766 > TimerExecution.reset() > TimerExecution.execute() WAIT > The same test when run against the jar before the fix was applied is this- > TimerExecution.TimerExecution() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:49:01.998 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.reset() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:49:02.123 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.reset() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:49:02.228 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.reset() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:49:02.333 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.reset() > TimerExecution.execute() RESULT > TimerExecution.close() > On Row 2013-02-15 17:49:02.438 > TimerExecution.reset() > TimerExecution.execute() WAIT > TimerExecution.reset() > The testcase is attached. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2160) data type for XMLTable for ordinality column is incorrect

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2160?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2160. --------------------------------- > data type for XMLTable for ordinality column is incorrect > --------------------------------------------------------- > > Key: TEIID-2160 > URL: https://issues.jboss.org/browse/TEIID-2160 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4.4, 8.2 > > > The XMLTable XMLColumn for ordinality constructor is hard-coding a type of STRING, rather than INTEGER. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2312) Allow resource adaptor to support "security-domain"

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2312?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2312. --------------------------------- > Allow resource adaptor to support "security-domain" > --------------------------------------------------- > > Key: TEIID-2312 > URL: https://issues.jboss.org/browse/TEIID-2312 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 8.1 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.3 > > > Currently > * LDAP > * Salesforce > * Google > connectors require user-id/password for making connections with underlying systems, but I do not think they support defining the "security-domain" so that the logged-in user's credentials can be passed through to sources. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2410) issues with output buffer blocking

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2410?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2410. --------------------------------- > issues with output buffer blocking > ---------------------------------- > > Key: TEIID-2410 > URL: https://issues.jboss.org/browse/TEIID-2410 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.3, 7.7.6 > > > when a local connection (regardless of using the calling thread) blocks on the output buffer (which cannot happen with forward only and using the calling thread, but due to another issue can occur with a scroll insensitive result) no corresponding process thread is awakened to process pending work. > Output blocking should also be disabled for non-forward only results. This was disabled at some point by a refactoring to reuse the output buffer from the plan. -- 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, 9 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