[JBoss JIRA] (TEIID-3030) Update Saxon to current release (9.5.x)
by Gary Gregory (JIRA)
[ https://issues.jboss.org/browse/TEIID-3030?page=com.atlassian.jira.plugin... ]
Gary Gregory commented on TEIID-3030:
-------------------------------------
Good news. Thank you Steven.
> Update Saxon to current release (9.5.x)
> ---------------------------------------
>
> Key: TEIID-3030
> URL: https://issues.jboss.org/browse/TEIID-3030
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 8.7
> Environment: Apache Maven 3.2.2 (45f7c06d68e745d05611f7fd14efb6594181933e; 2014-06-17T09:51:42-04:00)
> Maven home: C:\Java\apache-maven-3.2.2
> Java version: 1.7.0_60, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_60\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> Reporter: Gary Gregory
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> Our product embeds a Teiid server and provides its own set of 3rd party jar files, one of which clashes with Teiid: we provide Saxon-HE 9.4.0.6 and Teiid provides 9.2.1.5. These two versions are NOT binary compatible.
> This shows up using the web services connector as a class not found error because some classes have been repackaged between Saxon 9.2.x and 9.4.x.
> If Teiid updates to the latest version (9.5), so can we, and avoid backporting our Saxon dependencies.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIID-3042) expose dependency information in system tables
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3042:
-------------------------------------
Summary: expose dependency information in system tables
Key: TEIID-3042
URL: https://issues.jboss.org/browse/TEIID-3042
Project: Teiid
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
We should expose additional view/procedure and even column information in terms of their dependencies.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3041:
---------------------------------------
We also will need to add parsing support for enterprise types as those are referenced by the document model / mapping classes. There isn't a great analog for enterprise types in DDL yet as they are scoped to the vdb and not to a schema.
It would make some sense to just put all of this information into a modification of the mapping document xml rather than adding ddl modifications.
> Add support for xml document models in ddl
> ------------------------------------------
>
> Key: TEIID-3041
> URL: https://issues.jboss.org/browse/TEIID-3041
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3041?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3041:
---------------------------------------
What we would need to support is:
staging table - this is not too complicated, it just would need an extension property to identify as a staging table (however we used to support input sets)
mapping class - would need an extension property to identify as a mapping class, but it supports a notion of bindings for the input sets. It's more natural to think of bindings as procedure parameters
document - column names contain . and has an xml document for the "transformation"
> Add support for xml document models in ddl
> ------------------------------------------
>
> Key: TEIID-3041
> URL: https://issues.jboss.org/browse/TEIID-3041
> Project: Teiid
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Fix For: 8.9
>
>
> xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIID-3041) Add support for xml document models in ddl
by Steven Hawkins (JIRA)
Steven Hawkins created TEIID-3041:
-------------------------------------
Summary: Add support for xml document models in ddl
Key: TEIID-3041
URL: https://issues.jboss.org/browse/TEIID-3041
Project: Teiid
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.9
xml document model support was left out of the initial ddl design, but since the feature has not yet been retargeted from designer we should add support.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[JBoss JIRA] (TEIID-2955) Teiid selects incorrect source when conformed table is included in SQL JOIN
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-2955?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-2955.
---------------------------------
> Teiid selects incorrect source when conformed table is included in SQL JOIN
> ---------------------------------------------------------------------------
>
> Key: TEIID-2955
> URL: https://issues.jboss.org/browse/TEIID-2955
> Project: Teiid
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 8.7
> Environment: teiid 8.7
> Reporter: Filip Elias
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
> Attachments: server.log
>
>
> I have two models. postgres for PostgreSQL and mysql for MySQL. I have table test.conformedTable in the both models
> and I have configured conformedTable to be conformed. Table tablepostgre is in the PostgreSQL database. Table tablemysql in the MySQL.
> I want to join conformedTable with tablepostgre and tablemysql.
> The query
> select a.*,b.* from mysql.test.conformedTable as a, tablemysql b where a.id=b.id
> is processed OK, but query
> select a.*,b.* from mysql.test.conformedTable as a, tablepostgre b where a.id=b.id throws an exception (in the attachment)
> It seems that teiid searches tablepostgre in the mysql database, but the table is in the postgresql
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 10 months
[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 closed TEIID-2975.
---------------------------------
> mark the xmloutputfactory as a repairing namespace
> ---------------------------------------------------
>
> Key: TEIID-2975
> URL: https://issues.jboss.org/browse/TEIID-2975
> Project: Teiid
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Query Engine
> Affects Versions: 7.7.10
> Reporter: Johnathon Lee
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.7.1
>
>
> 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.6#6264)
9 years, 10 months