April 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5131) Create ansible playbooks for the ansible service broker

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5131. ----------------------------------- Resolution: Out of Date Marking this issue as out of date - there is still potentially a need for a better starting docker image for openshift, but that can be done under a new issue. Most of this work has been supplanted by work done for the openshift service image build process under https://issues.jboss.org/projects/TEIIDTOOLS > Create ansible playbooks for the ansible service broker > ------------------------------------------------------- > > Key: TEIID-5131 > URL: https://issues.jboss.org/browse/TEIID-5131 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.3 > > Attachments: teiid.png > > > For some of the most common usage patterns, we should create playbooks that contribute service brokers via the ansible service broker. This could be: > salesforce as db > couchbase as db/odata > mongodb as db/odata > other openshift databases as odata -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5307) Add views referential_constraints, key_column_usage, table_constraints to information_schema

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5307?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5307: ---------------------------------- Issue Type: Enhancement (was: Bug) Fix Version/s: 10.3 > Add views referential_constraints, key_column_usage, table_constraints to information_schema > -------------------------------------------------------------------------------------------- > > Key: TEIID-5307 > URL: https://issues.jboss.org/browse/TEIID-5307 > Project: Teiid > Issue Type: Enhancement > Components: ODBC, Query Engine > Reporter: Divyesh Vallabh > Assignee: Steven Hawkins > Fix For: 10.3 > > > Outside of what is reference in npgsql provider, it seems as though PowerBI also references following views to generate schema information > Add column in information_schema.columns > * data_type > Add support for information_schema.referential_constraints ( > https://www.postgresql.org/docs/current/static/infoschema-referential-con...) to teiid > Add support for information_schema.key_column_usage ( > https://www.postgresql.org/docs/current/static/infoschema-key-column-usag...) to teiid > Add support for information_schema.table_constraints ( > https://www.postgresql.org/docs/current/static/infoschema-table-constrain...) to teiid -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5307) Add views referential_constraints, key_column_usage, table_constraints to information_schema

by Divyesh Vallabh (JIRA)

Divyesh Vallabh created TEIID-5307: -------------------------------------- Summary: Add views referential_constraints, key_column_usage, table_constraints to information_schema Key: TEIID-5307 URL: https://issues.jboss.org/browse/TEIID-5307 Project: Teiid Issue Type: Bug Components: ODBC, Query Engine Reporter: Divyesh Vallabh Assignee: Steven Hawkins Outside of what is reference in npgsql provider, it seems as though PowerBI also references following views to generate schema information Add column in information_schema.columns * data_type Add support for information_schema.referential_constraints ( https://www.postgresql.org/docs/current/static/infoschema-referential-con...) to teiid Add support for information_schema.key_column_usage ( https://www.postgresql.org/docs/current/static/infoschema-key-column-usag...) to teiid Add support for information_schema.table_constraints ( https://www.postgresql.org/docs/current/static/infoschema-table-constrain...) to teiid -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

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: ------------------------------------ [~shawkins] at last I could check the fix from TEIID-5242 issue and it worked, thx again. > 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)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5306) JDG is doing away with hot rod client, going primarily with rest interface

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5306?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-5306: ------------------------------------ The hotrod client image contained all the modules needed to deploy for hotrod integration. And that made it easier to rebuild an image, like JDV, when a CVE or CP release of the hotrod client was needed. Didn't require the underlying JDV product to be rebuilt. So the same intent was used with the JDV JDBC driver. As to why JDV didn't included the JDG jars in its image, the reason is as mentioned above. However, now JDV will either have to create its own image with the needed jar's or will have to change its build to pull in the jar's. But will still need to consider the impact of JDG related changes on having to rebuild JDV. > JDG is doing away with hot rod client, going primarily with rest interface > -------------------------------------------------------------------------- > > Key: TEIID-5306 > URL: https://issues.jboss.org/browse/TEIID-5306 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > JDG is deprecating the JDG 7.2.x hot rod client and moving to provide exclusively rest interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5306) JDG is doing away with hot rod client, going primarily with rest interface

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5306?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5306: ------------------------------------- The protstream jars that are needed for hotrod access are already part of the distribution in upstream. Can you point me to link where Infinispan team is making this announcement to deprecating the hotrod client? > JDG is doing away with hot rod client, going primarily with rest interface > -------------------------------------------------------------------------- > > Key: TEIID-5306 > URL: https://issues.jboss.org/browse/TEIID-5306 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > JDG is deprecating the JDG 7.2.x hot rod client and moving to provide exclusively rest interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5306) JDG is doing away with hot rod client, going primarily with rest interface

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5306?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5306: ------------------------------- Comment: was deleted (was: A comment with security level 'Red Hat Employee' was removed.) > JDG is doing away with hot rod client, going primarily with rest interface > -------------------------------------------------------------------------- > > Key: TEIID-5306 > URL: https://issues.jboss.org/browse/TEIID-5306 > Project: Teiid > Issue Type: Feature Request > Components: JDG Connector > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Critical > > JDG is deprecating the JDG 7.2.x hot rod client and moving to provide exclusively rest interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5306) JDG is doing away with hot rod client, going primarily with rest interface

by Van Halbert (JIRA)

