June 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3685: --------------------------------------- What version are you looking at? > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4, 8.7.2.6_2 > > Attachments: datasert.csv, INTERNAL_TEST.zip, test.vdb > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Hisanobu Okuda updated TEIID-3685: ---------------------------------- Attachment: test.vdb > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4, 8.7.2.6_2 > > Attachments: datasert.csv, INTERNAL_TEST.zip, test.vdb > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Hisanobu Okuda reopened TEIID-3685: ----------------------------------- Please find the attached reproducer test.vdb. Deploy it, and run the following query:- call procs.ppp1; call procs.ppp2; call procs.ppp3; They are corresponding the above queries. > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4, 8.7.2.6_2 > > Attachments: datasert.csv, INTERNAL_TEST.zip > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3685) org.teiid.padSpace does not affect to the "IN" operator

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIID-3685?page=com.atlassian.jira.plugin... ] Hisanobu Okuda commented on TEIID-3685: --------------------------------------- This is not fixed. 1. SELECT * FROM #TEMP WHERE #TEMP.TEXT IN ('AAAA ', 'test'); 2. SELECT * FROM #TEMP WHERE #TEMP.TEXT IN ('AAAA', 'test'); 3. SELECT * FROM #TEMP WHERE #TEMP.TEXT = 'AAAA'; The query 1 and 3 returns a record. But the query 2 returns no record. > org.teiid.padSpace does not affect to the "IN" operator > ------------------------------------------------------- > > Key: TEIID-3685 > URL: https://issues.jboss.org/browse/TEIID-3685 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7.1 > Environment: JBoss DV 6.1.2 > Reporter: hisao furuichi > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4, 8.7.2.6_2 > > Attachments: datasert.csv, INTERNAL_TEST.zip > > > org.teiid.padSpace does affect to "=" operator. But does not affect to "IN" operator. > [data for a column named "id"] > {noformat} > "test1 " > {noformat} > ["=" operator] I can get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id ='TEST1'; > {noformat} > ["IN" operator] I can not get a result > {noformat} > SELECT * FROM ViewModel.originalViewTable WHERE ViewModel.originalViewTable.id IN ('TEST1', 'TEST2'); > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4266) Convert the Teiid examples to gitbook

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4266?page=com.atlassian.jira.plugin... ] Kylin Soong resolved TEIID-4266. -------------------------------- Resolution: Done * I have split excel data source from HelloWord federation example to a separate module due to compatible with the document. * The document can be view on https://teiid.gitbooks.io/teiid-quickstarts/content/ > Convert the Teiid examples to gitbook > ------------------------------------- > > Key: TEIID-4266 > URL: https://issues.jboss.org/browse/TEIID-4266 > Project: Teiid > Issue Type: Task > Components: Documentation > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: 9.1 > > > https://docs.jboss.org/author/display/teiidexamples/Home should be added to our gitbook documentation set to complete the move out of Confluence. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4187) Extend support for PI OLEDB Enterprise Queries in OSI PI Translator

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-4187?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-4187: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) > Extend support for PI OLEDB Enterprise Queries in OSI PI Translator > ------------------------------------------------------------------- > > Key: TEIID-4187 > URL: https://issues.jboss.org/browse/TEIID-4187 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.13.3 > Reporter: Al S > Assignee: Ramesh Reddy > Priority: Minor > Attachments: PI-OLEDB-Enterprise-2012-User-Guide.pdf > > > Background - PI OLEDB queries go against the PI Data Archive whereas PI OLEDB Enterprise go against PI AF, which is a metadata layer that sits atop the PI Data Archive. Both sets of queries are now accessible from the PI JDBC adapter. > Please add the following enhancements to allow the OSI PI translator to work more effectively with OLEDB Enterprise queries. > 1) Import table valued functions as Teiid procedures > 2) Allow the pushdown of nested table joins > 3) Update the PI translator to use the CROSS APPLY syntax. > 4) When importing schemas, importer.ImportKeys has to be set to false as otherwise we receive a DuplicateRecord exception since the table value function ft_GetPIPoint appears in more than one place in the AF schemas. Could we please put in a fix/workaround to address this? > Please refer to the OLEDB Enterprise Guide for query syntax and rules for more detail. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4273) With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4273?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4273. ----------------------------------- Resolution: Done Added a check for evaluatable subqueries. > With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4273 > URL: https://issues.jboss.org/browse/TEIID-4273 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1 > > > A query such as: > WITH qry_0 as /\*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /\*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0 > where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4273) With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4273?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-4273: ---------------------------------- Description: A query such as: WITH qry_0 as /\*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /\*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0 where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+). was: A query such as: WITH qry_0 as /*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0 where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+). > With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table > --------------------------------------------------------------------------------------------------- > > Key: TEIID-4273 > URL: https://issues.jboss.org/browse/TEIID-4273 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.1, 9.0.1 > > > A query such as: > WITH qry_0 as /\*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /\*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0 > where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4273) With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-4273: ------------------------------------- Summary: With clause used in evaluatable subquery in a fully pushed user query is seen as missing temp table Key: TEIID-4273 URL: https://issues.jboss.org/browse/TEIID-4273 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 9.1, 9.0.1 A query such as: WITH qry_0 as /*+ no_inline */ (SELECT e2 AS a1, e1 as str FROM pm1.g1 AS t), qry_1 as /*+ no_inline */ (SELECT 'b' AS a1) select (select a1 || 'a' from qry_1) as x, a1 from qry_0 where the projected scalar subquery cannot be pushed down, but the rest of the query can will result in the with plan for qry_1 not being associated with the parent RelationalPlan and results in an exception that the temporary table cannot be found. This does not occur if the clause is inlined (9.0+). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3834) Error during (re) adding connection factory using CLI

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3834?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3834: --------------------------------------- Yes Steve that is known. There have been multiple avenues that we've tried to get the upstream behavior changed, but no luck so far. > Error during (re) adding connection factory using CLI > ----------------------------------------------------- > > Key: TEIID-3834 > URL: https://issues.jboss.org/browse/TEIID-3834 > Project: Teiid > Issue Type: Sub-task > Components: Server > Affects Versions: 8.13 > Reporter: Kylin Soong > Assignee: Ramesh Reddy > > enable datasource command > {code} > /subsystem=datasources/data-source=h2:enable > {code} > seems redundant, cause datasource add already enable it, so if execute setup.cli > {code} > ./bin/jboss-cli.sh --connect --file=setup.cli > {code} > will cause a eror > {code} > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.h2 is already registered", > "rolled-back" => true > } > 14:35:55,436 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 9) WFLYCTL0013: Operation ("enable") failed - address: ([ > ("subsystem" => "datasources"), > ("data-source" => "h2") > ]): org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source-config.h2 is already registered > at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 2016