July 2016 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3635) Auto configuration of buffermanager values can be incorrect

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-3635?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-3635: ---------------------------------- > Auto configuration of buffermanager values can be incorrect > ----------------------------------------------------------- > > Key: TEIID-3635 > URL: https://issues.jboss.org/browse/TEIID-3635 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.12, 8.11.3, 8.7.5 > > > If the heap size is significantly larger than 2 gb, such that the auto computed value for the max reserve is larger than 2 gb and the memory buffer size is also auto calculated, then the computed values for max reserve and max memory buffer can be significantly different than expected. At worst this results in the max memory buffer size of 0, which just default the buffer to being accessible by a single thread. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3929) Accumulo does not return null values

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3929: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1301527|https://bugzilla.redhat.com/show_bug.cgi?id=1301527] from ON_QA to VERIFIED > Accumulo does not return null values > ------------------------------------ > > Key: TEIID-3929 > URL: https://issues.jboss.org/browse/TEIID-3929 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.3 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > Fix For: 9.0, 8.12.5 > > > Accumulo doesn't return null values when a whole 'column' is being selected. > For a command in accumulo shell like: > {code:plain} > scan -c name:BYTENUM > {code} > Accumulo returns only non-empty values, this is expected behaviour. > Equivalent query in Teiid would be: > {code:sql} > SELECT ByteNum FROM SmallA > {code} > Which returns the same results as Accumulo does. That means, no NULL values, if there are rowids without specified column families/qualifiers missing. But when a user has his schema defined in a vdb, he probably expects, that he will get as many rows as there are in the table. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4316) Accumulo translator: null values not returned for <> criteria in WHERE clause

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4316?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-4316: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1351987 Bugzilla Update: Perform > Accumulo translator: null values not returned for <> criteria in WHERE clause > ----------------------------------------------------------------------------- > > Key: TEIID-4316 > URL: https://issues.jboss.org/browse/TEIID-4316 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.12.5 > Reporter: Jan Stastny > Assignee: Ramesh Reddy > > For columns, which contain some null values, a query like: > {code:sql} > SELECT nullable_column FROM table_name WHERE nullable_column <> some_value > {code} > doesn't return null values. > Simple select works: > {code:sql} > SELECT nullable_column FROM table_name > {code} > returns all rows regardless whether they are null or not. > IS NULL criteria in WHERE clause also work: > {code:sql} > SELECT nullable_column FROM table_name WHERE nullable_column IS NULL > {code} > returns correct number of null values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4316) Accumulo translator: null values not returned for <> criteria in WHERE clause

by Jan Stastny (JIRA)

