June 2010 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-996) Administration of the granular entitlements to data elements should be supported using the management console.

by Van Halbert (JIRA)

Administration of the granular entitlements to data elements should be supported using the management console. --------------------------------------------------------------------------------------------------------------- Key: TEIID-996 URL: https://jira.jboss.org/jira/browse/TEIID-996 Project: Teiid Issue Type: Task Components: Jopr Plugin Reporter: Van Halbert Assignee: Steven Hawkins Fix For: 7.1 Administration of the granular entitlements to data elements should be supported using the management console. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-847) Constant conversion issue

by Steven Hawkins (JIRA)

Constant conversion issue ------------------------- Key: TEIID-847 URL: https://jira.jboss.org/jira/browse/TEIID-847 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.2.0 criteria such as convert(BQT1.SmallA.LongNum, bigdecimal) = '22.0' is being treated as false criteria since the resolverutil checks for a narrowing conversion using the equality method (which will not work for bigdecimals in JRE 1.6). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-858) DependentSetCriteria not being replaced

by Steven Hawkins (JIRA)

DependentSetCriteria not being replaced --------------------------------------- Key: TEIID-858 URL: https://jira.jboss.org/jira/browse/TEIID-858 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 6.2.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 6.3 This is a regression from TEIID-308. If the DependentAccessNode is not performing the expansion, then the criteria is not replaced. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIID-897) Create a new autowrap mode to replace pessimistic/optimistic

by Steven Hawkins (JIRA)

Create a new autowrap mode to replace pessimistic/optimistic ------------------------------------------------------------ Key: TEIID-897 URL: https://jira.jboss.org/jira/browse/TEIID-897 Project: Teiid Issue Type: Feature Request Components: Query Engine Affects Versions: 7.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 There are issues with pessimistic/optimistic autowrap modes: 1. optimistic transaction autowrap is no longer needed since all installations of Teiid have a transaction manager available. This mode is really only useful as a development time aid - there is also a case to replace it with a readonly mode to prevent all updates. 2. the detection of when a transaction is needed is based upon the resolved from of a command and not the actual plan/execution. This has led to progressively more pessimistic logic to capture when a transaction is needed (being fully pessimistic we'd have to assume that any procedure with an update count of 1 also needs a transaction since an error can occur during the conversion of output parameters that should cause a rollback). We should either do a better job based upon the plan/execution, or just state simple assumptions (select -no txn, source insert, update, delete, exec w/ update count <=1 -no txn, else txn). 3. the terminology is confusing since it's evocative of locking semantics I therefore propose we change these to txnAutoWrap=AUTO, which would be similar to pessimistic mode and would change the detection strategy to one of the proposals from 2. We should also be explicit that this mode is based upon the assumption that multiple selects do not need to be grouped in the same transaction. However when there is a transaction, then the selects will be performed in the same transaction. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-430) Root access needs enforced for subsystem admin api edits of security properties

by Steven Hawkins (JIRA)

Root access needs enforced for subsystem admin api edits of security properties ------------------------------------------------------------------------------- Key: TEIID-430 URL: https://jira.jboss.org/jira/browse/TEIID-430 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Priority: Minor Fix For: 6.1.0 Using the subsystem admin api (not exposed directly by any client) you can modify the security configuration properties as a product admin instead of root (this is only enforced by the console). We should enforce this on the server side as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-917) xml stream handling is inconsistent

by Steven Hawkins (JIRA)

xml stream handling is inconsistent ----------------------------------- Key: TEIID-917 URL: https://jira.jboss.org/jira/browse/TEIID-917 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Our SQLXMLImpl allows for a variety of source types - such as a streamsource coming from the xml source connector. However if the resulting SQLXML is used by the client (and not immediately consumed by something like XQuery) then the stream can only be read once. Also all of the conversion routines in the XMLTranslator logic (and in the xml document stylesheet application) are based upon full materialization. This may lead to memory problems. In general our SQLXMLImpl should be backed by a string if small and a (temp) file if large. Conversions from DOM and SAX sources would also need to create temp files to protect memory and allow for multiple reads respectively. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-989) Pushdown query ORDER BY is not always ordering results properly on Sql2000

by Warren Gibson (JIRA)

Pushdown query ORDER BY is not always ordering results properly on Sql2000 ---------------------------------------------------------------------------- Key: TEIID-989 URL: https://jira.jboss.org/jira/browse/TEIID-989 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Reporter: Warren Gibson Assignee: Steven Hawkins Pushdown queries with ORDER BY are not always ordering results correctly. The below query is returning query results in the proper order for Simple Capabilities but in the wrong order for Pushdown on sql2000 source. SELECT BQT1.SmallA.IntNum, BQT2.SmallB.StringNum FROM BQT1.SmallA, BQT2.SmallB WHERE BQT1.SmallA.IntNum = BQT2.SmallB.StringNum AND BQT1.SmallA.IntKey >= 5 AND BQT2.SmallB.IntKey >= 5 ORDER BY BQT1.SmallA.StringKey -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (TEIID-916) Initial client socket timeout is too low under load

by Steven Hawkins (JIRA)

Initial client socket timeout is too low under load --------------------------------------------------- Key: TEIID-916 URL: https://jira.jboss.org/jira/browse/TEIID-916 Project: Teiid Issue Type: Quality Risk Components: JDBC Driver Affects Versions: 6.0.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.0 Under stress tests errors are seen with socket connections during the handshake since the timeout is set to 3 seconds by default. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-570) Need new methods to expose Services for Configuring and Monitoring

by Van Halbert (JIRA)

Need new methods to expose Services for Configuring and Monitoring ------------------------------------------------------------------ Key: TEIID-570 URL: https://jira.jboss.org/jira/browse/TEIID-570 Project: Teiid Issue Type: Feature Request Components: AdminApi, Server Affects Versions: 6.1.0 Reporter: Van Halbert Assignee: Van Halbert Need new methods to expose Services for Configuring and Monitoring. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

3
13
0 / 0

[JBoss JIRA] Created: (TEIID-990) Remove the Axis library dependency on the XML Connectors

by Ramesh Reddy (JIRA)

Remove the Axis library dependency on the XML Connectors -------------------------------------------------------- Key: TEIID-990 URL: https://jira.jboss.org/jira/browse/TEIID-990 Project: Teiid Issue Type: Task Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 7.0 Currently XML-Source SOAP connector depends upon Axis 1.3, this needs to be removed and re-written to use JAX-WS and JBossWS-Native. Also, Salesforce connector uses Axis 1.3 to generate the client stub, this needs to be removed and re-generated using JAX-WS specific tools like wsimport. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 6 months

2
2
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues June 2010