May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2975) mark the xmloutputfactory as a repairing namespace

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2975?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2975: ---------------------------------- Fix Version/s: 8.7.1 8.8 Component/s: Query Engine > mark the xmloutputfactory as a repairing namespace > --------------------------------------------------- > > Key: TEIID-2975 > URL: https://issues.jboss.org/browse/TEIID-2975 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Affects Versions: 7.7.10 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Avoiding issue similar to [1] in cases of non-steaming xml where using a staxsource. The response is forwarded to the body and effectively loses any namespace declarations that are part of the soap envelope. > [1] > [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue13) TEIID30020 Processing exception for request a6bkC44ELQu9.3 'TEIID30151 Error building Source for context item.'. Originally TeiidProcessingException 'The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.' org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source).: org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item. > at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:140) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:226) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_71] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_71] > at java.lang.Thread.run(Thread.java:680) [rt.jar:1.6.0_71] > Caused by: nu.xom.ParsingException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. > at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] > at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:134) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > ... 7 more > Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. > at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:171) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] > ... 10 more > Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2939) Issues with applying row based security

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2939?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2939: --------------------------------- Fix Version/s: 8.4.2 > Issues with applying row based security > --------------------------------------- > > Key: TEIID-2939 > URL: https://issues.jboss.org/browse/TEIID-2939 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7.1, 8.8 > > > If a view over a left outer join has a row condition and is used in a simple aggregation: > select count\(*) from vw > Then a null pointer exception will occur when considering optional joins. > If intervening criteria is added: > select count\(*) from vw where ... > we can get past the initial error, but will fail in initializing the join node with an assertion error. Both of these have the same root issue, which is our attempt to make the logic selective about when assign output elements is run, which leads to the output elements not being in place when later needed. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-2930: --------------------------------- Fix Version/s: 7.7.10 (was: 7.7.9) > SCROLL keyword for DECLARE CURSOR not being parsed correctly > ------------------------------------------------------------ > > Key: TEIID-2930 > URL: https://issues.jboss.org/browse/TEIID-2930 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8, 7.7.10 > > > The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1] > [1] > http://www.postgresql.org/docs/8.4/static/sql-declare.html > [2] > https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii... > Example of error: > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"] > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0] > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0 > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8] > FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully. > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY> -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2972. --------------------------------- Labels: Beta1 (was: ) Fix Version/s: 8.7.1 8.8 Resolution: Done 1) Changed the DDLStringVisitor to always include the namespace even if they were built-in namespaces. During Parsing: 2) If name space is presented with same URI but different prefix, it will be considered as built-in namespace 3) If prefix matches with built-in prefix but the URI does not match then error thrown 4) if both match, it is like no-op > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2974) Excel translator extension property not specified correctly.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2974?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2974. --------------------------------- Labels: Beta1 (was: ) Fix Version/s: 8.7.1 8.8 Resolution: Done Changed applicable to Table.class > Excel translator extension property not specified correctly. > ------------------------------------------------------------ > > Key: TEIID-2974 > URL: https://issues.jboss.org/browse/TEIID-2974 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Labels: Beta1 > Fix For: 8.7.1, 8.8 > > > The FIRST_DATA_ROW_NUMBER extension property for excel is specified as applicable to Column. It should be Table. > See line 53 of ExcelMetadataProcessor. > We noticed a mismatch between the DDL where its specified on the table options. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2974) Excel translator extension property not specified correctly.

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2974?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2974: ------------------------------------- should we push this in 8.7.1 too? > Excel translator extension property not specified correctly. > ------------------------------------------------------------ > > Key: TEIID-2974 > URL: https://issues.jboss.org/browse/TEIID-2974 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > > The FIRST_DATA_ROW_NUMBER extension property for excel is specified as applicable to Column. It should be Table. > See line 53 of ExcelMetadataProcessor. > We noticed a mismatch between the DDL where its specified on the table options. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2972) adminApi getSchema does not include namespace info in the DDL

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2972?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2972: ------------------------------------- should we push this in 8.7.1? > adminApi getSchema does not include namespace info in the DDL > ------------------------------------------------------------- > > Key: TEIID-2972 > URL: https://issues.jboss.org/browse/TEIID-2972 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > Attachments: excelSheet.ddl > > > I was following this community example > https://community.jboss.org/wiki/MicrosoftExcelDocumentIntoRelationalTable > The DDL returned for the deployed dynamic vdb is attached. However, the DDL does not include a namespace statement like this > SET NAMESPACE 'http://www.teiid.org/translator/excel/2014' AS teiid_excel -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2975) mark the xmloutputfactory as a repairing namespace

by Johnathon Lee (JIRA)

Johnathon Lee created TEIID-2975: ------------------------------------ Summary: mark the xmloutputfactory as a repairing namespace Key: TEIID-2975 URL: https://issues.jboss.org/browse/TEIID-2975 Project: Teiid Issue Type: Feature Request Affects Versions: 7.7.10 Reporter: Johnathon Lee Assignee: Steven Hawkins Avoiding issue similar to [1] in cases of non-steaming xml where using a staxsource. The response is forwarded to the body and effectively loses any namespace declarations that are part of the soap envelope. [1] [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue13) TEIID30020 Processing exception for request a6bkC44ELQu9.3 'TEIID30151 Error building Source for context item.'. Originally TeiidProcessingException 'The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound.' org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source).: org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item. at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:140) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:226) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:269) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:214) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) [rt.jar:1.6.0_71] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) [rt.jar:1.6.0_71] at java.lang.Thread.run(Thread.java:680) [rt.jar:1.6.0_71] Caused by: nu.xom.ParsingException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] at nu.xom.Builder.build(Unknown Source) [xom-1.2.7-redhat-3.jar:1.2.7-redhat-3] at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:134) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] ... 7 more Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:171) [teiid-engine-8.4.1-redhat-7.jar:8.4.1-redhat-7] ... 10 more Caused by: net.sf.saxon.trans.XPathException: org.xml.sax.SAXParseException: The prefix "xsi" for attribute "xsi:nil" associated with an element type "<element>" is not bound. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2974) Excel translator extension property not specified correctly.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2974?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2974: ---------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Excel translator extension property not specified correctly. > ------------------------------------------------------------ > > Key: TEIID-2974 > URL: https://issues.jboss.org/browse/TEIID-2974 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Mark Drilling > Assignee: Ramesh Reddy > > The FIRST_DATA_ROW_NUMBER extension property for excel is specified as applicable to Column. It should be Table. > See line 53 of ExcelMetadataProcessor. > We noticed a mismatch between the DDL where its specified on the table options. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2974) Excel translator extension property not specified correctly.

by Mark Drilling (JIRA)

Mark Drilling created TEIID-2974: ------------------------------------ Summary: Excel translator extension property not specified correctly. Key: TEIID-2974 URL: https://issues.jboss.org/browse/TEIID-2974 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7 Reporter: Mark Drilling Assignee: Steven Hawkins The FIRST_DATA_ROW_NUMBER extension property for excel is specified as applicable to Column. It should be Table. See line 53 of ExcelMetadataProcessor. We noticed a mismatch between the DDL where its specified on the table options. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014