August 2012 - teiid-issues - Jboss List Archives

[JBoss JIRA] Created: (TEIID-1739) VDB deployment fails if metadata index file has been removed due to NPE during Index.initialize

by Larry O'Leary (JIRA)

VDB deployment fails if metadata index file has been removed due to NPE during Index.initialize ----------------------------------------------------------------------------------------------- Key: TEIID-1739 URL: https://issues.jboss.org/browse/TEIID-1739 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 7.5 Reporter: Larry O'Leary Assignee: Steven Hawkins VDB couldn't be deployed, so customer restarted SOA-P server and the server.log shows: DEPLOYMENTS MISSING DEPENDENCIES: Deployment "VDBDeployer" is missing the following dependencies: Dependency "SystemVDBDeployer" (should be in state "Create", but is actually in state "**ERROR**") DEPLOYMENTS IN ERROR: Deployment "SystemVDBDeployer" is in error due to the following reason(s): java.lang.NullPointerException, **ERROR** ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] (main) Error installing to Start: name=SystemVDBDeployer state=Create java.lang.NullPointerException at org.teiid.internal.core.index.BlocksIndexInput.close(BlocksIndexInput.java:65) at org.teiid.internal.core.index.Index.initialize(Index.java:222) at org.teiid.internal.core.index.Index.<init>(Index.java:82) at org.teiid.metadata.index.IndexMetadataFactory.getMetadataStore(IndexMetadataFactory.java:119) at org.teiid.deployers.SystemVDBDeployer.start(SystemVDBDeployer.java:48) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) Although we do not yet know what has caused this situation, the NPE is a direct result of a bug in the way the index initialization is performed. In the event the file can not be read, we should simply remove the index entry but we don't get this far because when the file fails to be opened, we attempt to close it to ensure we cleanup our code. The problem is, the object was never initialized due to the file not being opened and therefore, we cause a NullPointerException: Specifically, org.teiid.internal.core.index.BlocksIndexInput.close(): if (raf != null) raf.close(); vraf.close(); should be something like: if (raf != null) raf.close(); if (vraf != null) vraf.close(); -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIID-1693) Update Teiid ADmin Console Documentation

by Ted Jones (JIRA)

Update Teiid ADmin Console Documentation ---------------------------------------- Key: TEIID-1693 URL: https://issues.jboss.org/browse/TEIID-1693 Project: Teiid Issue Type: Task Components: Documentation Affects Versions: 7.4 Reporter: Ted Jones Assignee: Ted Jones Fix For: 7.4.1 The documentation needs to be brought up to date -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIID-1701) Misc procedure enhancements

by Steven Hawkins (JIRA)

Misc procedure enhancements --------------------------- Key: TEIID-1701 URL: https://issues.jboss.org/browse/TEIID-1701 Project: Teiid Issue Type: Enhancement Components: Query Engine Affects Versions: 7.5 Reporter: Steven Hawkins Assignee: Steven Hawkins Add support for compound/block statements (rather than only allowing them at the top level of loops/if), BEGIN [[NOT] ATOMIC] for block level transactions, loop/block labels, and the leave statement. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1602) Add support for like_regex and other regex functions

by Steven Hawkins (JIRA)

Add support for like_regex and other regex functions ---------------------------------------------------- Key: TEIID-1602 URL: https://issues.jboss.org/browse/TEIID-1602 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.5 Consider adding: like_regex substring_regex (as well as ANSI substring handling) position_regex this would somewhat obviate the need to add similar predicate handling although that should be added eventually as well. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

1
2
0 / 0

[JBoss JIRA] Created: (TEIID-1671) Need to add a place holder for the future deployment of Netezza

by Van Halbert (JIRA)

Need to add a place holder for the future deployment of Netezza --------------------------------------------------------------- Key: TEIID-1671 URL: https://issues.jboss.org/browse/TEIID-1671 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 7.4.1 Reporter: Van Halbert Assignee: Ramesh Reddy Priority: Blocker Fix For: 7.4.1 Add a place holder in 7.4.x for the ability to slide in Netezza when it becomes available. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 4 months

3
3
0 / 0

