January 2010 - teiid-issues - Jboss List Archives

[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

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

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

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

2
4
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

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

3
13
0 / 0

[JBoss JIRA] Created: (TEIID-922) Teiid Quick Start Example documentation errors

by David Egts (JIRA)

Teiid Quick Start Example documentation errors ---------------------------------------------- Key: TEIID-922 URL: https://jira.jboss.org/jira/browse/TEIID-922 Project: Teiid Issue Type: Bug Components: Documentation Affects Versions: 6.2.0 Environment: Should not matter since this is a documentation issue. Reporter: David Egts Assignee: Steven Hawkins Priority: Minor Over the holiday slowdown, I was able to partially run through the Teiid Quick Start Example [1] to get up to speed on Teiid. Good stuff! [1] http://docs.jboss.org/teiid/6.2/quick-start-guide/en-US/html/index.html I did notice however that the doc has some possibly outdated links and I got stuck part way due to lack of detail when combined with my relative newness to Eclipse. This is what I saw so far... - References to the downloads. *** Artifact names in Chapter 1 [2] don't match the names on the download page [3]. [2] http://docs.jboss.org/teiid/6.2/quick-start-guide/en-US/html/download.html [3] http://www.jboss.org/teiid/downloads.html *** The download links in the doc for Teiid and later for Designer point to broken links [4] which reroute back to the main Teiid page. This leaves the reader to drill down on the Download link as opposed to going directly there [5]. No biggie, but I figure I'd mention it. [4] http://teiid.org/Download.html [5] http://www.jboss.org/teiid/downloads.html - The Teiid family only comes as a zip files, but the doc references tar archives too. Again, no biggie, but I figure I'd mention it. - Section 4.2 [6] says "There is a video at the end of the list that will take you though all the steps involved." I don't see a video there. [6] http://docs.jboss.org/teiid/6.2/quick-start-guide/en-US/html/designer.htm... - At this point, I get to step 3 and I'm stuck due to lack of detail when combined with my relative newness to Eclipse. Any pointers? Possibly the missing video mentioned above would add the needed detail. The "File->New..." guidance was very helpful in steps 1 and 2. Replicating that on the other steps would be a huge help. I did post this to http://lists.jboss.org/pipermail/teiid-users/2010-January/thread.html#66, and Ramesh asked me to submit this JIRA. THANK YOU for putting this together! -- 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

5
6
0 / 0

[JBoss JIRA] Created: (TEIID-838) Runtime discovery of VDBs

by Steve Jacobs (JIRA)

Runtime discovery of VDBs ------------------------- Key: TEIID-838 URL: https://jira.jboss.org/jira/browse/TEIID-838 Project: Teiid Issue Type: Feature Request Components: Server Reporter: Steve Jacobs Assignee: Steven Hawkins Teiid server should be able to discover VDBs at runtime and automatically load them to the extent possible - i.e. if the server is not configured to require entitlements and all connectors are running, the server should load the VDB as a new version and allow queries. -- 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

5
6
0 / 0

[JBoss JIRA] Created: (TEIID-936) Query never returns from processing

by Paul Nittel (JIRA)

Query never returns from processing ----------------------------------- Key: TEIID-936 URL: https://jira.jboss.org/jira/browse/TEIID-936 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.0 Environment: fedora 12, Teiid build 1/19/2010, OpenJDK Server VM (build 14.0-b16, mixed mode) Reporter: Paul Nittel Assignee: Steven Hawkins I'm executing TPCR Query #16. It processes correctly, and very quickly, in Designer, which is using an older Teiid query engine. The current Teiid, running via AdminShell, never returns from this query. Both are using the same VDB. Two tables are involved PART (200,000 rows) and PARTSUPP (800,000 rows). The output will contain 18,314 rows. The transformation query is: SELECT P_BRAND, P_TYPE, P_SIZE, COUNT(DISTINCT PS_SUPPKEY) AS supplier_cnt FROM TPCR.PARTSUPP, TPCR.PART WHERE (P_PARTKEY = PS_PARTKEY) AND (P_BRAND <> 'Brand#45') AND (P_TYPE NOT LIKE 'MEDIUM POLISHED%') AND (P_SIZE IN (49, 14, 23, 45, 19, 3, 36, 9)) AND (PS_SUPPKEY NOT IN (SELECT S_SUPPKEY FROM TPCR.SUPPLIER WHERE S_COMMENT LIKE '%Customer%Complaints%')) GROUP BY P_BRAND, P_TYPE, P_SIZE The query being executed is: select * from vTpcr.Q16 ORDER BY supplier_cnt desc, p_brand, p_type, p_size I have tried to execute shorter version of the transformation query in AdminShell to no avail. This query: SELECT P_BRAND, P_TYPE, P_SIZE FROM TPCR.PARTSUPP, TPCR.PART WHERE (P_PARTKEY = PS_PARTKEY) AND (P_BRAND <> 'Brand#45') AND (P_TYPE NOT LIKE 'MEDIUM POLISHED%'); did not return in a reasonable time. Teiid seems to use a fair percentage of the CPU for a while, then usage drops to ~0.1% -- 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

3
4
0 / 0

[JBoss JIRA] Created: (TEIID-909) PropertiesUtils.resolveNestedProperties(Properties) goes in a loop

by Van Halbert (JIRA)

PropertiesUtils.resolveNestedProperties(Properties) goes in a loop ------------------------------------------------------------------- Key: TEIID-909 URL: https://jira.jboss.org/jira/browse/TEIID-909 Project: Teiid Issue Type: Bug Components: Common Affects Versions: 7.0 Reporter: Van Halbert Assignee: Van Halbert Fix For: 7.0 The resolveNestedProperties logic goes in a loop when the key is also in the value as ${key}. Example of what caused the problem was: key= usedatasources value=${usedatasources} -- 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

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues January 2010