June 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-4946) Support function SUBSTRING_INDEX in MySQL5ExecutionFactory

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4946?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4946: ---------------------------------- Component/s: JDBC Connector Query Engine Fix Version/s: 10.0 We'll evaluate if it makes sense to add this as an engine function as well. > Support function SUBSTRING_INDEX in MySQL5ExecutionFactory > ---------------------------------------------------------- > > Key: TEIID-4946 > URL: https://issues.jboss.org/browse/TEIID-4946 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector, Query Engine > Reporter: Pedro Inácio > Assignee: Steven Hawkins > Fix For: 10.0 > > > It is currently difficult to achieve the same functionality that is offered by *SUBSTRING_INDEX * function without direct support from _MySQL5ExecutionFactory_. > So it would be nice to have this function implemented in the execution factory. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4945: --------------------------------------- There must be more going on than that. Your exception means that the client is looking for a column with the VDBName label. This is not something that the driver will do internally - it's coming from client code in some way. So we need to find what query it believes VDBName should be associated with. > Teiid java client error (Column name "VDBName" does not exist) > -------------------------------------------------------------- > > Key: TEIID-4945 > URL: https://issues.jboss.org/browse/TEIID-4945 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 9.2.3 > Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology. > Reporter: Fábio Guilherme > Assignee: Steven Hawkins > > This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error). > Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error: > {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist. > 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available. > 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException > it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color} > i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)

by Fábio Guilherme (JIRA)

[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ] Fábio Guilherme commented on TEIID-4945: ---------------------------------------- For the querie the ontology i use this: PREFIX : <http://www.test.org#> select * where{ ?i a :country ; :shipImo ?imo ; :hasValue ?value . } For the mapping i use: mappingId M_country target :atribute{imo} a :country ; :shipImo {imo} ; :hasValue {country}. source select "imo", "country", "numb_owners" from "ship" Thanks for your replie > Teiid java client error (Column name "VDBName" does not exist) > -------------------------------------------------------------- > > Key: TEIID-4945 > URL: https://issues.jboss.org/browse/TEIID-4945 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 9.2.3 > Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology. > Reporter: Fábio Guilherme > Assignee: Steven Hawkins > > This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error). > Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error: > {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist. > 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available. > 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException > it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color} > i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4945: --------------------------------------- At a minimum we'll need the query this is associated with. > Teiid java client error (Column name "VDBName" does not exist) > -------------------------------------------------------------- > > Key: TEIID-4945 > URL: https://issues.jboss.org/browse/TEIID-4945 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 9.2.3 > Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology. > Reporter: Fábio Guilherme > Assignee: Steven Hawkins > > This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error). > Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error: > {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist. > 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available. > 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException > it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color} > i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4945?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4945: ---------------------------------- Issue Type: Bug (was: Feature Request) Priority: Major (was: Blocker) > Teiid java client error (Column name "VDBName" does not exist) > -------------------------------------------------------------- > > Key: TEIID-4945 > URL: https://issues.jboss.org/browse/TEIID-4945 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 9.2.3 > Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology. > Reporter: Fábio Guilherme > Assignee: Steven Hawkins > > This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error). > Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error: > {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist. > 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available. > 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException > it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color} > i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4946) Support function SUBSTRING_INDEX in MySQL5ExecutionFactory

by Pedro Inácio (JIRA)

Pedro Inácio created TEIID-4946: ----------------------------------- Summary: Support function SUBSTRING_INDEX in MySQL5ExecutionFactory Key: TEIID-4946 URL: https://issues.jboss.org/browse/TEIID-4946 Project: Teiid Issue Type: Enhancement Reporter: Pedro Inácio Assignee: Steven Hawkins It is currently difficult to achieve the same functionality that is offered by *SUBSTRING_INDEX * function without direct support from _MySQL5ExecutionFactory_. So it would be nice to have this function implemented in the execution factory. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4945) Teiid java client error (Column name "VDBName" does not exist)

by Fábio Guilherme (JIRA)

