November 2017 - teiid-issues - Jboss List Archives

[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: ------------------------------------- What do you suggest how we follow a release process for this? > 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.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)

7 years, 2 months

1
0
0 / 0

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

by dalex dalex (JIRA)

dalex dalex created TEIID-5133: ---------------------------------- Summary: 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: eiid-9.3.4 on WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) Reporter: dalex dalex Assignee: Steven Hawkins 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)

7 years, 2 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 commented on TEIID-4863: --------------------------------------- It can be a component, but there isn't a complete notion of a subproject. > 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.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)

7 years, 2 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: ------------------------------------- Should we move this into another sub-project and handle its JIRAs there? like web-console etc. I forgot how we created sub project. > 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.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)

7 years, 2 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 commented on TEIID-4863: --------------------------------------- Do you want to mark this as resolved or move it to a different release bucket so that we can close out 10.0? > 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.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)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5122) Osisoft Translator - Teiid pushes cast from Boolean to Single/Double

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5122?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5122. ----------------------------------- Fix Version/s: 10.1 (was: 10.0) Resolution: Done Applied the proposed fix from Andrej. > Osisoft Translator - Teiid pushes cast from Boolean to Single/Double > -------------------------------------------------------------------- > > Key: TEIID-5122 > URL: https://issues.jboss.org/browse/TEIID-5122 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Ramesh Reddy > Fix For: 10.1 > > > Osisoft PI does not support conversion from Boolean to Single or Double, however, query such as > {code:sql} > select cast(booleanvalue as float) from Source.smalla > {code} > is pushed as > {code:sql} > SELECT cast(g_0.BooleanValue AS Single) AS c_0 FROM dvqe..SmallA AS g_0 > {code} > which results in > {noformat} > com.osisoft.rdsa.RdsaException: [PIOLEDBENT] [SQL Analyzer] [Line 1:14] Cannot cast 'Boolean' to 'Single'. > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5132) max-active-plans property limit one higher than set.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5132?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5132. ----------------------------------- Fix Version/s: 10.1 Resolution: Done I could not determine a reason for that old change. There were no unit tests or other behavior that seemed dependent upon it. Changed to exactly enforcing the max active plans. > max-active-plans property limit one higher than set. > ---------------------------------------------------- > > Key: TEIID-5132 > URL: https://issues.jboss.org/browse/TEIID-5132 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Priority: Minor > Fix For: 10.1 > > > Setting the max-active-plans property limits the number of queries that are processed concurrently, however, in our testing, the actual number of concurrent queries is consistently one higher than the max-active-plans setting, i.e. setting max-active-plans to 1 allows two concurrent queries etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4992) Add OSDQ set functions

by vivek singh (JIRA)

[ https://issues.jboss.org/browse/TEIID-4992?page=com.atlassian.jira.plugin... ] vivek singh commented on TEIID-4992: ------------------------------------ I made some tweaks in code. I get following output now. This code will be checked into 6.2.4 [abcd] [abcd] [] [] [abcd] [abcd] [abcd, x] [abcd, x] [vivek16, vivek44] [vivek36, vivek445, vivekkk] [abcd, vivek16, vivek36, vivek44, vivek445, vivekkk, x] [abcd, vivek16, vivek36, vivek44, vivek445, vivekkk, x] [abcd, x] [abcd, x] [vivek16, vivek44, xx] [vivek36, vivek445, vivekkk] [abcd, vivek16, vivek36, vivek44, vivek445, vivekkk, x, xx] [abcd, vivek16, vivek36, vivek44, vivek445, vivekkk, x, xx] one of basic premises of Set is - all members are unique and the resultant set members are also unique. When we have fuzzy set, then the members which falls within similarity distance are duplicated and need to be removed. So the logic now is first deDup Fuzzy set using similarity algorithms and then do fuzzy union, intersection or minus. This tweak is added now. > Add OSDQ set functions > ---------------------- > > Key: TEIID-4992 > URL: https://issues.jboss.org/browse/TEIID-4992 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > Attachments: SetUtil.java > > > There will be a new osdq core library drop in maven central soon containing additional functions for Teiid to add. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5106) Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5106?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5106: --------------------------------------- Thanks for pointing that out. It has been corrected. > Tables names are case sensitive in Postgres/Oracle/MSSQL but not in Teiid. > -------------------------------------------------------------------------- > > Key: TEIID-5106 > URL: https://issues.jboss.org/browse/TEIID-5106 > Project: Teiid > Issue Type: Quality Risk > Components: JDBC Connector > Reporter: sameer P > Assignee: Steven Hawkins > Fix For: 10.0 > > > In Postgres/Oracle/MS , I can create two tables with the same name (but different cases): test12 and Test12 (by quoting it in create script) , but, Teiid complains saying duplicate table name and fails with the below error: > {code:java} > 16:53:11,161 WARN [org.teiid.RUNTIME] (Worker0_async-teiid-threads0) TEIID50036 VDB test.1 model "dsms" metadata failed to load. Reason:TEIID60013 Duplicate Table public.test12: org.teiid.metadata.DuplicateRecordException: TEIID60013 Duplicate Table public.test12 > at org.teiid.metadata.Schema.addTable(Schema.java:51) > at org.teiid.metadata.MetadataFactory.addTable(MetadataFactory.java:179) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:368) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.addTable(JDBCMetdataProcessor.java:351) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getTables(JDBCMetdataProcessor.java:324) > at org.teiid.translator.jdbc.JDBCMetdataProcessor.getConnectorMetadata(JDBCMetdataProcessor.java:166) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:306) > at org.teiid.translator.jdbc.JDBCExecutionFactory.getMetadata(JDBCExecutionFactory.java:69) > at org.teiid.query.metadata.NativeMetadataRepository.getMetadata(NativeMetadataRepository.java:96) > at org.teiid.query.metadata.NativeMetadataRepository.loadMetadata(NativeMetadataRepository.java:62) > at org.teiid.query.metadata.ChainingMetadataRepository.loadMetadata(ChainingMetadataRepository.java:55) > at org.teiid.jboss.VDBService$6.run(VDBService.java:341) > at org.teiid.jboss.VDBService$7.run(VDBService.java:392) > 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:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5132) max-active-plans property limit one higher than set.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5132?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5132: --------------------------------------- I see a change was made back in 7.4.1 to allow the additional active plan. I don't recall if that was done for a specific case. Let me investigate. > max-active-plans property limit one higher than set. > ---------------------------------------------------- > > Key: TEIID-5132 > URL: https://issues.jboss.org/browse/TEIID-5132 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.12.x-6.4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Priority: Minor > > Setting the max-active-plans property limits the number of queries that are processed concurrently, however, in our testing, the actual number of concurrent queries is consistently one higher than the max-active-plans setting, i.e. setting max-active-plans to 1 allows two concurrent queries etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 2 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2017