August 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5394: --------------------------------------- The drawback to the build time approach is that it's not straight-forward to flatten vdb.xml nor vdb.ddl contents. It's only straight-forward to flatten on a per schema basis when those are captured as separate ddl files. > so that would be external to the vdb maven plugin, at least right now >From the teiid thorntail examples the project yaml is treated as a resource that is copied into the target/classes, which is then picked up by the vdb maven plugin for inclusion in the .vdb. Is that not what you had in mind? > Define how to utilize multiple vdbs > ----------------------------------- > > Key: TEIID-5394 > URL: https://issues.jboss.org/browse/TEIID-5394 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5424) timestampadd/diff with quarter should not use 91 days

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5424?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5424: --------------------------------- Fix Version/s: 8.12.15.6_4 > timestampadd/diff with quarter should not use 91 days > ----------------------------------------------------- > > Key: TEIID-5424 > URL: https://issues.jboss.org/browse/TEIID-5424 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 11.0.1, 10.3.3, 8.12.15.6_4 > > > Teiid 8.2 and prior used interval approximations including 91 days for a quarter - which is still reflected in the jdbc translator. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5394: ------------------------------------- Instead of thinking like loading all the import vdbs, why not flatten the importing vdb with others at build time? That way we do not have to change deployment semantics. The config yaml is included when the Throntail's uberjar maven task is run, so that would be external to the vdb maven plugin, at least right now. > Define how to utilize multiple vdbs > ----------------------------------- > > Key: TEIID-5394 > URL: https://issues.jboss.org/browse/TEIID-5394 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4520) Support for Exasol Connector

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4520?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4520: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1613448 Bugzilla Update: Perform > Support for Exasol Connector > ---------------------------- > > Key: TEIID-4520 > URL: https://issues.jboss.org/browse/TEIID-4520 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 9.x > Reporter: Van Halbert > Assignee: Rafal Korytkowski > Fix For: 11.0 > > > Requesting support for Exasol Connector -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5439) Batch removed during large internal materialization load

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5439?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5439: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1613463 Bugzilla Update: Perform > Batch removed during large internal materialization load > -------------------------------------------------------- > > Key: TEIID-5439 > URL: https://issues.jboss.org/browse/TEIID-5439 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > For a sufficiently large materialization, such as 33000000 rows by 10 columns of biginteger/string types, the load will not complete and instead produce an exception: > {code} > ERROR: TEIID30019 Unexpected exception for request yGKKEfVoiD5O.0 > org.teiid.core.TeiidRuntimeException: Batch removed > at org.teiid.query.tempdata.TempTableDataManager.rethrow(TempTableDataManager.java:880) > at org.teiid.query.tempdata.TempTableDataManager.access$800(TempTableDataManager.java:92) > at org.teiid.query.tempdata.TempTableDataManager$4.load(TempTableDataManager.java:625) > at org.teiid.query.tempdata.TempTableDataManager$4.createTupleSource(TempTableDataManager.java:548) > at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:108) > at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:401) > at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) > at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) > at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) > at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) > at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) > at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5439) Batch removed during large internal materialization load

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5439: ------------------------------------- Summary: Batch removed during large internal materialization load Key: TEIID-5439 URL: https://issues.jboss.org/browse/TEIID-5439 Project: Teiid Issue Type: Bug Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.1 For a sufficiently large materialization, such as 33000000 rows by 10 columns of biginteger/string types, the load will not complete and instead produce an exception: {code} ERROR: TEIID30019 Unexpected exception for request yGKKEfVoiD5O.0 org.teiid.core.TeiidRuntimeException: Batch removed at org.teiid.query.tempdata.TempTableDataManager.rethrow(TempTableDataManager.java:880) at org.teiid.query.tempdata.TempTableDataManager.access$800(TempTableDataManager.java:92) at org.teiid.query.tempdata.TempTableDataManager$4.load(TempTableDataManager.java:625) at org.teiid.query.tempdata.TempTableDataManager$4.createTupleSource(TempTableDataManager.java:548) at org.teiid.query.tempdata.TempTableDataManager$ProxyTupleSource.nextTuple(TempTableDataManager.java:108) at org.teiid.query.processor.relational.AccessNode.nextBatchDirect(AccessNode.java:401) at org.teiid.query.processor.relational.RelationalNode.nextBatch(RelationalNode.java:277) at org.teiid.query.processor.relational.RelationalPlan.nextBatch(RelationalPlan.java:141) at org.teiid.query.processor.QueryProcessor.nextBatchDirect(QueryProcessor.java:148) at org.teiid.query.processor.QueryProcessor.nextBatch(QueryProcessor.java:111) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:160) at org.teiid.query.processor.BatchCollector.collectTuples(BatchCollector.java:142) at org.teiid.dqp.internal.process.RequestWorkItem.processMore(RequestWorkItem.java:492) {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5413) Make inclusion of DDL schema optional in list-vdbs CLI method

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5413?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5413: --------------------------------- Fix Version/s: 8.12.15.6_4 > Make inclusion of DDL schema optional in list-vdbs CLI method > ------------------------------------------------------------- > > Key: TEIID-5413 > URL: https://issues.jboss.org/browse/TEIID-5413 > Project: Teiid > Issue Type: Enhancement > Components: AdminApi, Server > Affects Versions: 11.0 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 11.1, 8.12.15.6_4 > > > By default the "list-vdbs" and "get-vdb" cli calls include the vdb payload with DDL metadata. It has been observed when the models are huge the web-console fails to work. Provide an option to not include the DDl in payload. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5394: --------------------------------------- Including a dependency to a vdb would look like: {code} <dependency> <groupId>org.teiid.thorntail</groupId> <artifactId>salesforce-as-datasource</artifactId> <version>1.0.0</version> <type>vdb</type> </dependency> {code} This is redundant with the vdb import statement in the vdb.xml/ddl, but makes it easy to include the vdb in the m2repo of thorntail. I'll see how easy it is to trigger a deployment from there. A vdb created by the maven plugin does include the config yaml, but I'm not sure how easy it will be to use or if everything would effectively need to be re-declared in the importing vdb config yaml. > Define how to utilize multiple vdbs > ----------------------------------- > > Key: TEIID-5394 > URL: https://issues.jboss.org/browse/TEIID-5394 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5394) Define how to utilize multiple vdbs

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5394?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5394: --------------------------------------- Looking at THORN-829 they have rejected deployments of higher level artifacts. As you suggest that leaves us with the option of expanding the deployer logic and/or adding build time support. The direction here will probably be to resolve base vdbs as maven artifacts and include them in the .vdb zip (thorntail also has an option to resolve dependencies at runtime) and update the deployer to load them first, then load the importing vdb. In keeping with the decision to not allow EAR deployments the base vdbs should be hidden. > Define how to utilize multiple vdbs > ----------------------------------- > > Key: TEIID-5394 > URL: https://issues.jboss.org/browse/TEIID-5394 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1 > > > Perhaps to support vdb imports, we should define how a build can incorporate multiple vdbs. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5437) ORDER BY combined with UNION/UNION ALL fails on PostgreSQL

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5437?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5437. ----------------------------------- Fix Version/s: 11.1 10.3.4 11.0.2 Resolution: Done The logic was creating an intermediate sort node without the groups assigned so that further pushing was to an inappropriate location. > ORDER BY combined with UNION/UNION ALL fails on PostgreSQL > ---------------------------------------------------------- > > Key: TEIID-5437 > URL: https://issues.jboss.org/browse/TEIID-5437 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: sameer P > Assignee: Steven Hawkins > Priority: Critical > Fix For: 11.1, 10.3.4, 11.0.2 > > > Combining union all and order by does not work when the query is pushed down to PostgreSQL. > The following query with dsp and dwh as postgres datasources, > {code:sql} > select * from ( > select b.i as col1, 'def' as col2 from dsp.test_ep_ds a > left join dwh.test_ep_dwh b on b.str=a.str > union all > select 2 as col1, 'abc' as col2 > )x order by col1 > {code} > Fails with the below errors: > {code:java} > Error: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 dsp_VDB_ID_1: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: [] SQL: SELECT g_0."str" AS c_0 FROM "public"."test_ep_ds" AS g_0 ORDER BY b."i" LIMIT 100] > SQLState: 50000 > ErrorCode: 30504 > {code} > Where as the following query works without any problem: > {code:sql} > select b.i as col1, 'def' as col2 from dsp.test_ep_ds a > left join dwh.test_ep_dwh b on b.str=a.str > union all > select 2 as col1, 'abc' as col2 > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2018