November 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5136) Osisoft translator - NPE when running query with LATERAL JOIN

by Andrej Šmigala (JIRA)

Andrej Šmigala created TEIID-5136: ------------------------------------- Summary: Osisoft translator - NPE when running query with LATERAL JOIN Key: TEIID-5136 URL: https://issues.jboss.org/browse/TEIID-5136 Project: Teiid Issue Type: Bug Components: JDBC Connector Reporter: Andrej Šmigala Assignee: Steven Hawkins Running the following query: {code:sql} SELECT bqt2.smalla.intkey, g2.intkey, bqt2.smalla.bytenum FROM bqt2.smalla LEFT JOIN LATERAL (SELECT intkey FROM bqt2.mediuma WHERE bqt2.smalla.bytenum = bqt2.mediuma.bytenum) AS g2 ON true {code} results in a NPE in teiid (before sending source src command). Stacktrace: {noformat} Connector worker process failed for atomic-request=vEbs99yd+srV.1.0.1: java.lang.NullPointerException at org.teiid.translator.jdbc.pi.PIExecutionFactory.translate(PIExecutionFactory.java:273) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:111) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:106) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] at org.teiid.language.visitor.SQLStringVisitor.visit(SQLStringVisitor.java:767) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] at org.teiid.language.Select.acceptVisitor(Select.java:110) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] at org.teiid.language.visitor.AbstractLanguageVisitor.visitNode(AbstractLanguageVisitor.java:51) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] at org.teiid.language.visitor.SQLStringVisitor.append(SQLStringVisitor.java:91) [teiid-api-8.12.11.6_4-redhat-64-7.jar:8.12.11.6_4-redhat-64-7] at org.teiid.translator.jdbc.SQLConversionVisitor.append(SQLConversionVisitor.java:130) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.translator.jdbc.TranslatedCommand.translateCommand(TranslatedCommand.java:76) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.translator.jdbc.JDBCBaseExecution.translateCommand(JDBCBaseExecution.java:120) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.translator.jdbc.JDBCQueryExecution.execute(JDBCQueryExecution.java:114) [translator-jdbc-8.12.11.6_4.jar:8.12.11.6_4] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:363) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_141] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_141] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_141] at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_141] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:211) at com.sun.proxy.$Proxy79.execute(Unknown Source) at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:306) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:112) at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_141] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:65) at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:284) at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:119) at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:210) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_141] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_141] at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_141] {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[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 commented on TEIID-5131: --------------------------------------- I'm not saying there is an issue. Only that I'm starting with the current state based upon the infinispan images / templates. Then I'll adjust things for swarm. > 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.1 > > > 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)

8 years, 5 months

1
0
0 / 0

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5131?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5131: ------------------------------------- What is the issue with WF-Swaram based approach? Fabric 8 plugin should be able to build right? https://maven.fabric8.io/#build-openshift > 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.1 > > > 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)

8 years, 5 months

1
0
0 / 0

