August 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5457) Issues with sybase/ms sql pad pushdown

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-5457?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-5457: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1624408 Bugzilla Update: Perform > Issues with sybase/ms sql pad pushdown > -------------------------------------- > > Key: TEIID-5457 > URL: https://issues.jboss.org/browse/TEIID-5457 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 10.3.4, 11.0.2, 8.12.15.6_4 > > > Sybase will return a non-null result then padding a null string. > Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4251) Built in support for Postgres DB as materialization target

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4251?page=com.atlassian.jira.plugin... ] Work on TEIID-4251 stopped by Steven Hawkins. --------------------------------------------- > Built in support for Postgres DB as materialization target > ---------------------------------------------------------- > > Key: TEIID-4251 > URL: https://issues.jboss.org/browse/TEIID-4251 > Project: Teiid > Issue Type: Sub-task > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 11.1 > > > If Postgres database is available along with install or assumed that it is available, then some of the materialization task can be automated, like > - Creation of a common STATUS table > - Creation of the materilization targets (create views on dbms) > - On load, on undeploy and load scripts for all the materialization views > We need to device a way this to be pluggable, such that based on success of this, we can provide additional support for other sources. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5461) Add parsing and push down support for the frame clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5461?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5461: --------------------------------------- With this issue I can mark Hive/Impala as having initial support for the window frame clause, but their actual support is more nuanced. Only aggregates and the first/last_value analytical functions seem to be allowed. Once we have engine support we'll have to add additional restrictions. > Add parsing and push down support for the frame clause > ------------------------------------------------------ > > Key: TEIID-5461 > URL: https://issues.jboss.org/browse/TEIID-5461 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > To make it possible to introduce these changes into older branches, we should first implement the parsing and push down logic - such that engine processing would initially fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5457) Issues with sybase/ms sql pad pushdown

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5457?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5457: --------------------------------- Fix Version/s: 8.12.15.6_4 > Issues with sybase/ms sql pad pushdown > -------------------------------------- > > Key: TEIID-5457 > URL: https://issues.jboss.org/browse/TEIID-5457 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 10.3.4, 11.0.2, 8.12.15.6_4 > > > Sybase will return a non-null result then padding a null string. > Sybase and ms sql will trim from the string from the left when lpad is specified with a pad length shorter than the string. The expected behavior is to always trim from the right. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5446) Retrieving clob values from Exasol prints stacktrace to server log

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5446?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5446: --------------------------------- Fix Version/s: 8.12.15.6_4 > Retrieving clob values from Exasol prints stacktrace to server log > ------------------------------------------------------------------ > > Key: TEIID-5446 > URL: https://issues.jboss.org/browse/TEIID-5446 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 11.1, 8.12.15.6_4 > Reporter: Andrej Šmigala > Assignee: Steven Hawkins > Fix For: 11.1, 8.12.15.6_4 > > > In Exasol, CLOB is [an alias|https://www.exasol.com/support/secure/attachment/49848/EXASOL_User_...] for VARCHAR. When querying a foreign table with a CLOB column defined as > {code:sql} > ObjectValue clob OPTIONS (NATIVE_TYPE 'varchar(4000)', NAMEINSOURCE 'objectvalue')) > {code}, > an exception is logged in the server output for each row. > The query itself finishes successfully and the returned results are correct. > {noformat} > 12:44:20,959 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr java.lang.Throwable > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at com.exasol.jdbc.Column.type_error(Column.java:26) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at com.exasol.jdbc.Column.getClob(Column.java:137) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at com.exasol.jdbc.EXAResultSet.getClob(EXAResultSet.java:686) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.jboss.jca.adapters.jdbc.WrappedResultSet.getClob(WrappedResultSet.java:1060) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.translator.jdbc.JDBCExecutionFactory.retrieveValue(JDBCExecutionFactory.java:1146) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.translator.jdbc.JDBCQueryExecution.next(JDBCQueryExecution.java:340) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.handleBatch(ConnectorWorkItem.java:455) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.more(ConnectorWorkItem.java:241) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at java.lang.reflect.Method.invoke(Method.java:498) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:229) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at com.sun.proxy.$Proxy36.more(Unknown Source) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:305) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:61) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:44:20,960 ERROR [stderr] (Worker6_QueryProcessorQueue42) axblivLlwkmr at java.lang.Thread.run(Thread.java:748) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5461) Add parsing and push down support for the frame clause

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-5461: ------------------------------------- Summary: Add parsing and push down support for the frame clause Key: TEIID-5461 URL: https://issues.jboss.org/browse/TEIID-5461 Project: Teiid Issue Type: Sub-task Components: Connector API, Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 11.2 To make it possible to introduce these changes into older branches, we should first implement the parsing and push down logic - such that engine processing would initially fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5461) Add parsing and push down support for the frame clause

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5461?page=com.atlassian.jira.plugin... ] Work on TEIID-5461 started by Steven Hawkins. --------------------------------------------- > Add parsing and push down support for the frame clause > ------------------------------------------------------ > > Key: TEIID-5461 > URL: https://issues.jboss.org/browse/TEIID-5461 > Project: Teiid > Issue Type: Sub-task > Components: Connector API, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.2 > > > To make it possible to introduce these changes into older branches, we should first implement the parsing and push down logic - such that engine processing would initially fail. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4355) Move Custom Authorization Validator to Developers Guide

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-4355?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-4355. ----------------------------------- Resolution: Won't Fix > Move Custom Authorization Validator to Developers Guide > ------------------------------------------------------- > > Key: TEIID-4355 > URL: https://issues.jboss.org/browse/TEIID-4355 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > > To keep things consistent, the custom authorization validator section in the security guide should be moved to the Developers Guide. Also, this should include the creation of an archetype. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5414) LISTAGG support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5414?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5414: ---------------------------------- Fix Version/s: 11.2 (was: 11.x) > LISTAGG support > --------------- > > Key: TEIID-5414 > URL: https://issues.jboss.org/browse/TEIID-5414 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Lukáš Svačina > Assignee: Steven Hawkins > Fix For: 11.2 > > > It would be useful to have supported new SQL2016 syntax for *LISTAGG*. Currently TEIID suport only *STRING_AGG *keyword, so I have to regexp replace it in SQL syntax generated by JOOQ sql builder as it uses new *LISTAGG *keyword in default. > Parameteres syntax should be the same in both so the easiest option is to add just alias into grammar. However LISTAGG supports also some advanced syntax which could be useful too. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 8 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... ] Work on TEIID-5394 stopped by Steven Hawkins. --------------------------------------------- > 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.2 > > > 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)

5 years, 8 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