Fábio Guilherme created TEIID-4945: -------------------------------------- Summary: Teiid java client error (Column name "VDBName" does not exist) Key: TEIID-4945 URL: https://issues.jboss.org/browse/TEIID-4945 Project: Teiid Issue Type: Feature Request Components: JDBC Driver Affects Versions: 9.2.3 Environment: Running teiid 9.2.3 on wildfly, failing using java client with 9.2.3 driver and sucess using protege with driver 9.2.3. both use ontop for mapping the data from db to the ontology. Reporter: Fábio Guilherme Assignee: Steven Hawkins Priority: Blocker This java client uses ontop to make the mapping from a db to a ontology. I had prior version where i was mapping my data from a postgres db to the ontology using ontop, in my recent version i changed the db to a teiid db(where i get the error). Using teiid 9.2.3 and wildfly with java client with 9.2.3 driver i get this error: {color:red}Error obtaining the Metadataorg.teiid.jdbc.TeiidSQLException: Column name "VDBName" does not exist. 09:31:15.411 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - Could not initialize the Quest query answering engine. Answering queries will not be available. 09:31:15.427 [http-nio-8081-exec-8] ERROR i.u.k.o.o.owlapi3.QuestOWL - java.lang.NullPointerException it.unibz.krdb.obda.model.OBDAException: java.lang.NullPointerException{color} i used the same driver(9.2.3) on protege with ontop-pro and i dont get any error. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4944) Remove misc deprecated code

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4944: ------------------------------------- Summary: Remove misc deprecated code Key: TEIID-4944 URL: https://issues.jboss.org/browse/TEIID-4944 Project: Teiid Issue Type: Task Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 With a new major release we can remove older deprecated code. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4943) Allow translators to declare if copied criteria should be included

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4943: ------------------------------------- Summary: Allow translators to declare if copied criteria should be included Key: TEIID-4943 URL: https://issues.jboss.org/browse/TEIID-4943 Project: Teiid Issue Type: Enhancement Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 10.0 When an inner join with a predicate that can be copied is pushed, we will still create the copied criteria. In some situations, this over-constraining is not desirable. There should be a capability to determine if this copying should take place. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4875) Planning issue with multiple aggregate decompositions through a join tree

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4875?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4875: ---------------------------------- Fix Version/s: 9.2.4 (was: 9.2.3) > Planning issue with multiple aggregate decompositions through a join tree > ------------------------------------------------------------------------- > > Key: TEIID-4875 > URL: https://issues.jboss.org/browse/TEIID-4875 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.x-6.4, 8.12.11.6_3, 9.2.4 > > > The logic for determining other symbols from aggregates will not work correctly when a staged grouping is initially pushed and another staged grouping is then pushed above a join that is above that location (typically due to join predicates that pull in other groups). > A query such as: > SELECT max(t3.e4), max(t2.e4) as s FROM pm1.g1 as t1, pm1.g2 as t2, pm1.g3 as t3, pm1.g4 as t4, pm2.g1 as t5 WHERE t1.e1 = t2.e1 and (t2.e2 = t3.e2 and t1.e3 || t2.e3 = t3.e3) and t3.e3 = t4.e3 and t4.e4 = t5.e4 > With capabilities that disable join pushdown will fail with an assertionerror that a staged grouping symbol cannot be found during the initialization of the parent join node. > java.lang.AssertionError: ASSERTION FAILED: expected reference to be not null > at org.teiid.core.util.Assertion.failed(Assertion.java:73) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:100) > at org.teiid.core.util.Assertion.isNotNull(Assertion.java:92) > at org.teiid.query.processor.relational.RelationalNode.getProjectionIndexes(RelationalNode.java:367) > at org.teiid.query.processor.relational.JoinNode.initialize(JoinNode.java:133) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:96) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.connectExternal(RelationalPlan.java:102) > at org.teiid.query.processor.relational.RelationalPlan.initialize(RelationalPlan.java:91) > at org.teiid.query.processor.QueryProcessor.init(QueryProcessor.java:226) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:138) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:114) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:164) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:146) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 June 2017