[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 commented on TEIID-5131: --------------------------------------- I have emulated the infinispan approach to create an openshift image for our standalone-teiid.xml - infinispan adds a clustered.xml and cloud.xml to the wildfly standalone configurations and they also inject a configuration via the template. The default security realm is used to add application and management users. This is fine for a first cut, but we'll need to have an option to support keycloak/openshift sso (especially for admin). I should have this wired for just salesforce for jdbc access on Monday, such that the template will accept the sf credentials and handle the appropriate vdb / resource adapter configuration. I want to make sure I have a handle on exposing JDBC as a route and to validate clustering/ha with this template (although other than ha there won't be much benefit). The next step will be to expose odata for an existing provisioned instance. I'm not sure if that can be done via templates or if ansible will be required. > 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.1 > > > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5133) XmlTable path language is not always identical to XPathValue expressions

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5133?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5133: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1508911 Bugzilla Update: Perform > XmlTable path language is not always identical to XPathValue expressions > ------------------------------------------------------------------------ > > Key: TEIID-5133 > URL: https://issues.jboss.org/browse/TEIID-5133 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 9.3.4 > Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.7, 9.3.5 > > > The same Path value, used in XPathValue and XmlTable->Path brings different results. > That is for the following query: > {code:sql} > Select * From > (select '<root> > <item> > <id>id1</id> > <val>val1</val> > </item> > </root>' as resp) w, > XMLTABLE( > '/root' passing XMLPARSE(document w.resp) columns > valOption2 string PATH 'item[id = "id1"]/val' > --,valOption1 string PATH 'item[id/text() = "id1"]/val' > ) x;; > {code} > returned value for "valOption2" will be changed from "val1" to "null" that is incorrect and unexpected behavior. > Using "node/text()" in Path expressions may result in side effects. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[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 commented on TEIID-5131: --------------------------------------- Current state: Project Docker repo - https://hub.docker.com/r/teiid/teiid/ images are pushed from the building using the fabric8 plugin. The images are not valid for OpenShift due to permission issues with the standalone directory JBoss Docker repo - https://hub.docker.com/r/jboss/teiid/ images are created as part of an automated build from https://github.com/jboss-dockerfiles/teiid - this is not in sync with either the product or the project. It is also not valid for OpenShift due to permission issues with the standalone directory Potential next steps: Following the infinispan approach, we can update JBoss Docker repo for Teiid to be a valid OpenShift image stream - see https://github.com/jboss-dockerfiles/infinispan/tree/master/server However that approach is based upon WildFly, not swarm, so it is not quite inline with our next state thinking. It would be nice to have a more usable up-to-date community image stream. > 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.1 > > > 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)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4863) Run teiid embedded via Spring Boot

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4863?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4863: ---------------------------------- Component/s: Teiid Spring Boot (was: Embedded) > Run teiid embedded via Spring Boot > ---------------------------------- > > Key: TEIID-4863 > URL: https://issues.jboss.org/browse/TEIID-4863 > Project: Teiid > Issue Type: Feature Request > Components: Teiid Spring Boot > Affects Versions: 10.x > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: tsb-1.0.0 > > > WildFly Swarm can use simple pojo to integrate framework, which compatible with EmbeddedConfiguration, actually this is encouraged way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4863) Run teiid embedded via Spring Boot

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4863?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4863: ---------------------------------- Fix Version/s: tsb-1.0.0 (was: 10.x) > Run teiid embedded via Spring Boot > ---------------------------------- > > Key: TEIID-4863 > URL: https://issues.jboss.org/browse/TEIID-4863 > Project: Teiid > Issue Type: Feature Request > Components: Teiid Spring Boot > Affects Versions: 10.x > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: tsb-1.0.0 > > > WildFly Swarm can use simple pojo to integrate framework, which compatible with EmbeddedConfiguration, actually this is encouraged way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5135) REPEAT function truncates strings to 4000 characters

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5135?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5135: ---------------------------------- Issue Type: Quality Risk (was: Bug) Priority: Minor (was: Critical) The system has a max length for the string data type. That affects all functions evaluated in Teiid. You may adjust this with a system property if you have a different need org.teiid.maxStringLength - https://teiid.gitbooks.io/documents/content/admin/System_Properties.html You should still keep it as constrained as possible as the string type for a live batch is always fully held in memory. > REPEAT function truncates strings to 4000 characters > ---------------------------------------------------- > > Key: TEIID-5135 > URL: https://issues.jboss.org/browse/TEIID-5135 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Affects Versions: 9.3.4 > Environment: teiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) > Reporter: dalex dalex > Assignee: Steven Hawkins > Priority: Minor > > Probably it's not bug. When running the following queries: > {code:sql} > Select Length(Repeat('abcde', 9000));; /* 4000 chars */ > Select Length(Repeat('a', 9000));; /* 4000 chars */ > {code} > Teiid returns 4000 instead of 9000. Can the internal truncation be avoided (maybe in some cases) or not? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4863) Run teiid embedded via Spring Boot

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4863?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-4863: ------------------------------------- Ok, we can add the release version numbers, I missed that. Yes that will work. > Run teiid embedded via Spring Boot > ---------------------------------- > > Key: TEIID-4863 > URL: https://issues.jboss.org/browse/TEIID-4863 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 10.x > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 10.x > > > WildFly Swarm can use simple pojo to integrate framework, which compatible with EmbeddedConfiguration, actually this is encouraged way. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2017