August 2018 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5372) Enhance docker support

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5372?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5372: --------------------------------------- There are only about 7 projects that actively maintain jboss-dockerfiles repo locations. In conferring with Rob Cernich it appears that they may be wanting communities to maintain their own images. At this point it could be worth considering just providing a dockerfile and skip providing the base image entirely. > Enhance docker support > ---------------------- > > Key: TEIID-5372 > URL: https://issues.jboss.org/browse/TEIID-5372 > Project: Teiid > Issue Type: Enhancement > Reporter: Rafal Korytkowski > Assignee: Rafal Korytkowski > Priority: Optional > Fix For: 11.1 > > > Currently there's limited support for docker in Teiid, which can be enabled by adding -Ddocker=true to the build command. The generated image is based on CentOS and running standalone on the Wildfly server. Latest builds are pushed to https://hub.docker.com/r/jboss/teiid/, but versions are not tagged automatically with releases. Development with Docker is not supported. > Proposed changes: > 1. Produce docker image based on Alpine, which is better suited for microservices, in addition to CentOS. > 2. Automatically tag versions in Docker when doing releases. > 3. Support development by providing a docker-compose file with the possibility to start server in a debug mode and enabled auto-redeployment of code changes. > 4. Optionally provide a Docker image for building code using maven in Docker. Having Docker as the only prerequisite is convenient for CI environments and makes the build environment agnostic. > [~shawkins], [~rareddy], thoughts? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5416) Upgrade web-console to 3.1.0

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-5416?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-5416: ------------------------------------- Looks like I need to do some name cleanup, and publish to maven central but here is the link for latest 3.1.0 download link. https://repository.jboss.org/nexus/service/local/repositories/thirdparty-... > Upgrade web-console to 3.1.0 > ---------------------------- > > Key: TEIID-5416 > URL: https://issues.jboss.org/browse/TEIID-5416 > Project: Teiid > Issue Type: Task > Components: Server > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 11.1 > > > Upgrade the Teiid Web-Console to 3.1.0 version -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5430) Closing Teiid JDBC connection is delayed 5 seconds

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5430?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5430: --------------------------------- Fix Version/s: 8.12.15.6_4 > Closing Teiid JDBC connection is delayed 5 seconds > -------------------------------------------------- > > Key: TEIID-5430 > URL: https://issues.jboss.org/browse/TEIID-5430 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.12.13.6_4 > Reporter: Hiroki Daicho > Assignee: Steven Hawkins > Fix For: 11.1, 8.12.15.6_4 > > Attachments: JDBCClient.java > > > Teiid JDBC Driver waits 5 seconds during closing connection when the client can not reach teiid server. > If many connections are pooling by the client as a Datasource, it takes more time the closing all connections. > e.g. if the datasource has 50 connections, the close time would be 5 seconds * 50. > [1] is the stacktrace whie the connection is closing with the delay. > When closing connection, teiid JDBC waits server response by Future#get() with timeout of 5 seconds. > So, it would be waiting for the time if the socket doesn't receive any response. > [1] Stacktrace when the connection waits 5 seconds. > {code} > "main" #1 prio=5 os_prio=0 tid=0x00007f5b1c009000 nid=0x707b runnable [0x00007f5b238ac000] > java.lang.Thread.State: RUNNABLE > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.socketRead(SocketInputStream.java:116) > at java.net.SocketInputStream.read(SocketInputStream.java:171) > at java.net.SocketInputStream.read(SocketInputStream.java:141) > at java.io.BufferedInputStream.fill(BufferedInputStream.java:246) > at java.io.BufferedInputStream.read(BufferedInputStream.java:265) > - locked <0x000000071c98cad0> (a org.teiid.core.util.AccessibleBufferedInputStream) > at java.io.DataInputStream.readInt(DataInputStream.java:387) > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:97) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:416) > at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:117) > at org.teiid.net.socket.SocketServerInstanceImpl.read(SocketServerInstanceImpl.java:308) > at org.teiid.net.socket.SocketServerInstanceImpl$RemoteInvocationHandler$1.get(SocketServerInstanceImpl.java:411) > at org.teiid.net.socket.SocketServerConnection.logoff(SocketServerConnection.java:331) > at org.teiid.net.socket.SocketServerConnection.close(SocketServerConnection.java:306) > - locked <0x000000071c51bb48> (a org.teiid.net.socket.SocketServerConnection) > at org.teiid.jdbc.ConnectionImpl.close(ConnectionImpl.java:282) > at ClientMain.invoke(ClientMain.java:83) > at ClientMain.main(ClientMain.java:30) > {code} > [2] > https://github.com/teiid/teiid/blob/master/client/src/main/java/org/teiid... > {code} > private void logoff() { > disconnect(); > try { > //make a best effort to send the logoff > Future<?> writeFuture = this.serverInstance.getService(ILogon.class).logoff(); > writeFuture.get(5000, TimeUnit.MILLISECONDS); > } catch (Exception e) { > //ignore > } > closeServerInstance(); > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5422) Buffer cleaner running too often in some cases

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5422?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5422: --------------------------------- Fix Version/s: 8.12.15.6_4 > Buffer cleaner running too often in some cases > ---------------------------------------------- > > Key: TEIID-5422 > URL: https://issues.jboss.org/browse/TEIID-5422 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 11.0.1, 10.3.3, 8.12.15.6_4 > > > As observed in TEIID-5418 when the buffer cleaner runs too often it causes thrashing by pushing out pages that get reused close to the cleaning interval of 100 milliseconds. > Increasing that interval to at least beyond the default time-slice will consume more heap - but the cleaner will still be engaged when a processing thread must clean beyond the max allowed. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5435) Cassandra translator broken due to missing Guava dependency

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5435?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5435. ----------------------------------- Fix Version/s: 11.1 10.3.4 11.0.2 Resolution: Done Added an export of the guava dependency as well. > Cassandra translator broken due to missing Guava dependency > ----------------------------------------------------------- > > Key: TEIID-5435 > URL: https://issues.jboss.org/browse/TEIID-5435 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Jan Martiska > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 11.1, 10.3.4, 11.0.2 > > > After the fix TEIID-5433 fixing the Cassandra resource adapter, I'm seeing a similar error, this time from the translator: > {noformat} > 13:22:01,986 ERROR [org.teiid.CONNECTOR] (Worker2_QueryProcessorQueue1635) ErXTPMPKCQ29 Connector worker process failed for atomic-request=ErXTPMPKCQ29.730.1.268: java.lang.NoClassDefFoundError: com/google/common/util/concurrent/MoreExecutors > [mppr] at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:88) > [mppr] at org.teiid.translator.cassandra.CassandraQueryExecution.execute(CassandraQueryExecution.java:75) > [mppr] at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:382) > [mppr] at sun.reflect.GeneratedMethodAccessor102.invoke(Unknown Source) > [mppr] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > [mppr] at java.lang.reflect.Method.invoke(Method.java:498) > [mppr] at org.teiid.dqp.internal.datamgr.ConnectorManager$1.invoke(ConnectorManager.java:229) > [mppr] at com.sun.proxy.$Proxy36.execute(Unknown Source) > [mppr] at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:302) > [mppr] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:108) > [mppr] at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:104) > [mppr] at java.util.concurrent.FutureTask.run(FutureTask.java:266) > [mppr] at org.teiid.dqp.internal.process.FutureWork.run(FutureWork.java:61) > [mppr] at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:277) > [mppr] at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:115) > [mppr] at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:206) > [mppr] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > [mppr] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > [mppr] at java.lang.Thread.run(Thread.java:748) > [mppr] > {noformat} > It can be fixed by adding com.google.guava dependency to the translator module. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5417) Performance degradation with large in predicate against temp table

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5417?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5417: --------------------------------- Fix Version/s: 8.12.15.6_4 > Performance degradation with large in predicate against temp table > ------------------------------------------------------------------ > > Key: TEIID-5417 > URL: https://issues.jboss.org/browse/TEIID-5417 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 11.1, 11.0.1, 10.3.3, 8.12.15.6_4 > > > Dependent joins producing a large in predicate will do a linear search over the predicate. The predicate should be marked as all constants and dealt with as a set instead. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5390) Concurrent repeated add attempts create orphaned blocks

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-5390?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-5390: --------------------------------- Fix Version/s: 8.12.15.6_4 > Concurrent repeated add attempts create orphaned blocks > ------------------------------------------------------- > > Key: TEIID-5390 > URL: https://issues.jboss.org/browse/TEIID-5390 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 11.0, 10.3.2, 10.2.3, 8.12.15.6_4 > > > If both a user thread and the buffer cleaner are evicting the same batch/page at the same time - and multiple attempts are made by one of the threads it will result in duplicate inode / data block entries being created, which then cannot be cleaned. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4761) Support lpad/rpad pushdown to sql server

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-4761?page=com.atlassian.jira.plugin... ] Johnathon Lee updated TEIID-4761: --------------------------------- Fix Version/s: 8.12.15.6_4 > Support lpad/rpad pushdown to sql server > ---------------------------------------- > > Key: TEIID-4761 > URL: https://issues.jboss.org/browse/TEIID-4761 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Connector > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.3, 8.12.15.6_4 > > > lpad/rpad is not pushded down to sql server since it lacked a direct equivalent - but it can be supported with an expression. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-2476: ---------------------------------- > Exclude hidden tables/columns from metadata > ------------------------------------------- > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0, 8.12.15.6_4 > > > We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2476) Exclude hidden tables/columns from metadata

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2476?page=com.atlassian.jira.plugin... ] Johnathon Lee closed TEIID-2476. -------------------------------- Resolution: Done > Exclude hidden tables/columns from metadata > ------------------------------------------- > > Key: TEIID-2476 > URL: https://issues.jboss.org/browse/TEIID-2476 > Project: Teiid > Issue Type: Enhancement > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.15.6_4, 9.0 > > > We should offer or possibly default to filtering tables/columns that can not accessed out of the user metadata. This should be done on the server side - however given the reuse we have of the system tables for example for materialized pg catalog queries - it is easier to add filters to the DatabaseMetadata (and ideally pg) metadata queries. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues August 2018