February 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5172) Missing message for key "TEIID31262"

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5172?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5172: --------------------------------- Fix Version/s: 8.12.12.6_4 > Missing message for key "TEIID31262" > ------------------------------------ > > Key: TEIID-5172 > URL: https://issues.jboss.org/browse/TEIID-5172 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.11.6_4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 10.1, 10.0.1, 9.3.6, 8.12.12.6_4 > > > When creating tests for TEIID-4557, I ran into missing message for an exception: > {noformat} > [org.teiid.PROCESSOR] (Worker0_QueryProcessorQueue200) TEIID30019 Unexpected exception for request oekxHV8aThTk.100: org.teiid.core.TeiidComponentException: TEIID31261 TEIID31262 <Missing message for key "TEIID31262" in: org.teiid.query.i18n> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5130) Document/refine behavior of treating result parameter as the first parameter

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5130?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5130: --------------------------------- Fix Version/s: 8.12.12.6_4 > Document/refine behavior of treating result parameter as the first parameter > ---------------------------------------------------------------------------- > > Key: TEIID-5130 > URL: https://issues.jboss.org/browse/TEIID-5130 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.5, 8.12.12.6_4 > > > DDL and metadata import make the assumption that the return parameter is the first in the underlying metadata (in part to ensure support of varargs), but we still allowed the result parameter to appear anywhere in the parameter list as to maintain backwards compatibility with legacy/Designer ddl. However in index metadata there is slightly different behavior in that the result parameter remains in it's original position. > We need to clarify this behavior - more documentation, enforce/validate that the result parameter is first in ddl, or perform the same reordering for index metadata. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-4950) PostgreSQL Linux ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4950?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4950: --------------------------------- Fix Version/s: 8.12.12.6_4 > PostgreSQL Linux ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1 > ---------------------------------------------------------------------------------------- > > Key: TEIID-4950 > URL: https://issues.jboss.org/browse/TEIID-4950 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 9.1.1 > Environment: Oracle Linux 7.3 > OBIEE 12c > unixODBC > Official PostgreSQL ODBC Drivers > Reporter: Steve Boyce > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.1, 8.12.12.6_4 > > > PostgreSQL ODBC driver v09.06.0100 and newer does not work with Teiid Server 9.1.1 > This is an OBIEE 12c/unixODBC error: > {noformat} > [2017-06-06T15:00:48.159+00:00] [OBIS] [ERROR:1] [] [] [ecid: 005KKjYVpflEkJ4_VTS4yc0004Vq0002Lh,0:1] [sik: ssi] [tid: a5dc9700] [nQSError: 16001] ODBC error state: 50000 code: 110 message: [unixODBC]ERROR: TEIID31100 Parsing error: Encountered "[*]SET[*] DateStyle =" at line 1, column 1. [[ > file: server/Query/Execution/DbGateway/Odbc35/../Odbc/Src/SQXDGOdbcConnection.cpp; line: 1009 > Properties: description=ExecutePhysical Exchange; producerID=0x321b5ff8; requestID=0x61ac0002; sessionID=0x61ac0000; userName=weblogic; > Was expecting: "alter" | "begin" | "call" | "create" | "delete" | "drop" | "exec" | "execute" | "insert" | "merge" .... > {noformat} > Looking at the source code for the ODBC drivers, it seems that switching from CC_send_settings to CC_send_query for setting various settings does not work with Teiid. > {noformat} > # grep -r -i --include *.c DateStyle psqlodbc-09* > psqlodbc-09.05.0400/connection.c: CC_send_settings(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2"); > psqlodbc-09.06.0100/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL); > psqlodbc-09.06.0200/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL); > psqlodbc-09.06.0300/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL); > psqlodbc-09.06.0310/connection.c: res = CC_send_query(self, "SET DateStyle = 'ISO';SET extra_float_digits = 2;" ISOLATION_SHOW_QUERY, NULL, 0, NULL); > {noformat} > I'm not sure if the bug is with the ODBC driver or this was an intentional change that Postgres Server can deal with and therefore Teiid server should be able to deal with. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5261) Add support for Teiid Spring vs VDB

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/TEIID-5261?page=com.atlassian.jira.plugin... ] Arvind Gopinath updated TEIID-5261: ----------------------------------- Attachment: Errorlogs.txt > Add support for Teiid Spring vs VDB > ----------------------------------- > > Key: TEIID-5261 > URL: https://issues.jboss.org/browse/TEIID-5261 > Project: Teiid > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Steven Hawkins > Priority: Minor > Attachments: Errorlogs.txt > > > The virtual View construction happens with Annotations using Teiid Spring Boot. > Without annotations, it will be value added if Teiid Spring Boot supports VDB. > Referring below example to implement the same using Spring Boot - > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5261) Add support for Teiid Spring vs VDB

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/TEIID-5261?page=com.atlassian.jira.plugin... ] Arvind Gopinath commented on TEIID-5261: ---------------------------------------- [^Errorlogs.txt] [~rareddy] Once I add the dependency in pom.xml, I have got the exception and attached the logs for your reference. Thanks for your help. > Add support for Teiid Spring vs VDB > ----------------------------------- > > Key: TEIID-5261 > URL: https://issues.jboss.org/browse/TEIID-5261 > Project: Teiid > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Steven Hawkins > Priority: Minor > Attachments: Errorlogs.txt > > > The virtual View construction happens with Annotations using Teiid Spring Boot. > Without annotations, it will be value added if Teiid Spring Boot supports VDB. > Referring below example to implement the same using Spring Boot - > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5262) Remove support for Teiid 7.x clients/servers

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5262: ------------------------------------- Summary: Remove support for Teiid 7.x clients/servers Key: TEIID-5262 URL: https://issues.jboss.org/browse/TEIID-5262 Project: Teiid Issue Type: Quality Risk Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.2 There is no need to maintain support for 7.x clients/servers given the age of those releases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5248) Upgrade to v4 api for google spreadsheets

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5248?page=com.atlassian.jira.plugin... ] Work on TEIID-5248 started by Steven Hawkins. --------------------------------------------- > Upgrade to v4 api for google spreadsheets > ----------------------------------------- > > Key: TEIID-5248 > URL: https://issues.jboss.org/browse/TEIID-5248 > Project: Teiid > Issue Type: Quality Risk > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.2 > > > Our integration is based upon the v3 api, which will soon be deprecated. This will be a large change given the api differences. We can also look to include TEIID-5040 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5261) Add support for Teiid Spring vs VDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5261?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5261: ------------------------------------- >> End goal we are trying to figure out how to dockerise the deployment. Preferrable in the wildfly swarm mode. [~arvindo] you are in luck, we are trying to do the exact same thing for OpenShift environment, involves same steps. So, are you trying to do simple docker image or are you also trying to get that image into OpenShift? Depending upon it the data source configuration is somewhat different. As I mentioned before, and also on the above examples site these examples are stale and written for older version of the WildFly Swarm. It is on my todo to update these examples. >> All good, but in Wildfly swarm, we could not able to access the vdb through ODATA. I didnt find the right way/example for how to do that. with wildfly-swarm all you would do is add a dependency in your pom.xml like {code} <dependency> <groupId>org.wildfly.swarm</groupId> <artifactId>odata</artifactId> </dependency> {code} That should enable the OData access. Try with latest version "2018.2.0" version of the Wildfly-swarm as I made a change to the OData, then tell us what is not working. > Add support for Teiid Spring vs VDB > ----------------------------------- > > Key: TEIID-5261 > URL: https://issues.jboss.org/browse/TEIID-5261 > Project: Teiid > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Steven Hawkins > Priority: Minor > > The virtual View construction happens with Annotations using Teiid Spring Boot. > Without annotations, it will be value added if Teiid Spring Boot supports VDB. > Referring below example to implement the same using Spring Boot - > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5258) TEIID30151 Error building Source for context item