Jan Stastny created TEIID-4316: ---------------------------------- Summary: Accumulo translator: null values not returned for <> criteria in WHERE clause Key: TEIID-4316 URL: https://issues.jboss.org/browse/TEIID-4316 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.12.5 Reporter: Jan Stastny Assignee: Ramesh Reddy For columns, which contain some null values, a query like: {code:sql} SELECT nullable_column FROM table_name WHERE nullable_column <> some_value {code} doesn't return null values. Simple select works: {code:sql} SELECT nullable_column FROM table_name {code} returns all rows regardless whether they are null or not. IS NULL criteria in WHERE clause also work: {code:sql} SELECT nullable_column FROM table_name WHERE nullable_column IS NULL {code} returns correct number of null values. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ] Kylin Soong edited comment on TEIID-4311 at 7/1/16 5:53 AM: ------------------------------------------------------------ How to understand templateName in below method? is it a driver name or a exist Datasource name? {code} public void createDataSource(String deploymentName, String templateName, Properties properties) throws AdminException {code} >From AdminFactory line 1208 {code} // get JDBC properties cliCall("read-resource-description", new String[] {"subsystem", "datasources", "data-source", templateName}, null, builder); {code} It looks as a datasource name, but from AdminFactory line 469 {code} Set<String> drivers = getInstalledJDBCDrivers(); if (!drivers.contains(templateName)) { throw new AdminProcessingException(AdminPlugin.Event.TEIID70004, AdminPlugin.Util.gs(AdminPlugin.Event.TEIID70004, templateName)); } {code} it should be the driver name. was (Author: kylin): How to understand templateName in below method? is it a driver name or a exist Datasource name? {code} public void createDataSource(String deploymentName, String templateName, Properties properties) throws AdminException {code} > Teiid Admin Api not support to create XA datasource on Jboss server. > -------------------------------------------------------------------- > > Key: TEIID-4311 > URL: https://issues.jboss.org/browse/TEIID-4311 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.13.x > Reporter: Prakash Jape > Assignee: Kylin Soong > Fix For: 9.1, 9.0.1 > > > Teiid Admin api does not support or does not have capability to create XA datasource on Jboss server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4311: ------------------------------------ How to understand templateName in below method? is it a driver name or a exist Datasource name? {code} public void createDataSource(String deploymentName, String templateName, Properties properties) throws AdminException {code} > Teiid Admin Api not support to create XA datasource on Jboss server. > -------------------------------------------------------------------- > > Key: TEIID-4311 > URL: https://issues.jboss.org/browse/TEIID-4311 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.13.x > Reporter: Prakash Jape > Assignee: Kylin Soong > Fix For: 9.1, 9.0.1 > > > Teiid Admin api does not support or does not have capability to create XA datasource on Jboss server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4293) Some Management CLI should setAllowedValues

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4293?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4293: ------------------------------------ Have filed a new web-console to Jie. > Some Management CLI should setAllowedValues > ------------------------------------------- > > Key: TEIID-4293 > URL: https://issues.jboss.org/browse/TEIID-4293 > Project: Teiid > Issue Type: Enhancement > Components: Server > Affects Versions: 9.1 > Reporter: Kylin Soong > Assignee: Kylin Soong > Fix For: 9.1 > > > * /subsystem=teiid:write-attribute(name=authentication-type,value=USERPASSWORD) - the allowed values should be USERPASSWORD,GSS > * /subsystem=teiid:clear-cache(cache-type=PREPARED_PLAN_CACHE) - the cach-type allowed values should be PREPARED_PLAN_CACHE, QUERY_SERVICE_RESULT_SET_CACHE > * /subsystem=teiid/transport=jdbc:write-attribute(name=protocol,value=teiid) - the protocol allowed values should be teiid, pg,? > * /subsystem=teiid/transport=jdbc:write-attribute(name=keystore-type,value=JKS) - the keystore-type allowed values should be JKS, and ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4297) Add UDF functions based on OSDQ for POC

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4297?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-4297: ------------------------------------ Thanks [~arunwizz], also this kinds of dependencies should be comment out. {code} <dependency> <groupId>ojdbc14</groupId> <artifactId>ojdbc14</artifactId> <version>0.0</version> <scope>system</scope> <systemPath>${project.basedir}/lib/ojdbc14.jar</systemPath> </dependency> <dependency> <groupId>ifxjdbc</groupId> <artifactId>ifxjdbc</artifactId> <version>0.0</version> <scope>system</scope> <systemPath>${project.basedir}/lib/ifxjdbc.jar</systemPath> </dependency> {code} > Add UDF functions based on OSDQ for POC > --------------------------------------- > > Key: TEIID-4297 > URL: https://issues.jboss.org/browse/TEIID-4297 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Ramesh Reddy > Assignee: JieRen JieRen > Fix For: 9.1 > > > Please add following UDF functions to Teiid library based on maven module > http://search.maven.org/#search%7Cga%7C1%7Carrahtec > The UDF functions needs to from this class below > {code} > public class Maskutil { > /** > * @param a > * The string that need to randomize > * vivek singh' will become 'ihg vkeivh' > */ > public static String toRandomValue(String a) { > return ShuffleRTM.shuffleString(a); > } > /** > * @param a > * This function will retrun MD5 hashcode of the string > * @return String > */ > public static String toHashValue(String a) { > if (a == null) > return "d41d8cd98f00b204e9800998ecf8427e"; // null MD5 value > return ResultsetToRTM.getMD5(a).toString(); > } > /** > * @param a > * This function will return digit characters of the string > * @return > * > */ > public static String toDigitValue(String a) { > return StringCaseFormatUtil.digitString(a); > } > } > {code} > for example Teiid should have UDF functions like > {code} > string random(string) > string hash(string) > string digit(string) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ] Kylin Soong reassigned TEIID-4311: ---------------------------------- Assignee: Kylin Soong > Teiid Admin Api not support to create XA datasource on Jboss server. > -------------------------------------------------------------------- > > Key: TEIID-4311 > URL: https://issues.jboss.org/browse/TEIID-4311 > Project: Teiid > Issue Type: Bug > Components: AdminApi > Affects Versions: 8.13.x > Reporter: Prakash Jape > Assignee: Kylin Soong > Fix For: 9.1, 9.0.1 > > > Teiid Admin api does not support or does not have capability to create XA datasource on Jboss server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIID-4258) Cannot connect to Teiid if server runs on JVM 1.6

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-4258?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-4258: ------------------------------------------------ Juraj Duráni <jdurani(a)redhat.com> changed the Status of [bug 1343956|https://bugzilla.redhat.com/show_bug.cgi?id=1343956] from ON_QA to VERIFIED > Cannot connect to Teiid if server runs on JVM 1.6 > ------------------------------------------------- > > Key: TEIID-4258 > URL: https://issues.jboss.org/browse/TEIID-4258 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.12.5 > Environment: JVM 1.6 > Reporter: Juraj Duráni > Assignee: Steven Hawkins > Priority: Blocker > Fix For: 8.12.5 > > > If Teiid runs on JVM 1.6. connection fails with EOFException \[1\] > \[1\] Exception thrown (used squirrel client) > {code:plain} > java.util.concurrent.ExecutionException: java.lang.RuntimeException: org.teiid.jdbc.TeiidSQLException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: null > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.awaitConnection(OpenConnectionCommand.java:132) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$100(OpenConnectionCommand.java:45) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$2.run(OpenConnectionCommand.java:115) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:744) > Caused by: java.lang.RuntimeException: org.teiid.jdbc.TeiidSQLException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: null > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:171) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.access$000(OpenConnectionCommand.java:45) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand$1.run(OpenConnectionCommand.java:104) > ... 5 more > Caused by: org.teiid.jdbc.TeiidSQLException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: null > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:66) > at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:107) > at org.teiid.jdbc.TeiidDriver.connect(TeiidDriver.java:55) > at net.sourceforge.squirrel_sql.fw.sql.SQLDriverManager.getConnection(SQLDriverManager.java:133) > at net.sourceforge.squirrel_sql.client.mainframe.action.OpenConnectionCommand.executeConnect(OpenConnectionCommand.java:167) > ... 7 more > Caused by: org.teiid.net.socket.SingleInstanceCommunicationException: TEIID20020 Error establishing socket to host and port: localhost:31000. Reason: null > at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:161) > at org.teiid.net.socket.SocketServerConnection.<init>(SocketServerConnection.java:95) > at org.teiid.net.socket.SocketServerConnectionFactory.getConnection(SocketServerConnectionFactory.java:316) > at org.teiid.jdbc.SocketProfile.connect(SocketProfile.java:64) > ... 11 more > Caused by: java.io.EOFException > at java.io.DataInputStream.readInt(DataInputStream.java:392) > at org.teiid.netty.handler.codec.serialization.ObjectDecoderInputStream.readObjectOverride(ObjectDecoderInputStream.java:97) > at java.io.ObjectInputStream.readObject(ObjectInputStream.java:365) > at org.teiid.net.socket.OioOjbectChannelFactory$OioObjectChannel.read(OioOjbectChannelFactory.java:117) > at org.teiid.net.socket.SocketServerInstanceImpl.doHandshake(SocketServerInstanceImpl.java:128) > at org.teiid.net.socket.SocketServerInstanceImpl.connect(SocketServerInstanceImpl.java:96) > at org.teiid.net.socket.SocketServerConnectionFactory.getServerInstance(SocketServerConnectionFactory.java:277) > at org.teiid.net.socket.SocketServerConnection.connect(SocketServerConnection.java:239) > at org.teiid.net.socket.SocketServerConnection.selectServerInstance(SocketServerConnection.java:125) > ... 14 more > {code} > I have tried several combinations: > |client|server|result| > |JVM 1.6| JVM 1.6|fail| > |JVM 1.8| JVM 1.6|fail| > |JVM 1.6| JVM 1.8|OK| -- 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 July 2016