[JBoss JIRA] (TEIID-993) Enhance XML processing to execute relational queries in parallel when possible

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-993?page=com.atlassian.jira.plugin.... ] Steven Hawkins closed TEIID-993. -------------------------------- > Enhance XML processing to execute relational queries in parallel when possible > ------------------------------------------------------------------------------ > > Key: TEIID-993 > URL: https://issues.jboss.org/browse/TEIID-993 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4.1, 7.5 > > > Per feedback from Barry, was reviewing XML processing and because we execute all queries serially in our XML processing. However, conceptually, we could often execute multiple mapping class and/or temp table queries in parallel. When time permits it might be benefitial to investigate this. > All mapping classes at depth "n" in the document model are independent of each other, so they can be executed in parallel. Each mapping class may have input sets to any ancestor mapping class up to depth "n-1", or may select from any temp table up to depth "n" (the same depth). -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1843) StackOverflow using a changing expression as a boolean condition

by Steven Hawkins (Created) (JIRA)

StackOverflow using a changing expression as a boolean condition ---------------------------------------------------------------- Key: TEIID-1843 URL: https://issues.jboss.org/browse/TEIID-1843 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.6 If a changing value is used as a condition directly, e.g. col = case when changing.y then ... The rewriter will fail to replace the changing value and we will continually attempt to rewrite the base update as a loop procedure. -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1719) Executing an SQL statement over ODBC interface does not respond

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1719?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1719. --------------------------------- > Executing an SQL statement over ODBC interface does not respond > --------------------------------------------------------------- > > Key: TEIID-1719 > URL: https://issues.jboss.org/browse/TEIID-1719 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.4.1 > Reporter: Pavel Macik > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.4.1, 7.5 > > Attachments: odbc-reproducer.zip, teiid-520ER2.log.zip > > > When one tries to execute an SQL query using ODBC interface of EDS it the execution get stuck in the phase of waiting for results from EDS. > An ODBC connection from client is established, a query is sent to EDS, EDS executes the query against the underlying Oracle DB, EDS receives the response from the DB, but does not return the response back to the ODBC client... > To reproduce: > 1) deploy perf.vdb from resources into SOA-P > 2) start SOA-P > 3) unzip odbc-reproducer.zip > 4) execute clean.sh > 5) execute build.sh > 6) configure SERVER and ODBC_DRIVER according to your SOA-P and ODBC installation in the run-test.sh script file > 7) execute run-test.sh > Resources (*-ds.xml, *.sql schema and perf.vdb) can be found here https://svn.devel.redhat.com/repos/jboss-soa/trunk/qa/tests/teargas/perfo... -- 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

12 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1771) 7.3 or older clients see the wrong column metadata

by Steven Hawkins (Created) (JIRA)

7.3 or older clients see the wrong column metadata -------------------------------------------------- Key: TEIID-1771 URL: https://issues.jboss.org/browse/TEIID-1771 Project: Teiid Issue Type: Quality Risk Components: Query Engine Affects Versions: 7.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 7.4.1, 7.6 The fix for TEIID-1534 corrected column name vs. column label. However 7.3 clients use the column name and label interchangeably and typically uses column name. When running against 7.4 or later the column name needs to be reported as the label for legacy clients to work appropriately. -- 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

12 years, 4 months

3
2
0 / 0

[JBoss JIRA] (TEIID-1729) EDS XML as source - results returned on 1st query only, subsequent query returns 0 rows - Streaming logic problem

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1729?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-1729. --------------------------------- > EDS XML as source - results returned on 1st query only, subsequent query returns 0 rows - Streaming logic problem > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIID-1729 > URL: https://issues.jboss.org/browse/TEIID-1729 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.4.1, 7.5 > Reporter: Warren Gibson > Assignee: Steven Hawkins > Priority: Critical > Fix For: 7.4.1, 7.6 > > > Submitted the following queries to SOAP-5.2 ER3 server: > SELECT * FROM vParts > SELECT * FROM vParts where Part_Name = 'windshield' > SELECT * FROM vParts > Results were returned on the first query but 0 rows returned on the other queries. this can be > duplicated. > The log file, PartsData.xml file and VDB are attached. -- 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

12 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2012