by dalex dalex (JIRA)

[ https://issues.jboss.org/browse/TEIID-5258?page=com.atlassian.jira.plugin... ] dalex dalex commented on TEIID-5258: ------------------------------------ Hi [~shawkins] > can you test with master? I'm very sorry, didn't have enough time for checking the bug on master branch. But I'll check the TEIID-5242 changes asap, that's great that you have already fixed it in scope of the DVCORE-5242 issue. Thx. > TEIID30151 Error building Source for context item > ------------------------------------------------- > > Key: TEIID-5258 > URL: https://issues.jboss.org/browse/TEIID-5258 > Project: Teiid > Issue Type: Bug > Components: XML Connector > Affects Versions: 10.1 > Environment: teiid-10.1.0 on WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Attachments: failed.json > > > When running the following script: > {code:sql} > Begin > with t As ( > Select campaign_id, email_address, activity > From ( > call files.getFiles(pathAndPattern => 'failed.json') > ) f > Cross Join > XmlTable ( > '/root/emails' > Passing JsonToXml('root', f.file) > Columns > campaign_id string, > list_id string, > list_is_active boolean, > email_id string, > email_address string, > activity xml > ) x > Where activity Is Not Null > ) > Select * > From t Cross Join XmlTable ( > '/root/activity' > Passing XmlElement(root, t.activity) > Columns > action string, > "timestamp" timestamp, > url string, > ip string > ) a; > End; > {code} > teiid throws out the following error: > {code:noformat} > 2018-02-13 17:55:47,054 WARN [org.teiid.PROCESSOR] (Worker2_QueryProcessorQueue7) /okCCfP2/yjh TEIID30020 Processing exception for request /okCCfP2/yjh.0 'TEIID30151 Error building > Source for context item.'. Originally TeiidProcessingException StaxToEventBridge.java:325.: org.teiid.core.TeiidProcessingException: TEIID30151 Error building Source for context item > . > at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:163) > at org.teiid.query.processor.relational.XMLTableNode$1.run(XMLTableNode.java:265) > at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:280) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: nu.xom.ParsingException > at nu.xom.Builder.build(Unknown Source) > at nu.xom.Builder.build(Unknown Source) > at org.teiid.query.xquery.saxon.XQueryEvaluator.evaluateXQuery(XQueryEvaluator.java:157) > ... 7 more > Caused by: java.lang.NullPointerException > at net.sf.saxon.evpull.StaxToEventBridge.getSystemId(StaxToEventBridge.java:325) > at net.sf.saxon.evpull.StaxToEventBridge.getSystemId(StaxToEventBridge.java:385) > at net.sf.saxon.event.ContentHandlerProxyLocator.getSystemId(ContentHandlerProxyLocator.java:72) > at nu.xom.XOMHandler.startElement(Unknown Source) > at net.sf.saxon.event.ContentHandlerProxy.startContent(ContentHandlerProxy.java:373) > at org.teiid.query.xquery.saxon.ContentHandlerProxyReceiver.startContent(StreamingUtils.java:291) > at net.sf.saxon.event.ProxyReceiver.startContent(ProxyReceiver.java:177) > at org.teiid.query.xquery.saxon.PathMapFilter.startContent(PathMapFilter.java:226) > at net.sf.saxon.event.TreeReceiver.startContent(TreeReceiver.java:220) > at net.sf.saxon.evpull.EventIteratorToReceiver.copy(EventIteratorToReceiver.java:78) > at net.sf.saxon.event.Sender.sendPullEventSource(Sender.java:559) > at net.sf.saxon.event.Sender.send(Sender.java:132) > at net.sf.saxon.Configuration.buildDocument(Configuration.java:3361) > at net.sf.saxon.Configuration.buildDocument(Configuration.java:3303) > at org.teiid.query.xquery.saxon.SaxonReader.parse(StreamingUtils.java:175) > ... 10 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-5261) Add support for Teiid Spring vs VDB

by Arvind Gopinath (JIRA)

[ https://issues.jboss.org/browse/TEIID-5261?page=com.atlassian.jira.plugin... ] Arvind Gopinath commented on TEIID-5261: ---------------------------------------- [~rareddy] End goal we are trying to figure out how to dockerise the deployment. Preferrable in the wildfly swarm mode. I have tried using this example (https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat...) and modified our code to test with our VDB (connecting sqlite Database) and it was running perfectly in wildfly swarm. All good, but in Wildfly swarm, we could not able to access the vdb through ODATA. I didnt find the right way/example for how to do that. I saw your blog on Teiid Spring Boot and I could able to see you have given for same example with OData also. But only thing, i have noticed everything were based on annotations and you were not using VDB for that. We created VDBs for many of our projects and deployed in standalone. That's the reason, I have asked, if there is a way. > Add support for Teiid Spring vs VDB > ----------------------------------- > > Key: TEIID-5261 > URL: https://issues.jboss.org/browse/TEIID-5261 > Project: Teiid > Issue Type: Feature Request > Reporter: Arvind Gopinath > Assignee: Steven Hawkins > Priority: Minor > > The virtual View construction happens with Annotations using Teiid Spring Boot. > Without annotations, it will be value added if Teiid Spring Boot supports VDB. > Referring below example to implement the same using Spring Boot - > https://github.com/teiid/wildfly-swarm-teiid-examples/tree/master/vdb-dat... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2018