Van Halbert created TEIID-5306: ---------------------------------- Summary: JDG is doing away with hot rod client, going primarily with rest interface Key: TEIID-5306 URL: https://issues.jboss.org/browse/TEIID-5306 Project: Teiid Issue Type: Feature Request Components: JDG Connector Reporter: Van Halbert Assignee: Steven Hawkins Priority: Critical JDG is deprecating the JDG 7.2.x hot rod client and moving to provide exclusively rest interfaces. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5224) Osisoft translator - general lateral join support

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5224?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5224: --------------------------------- Fix Version/s: 8.12.13.6_4 > Osisoft translator - general lateral join support > ------------------------------------------------- > > Key: TEIID-5224 > URL: https://issues.jboss.org/browse/TEIID-5224 > Project: Teiid > Issue Type: Quality Risk > Components: Connector API, Misc. Connectors, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.2, 8.12.13.6_4 > > > Osisoft PI only supports a lateral join between a table and a table value function - not between a table and a derived table / inline view. However those joins are pushed down as pi advertises general lateral join support. Additional capabilities and possibly extension metadata may be required for the engine to differentiate these cases. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5269) Odata4 metadata roundtrip is not in place

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5269?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5269: --------------------------------- Fix Version/s: 8.12.13.6_4 > Odata4 metadata roundtrip is not in place > ----------------------------------------- > > Key: TEIID-5269 > URL: https://issues.jboss.org/browse/TEIID-5269 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors, OData > Affects Versions: 8.12.12.6_4 > Reporter: Jan Stastny > Assignee: Steven Hawkins > Fix For: 10.0.4, 10.2, 10.1.2, 8.12.13.6_4 > > > Teiid should be able to import (using odata4 translator) metadata exposed by its own odata4 interface. > Currently there is following identified discrepancy. > Foreign keys are not properly carried through the expose/import roundtrip. After importing metadata from odata4 endpoint for another vdb (all in single instance), the resulting metadata lacks FK definitions. > For following data exposed in a VDB: > {code:sql} > CREATE VIEW A(a_id integer PRIMARY KEY, a_value string) AS SELECT 1, 'a1' UNION ALL SELECT 2, 'a2'; > CREATE VIEW B(b_id integer PRIMARY KEY, b_value string) AS SELECT 3, 'b1' UNION ALL SELECT 4, 'b2'; > CREATE VIEW C(c_id integer PRIMARY KEY, a_ref integer, b_ref integer, > FOREIGN KEY (a_ref) REFERENCES A(a_id), > FOREIGN KEY (b_ref) REFERENCES B(b_id)) > AS SELECT 5, 1, 3 UNION ALL SELECT 6, 2, 4; > {code} > the following odata4 metadata are served: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <edmx:Edmx xmlns:edmx="http://docs.oasis-open.org/odata/ns/edmx" Version="4.0"> > <edmx:Reference Uri="http://localhost:8080/odata4/static/org.apache.olingo.v1.xml"> > <edmx:Include Namespace="org.apache.olingo.v1" Alias="olingo-extensions"/> > </edmx:Reference> > <edmx:DataServices> > <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="teiid5221data.1.data" Alias="data"> > <EntityType Name="A"> > <Key> > <PropertyRef Name="a_id"/> > </Key> > <Property Name="a_id" Type="Edm.Int32" Nullable="false"/> > <Property Name="a_value" Type="Edm.String" MaxLength="4000"/> > <NavigationProperty Name="C_FK0" Type="Collection(data.C)"/> > </EntityType> > <EntityType Name="B"> > <Key> > <PropertyRef Name="b_id"/> > </Key> > <Property Name="b_id" Type="Edm.Int32" Nullable="false"/> > <Property Name="b_value" Type="Edm.String" MaxLength="4000"/> > <NavigationProperty Name="C_FK1" Type="Collection(data.C)"/> > </EntityType> > <EntityType Name="C"> > <Key> > <PropertyRef Name="c_id"/> > </Key> > <Property Name="c_id" Type="Edm.Int32" Nullable="false"/> > <Property Name="a_ref" Type="Edm.Int32"/> > <Property Name="b_ref" Type="Edm.Int32"/> > <NavigationProperty Name="FK0" Type="data.A"/> > <NavigationProperty Name="FK1" Type="data.B"/> > </EntityType> > <EntityContainer Name="data"> > <EntitySet Name="A" EntityType="data.A"> > <NavigationPropertyBinding Path="C_FK0" Target="C"/> > </EntitySet> > <EntitySet Name="B" EntityType="data.B"> > <NavigationPropertyBinding Path="C_FK1" Target="C"/> > </EntitySet> > <EntitySet Name="C" EntityType="data.C"> > <NavigationPropertyBinding Path="FK0" Target="A"/> > <NavigationPropertyBinding Path="FK1" Target="B"/> > </EntitySet> > </EntityContainer> > </Schema> > </edmx:DataServices> > </edmx:Edmx> > {code} > Then, when I import from the odata4 endpoint I get following: > {code:sql} > ===> SET NAMESPACE 'http://www.jboss.org/teiiddesigner/ext/odata/2012' AS teiid_odata; > CREATE FOREIGN TABLE A ( > a_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'), > a_value string, > PRIMARY KEY(a_id) > ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.A', "teiid_odata:Type" 'ENTITY_COLLECTION'); > CREATE FOREIGN TABLE B ( > b_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'), > b_value string, > PRIMARY KEY(b_id) > ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.B', "teiid_odata:Type" 'ENTITY_COLLECTION'); > CREATE FOREIGN TABLE C ( > c_id integer NOT NULL OPTIONS (NATIVE_TYPE 'Edm.Int32'), > a_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'), > b_ref integer OPTIONS (NATIVE_TYPE 'Edm.Int32'), > PRIMARY KEY(c_id) > ) OPTIONS (UPDATABLE TRUE, "teiid_odata:NameInSchema" 'data.C', "teiid_odata:Type" 'ENTITY_COLLECTION'); > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues April 2018