[JBoss JIRA] (TEIID-3929) Accumulo does not return null values
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3929?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-3929.
---------------------------------
> 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)
8 years, 6 months
[JBoss JIRA] (TEIID-4258) Cannot connect to Teiid if server runs on JVM 1.6
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4258?page=com.atlassian.jira.plugin... ]
Steven Hawkins closed TEIID-4258.
---------------------------------
> 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
> Components: Server
> 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)
8 years, 6 months
[JBoss JIRA] (TEIID-4258) Cannot connect to Teiid if server runs on JVM 1.6
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-4258?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-4258:
----------------------------------
Component/s: Server
> 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
> Components: Server
> 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)
8 years, 6 months
[JBoss JIRA] (TEIID-3946) Version negotiation in JDBC connection
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-3946?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration updated TEIID-3946:
-------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1303496
Bugzilla Update: Perform
> Version negotiation in JDBC connection
> --------------------------------------
>
> Key: TEIID-3946
> URL: https://issues.jboss.org/browse/TEIID-3946
> Project: Teiid
> Issue Type: Feature Request
> Components: JDBC Driver
> Affects Versions: 8.7.4
> Environment: - JDV 6.2
> Reporter: Hisanobu Okuda
> Assignee: Steven Hawkins
> Priority: Minor
>
> Our customer is providing a service on top of JDV and some of the external clients are still using outdated teiid drivers and wants something they can make for JDV to block a connection if the JDBC Driver used in a client is outdated. This scenario occurs everytime the customer updates JDV. Since there are so much external clients, some of them don't update their JDBC Drivers and this leads to some errors in JDV.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 6 months
[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ]
Ramesh Reddy edited comment on TEIID-4311 at 7/1/16 10:42 AM:
--------------------------------------------------------------
This may NOT be straight forward as others. To find out a JDBC driver supports the XA connection, on the call
{code}
[standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list
{
"outcome" => "success",
"result" => [
{
"driver-name" => "teiid-local",
"deployment-name" => undefined,
"driver-module-name" => "org.jboss.teiid",
"module-slot" => "main",
"driver-datasource-class-name" => "",
"driver-xa-datasource-class-name" => "org.teiid.jdbc.TeiidDataSource",
"driver-class-name" => "org.teiid.jdbc.TeiidDriver",
"driver-major-version" => 8,
"driver-minor-version" => 12,
"jdbc-compliant" => false
}
}
{code}
You need to make sure "driver-xa-datasource-class-name" property exists with valid name. Now based on this, we need to introduce an extra template name with "xa-" as post fix
The template definition properties for this "xa" template, we need to add three extra properties
{code}
ServerName
PortNumber
DatabaseName
{code}
Now, when a user calls "createDatasource", with this new template you will know it is XA connection based on template name or an extra property in it. Now coming down to setting "xa-datasource-properties", there is property called "connection-properties" you need to use that. See, how this is used in the driver creation, we need to re-purpose this property.
As these require multiple executions run them in batch.
was (Author: rareddy):
This may be straight forward as others. To find out a JDBC driver supports the XA connection, on the call
{code}
[standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list
{
"outcome" => "success",
"result" => [
{
"driver-name" => "teiid-local",
"deployment-name" => undefined,
"driver-module-name" => "org.jboss.teiid",
"module-slot" => "main",
"driver-datasource-class-name" => "",
"driver-xa-datasource-class-name" => "org.teiid.jdbc.TeiidDataSource",
"driver-class-name" => "org.teiid.jdbc.TeiidDriver",
"driver-major-version" => 8,
"driver-minor-version" => 12,
"jdbc-compliant" => false
}
}
{code}
You need to make sure "driver-xa-datasource-class-name" property exists with valid name. Now based on this, we need to introduce an extra template name with "xa-" as post fix
The template definition properties for this "xa" template, we need to add three extra properties
{code}
ServerName
PortNumber
DatabaseName
{code}
Now, when a user calls "createDatasource", with this new template you will know it is XA connection based on template name or an extra property in it. Now coming down to setting "xa-datasource-properties", there is property called "connection-properties" you need to use that. See, how this is used in the driver creation, we need to re-purpose this property.
As these require multiple executions run them in batch.
> 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)
8 years, 6 months
[JBoss JIRA] (TEIID-4311) Teiid Admin Api not support to create XA datasource on Jboss server.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-4311?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-4311:
-------------------------------------
This may be straight forward as others. To find out a JDBC driver supports the XA connection, on the call
{code}
[standalone@localhost:9999 /] /subsystem=datasources:installed-drivers-list
{
"outcome" => "success",
"result" => [
{
"driver-name" => "teiid-local",
"deployment-name" => undefined,
"driver-module-name" => "org.jboss.teiid",
"module-slot" => "main",
"driver-datasource-class-name" => "",
"driver-xa-datasource-class-name" => "org.teiid.jdbc.TeiidDataSource",
"driver-class-name" => "org.teiid.jdbc.TeiidDriver",
"driver-major-version" => 8,
"driver-minor-version" => 12,
"jdbc-compliant" => false
}
}
{code}
You need to make sure "driver-xa-datasource-class-name" property exists with valid name. Now based on this, we need to introduce an extra template name with "xa-" as post fix
The template definition properties for this "xa" template, we need to add three extra properties
{code}
ServerName
PortNumber
DatabaseName
{code}
Now, when a user calls "createDatasource", with this new template you will know it is XA connection based on template name or an extra property in it. Now coming down to setting "xa-datasource-properties", there is property called "connection-properties" you need to use that. See, how this is used in the driver creation, we need to re-purpose this property.
As these require multiple executions run them in batch.
> 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)
8 years, 6 months
[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 updated TEIID-3635:
---------------------------------
Fix Version/s: 8.7.8.6_2
> 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, 8.7.8.6_2
>
>
> 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)
8 years, 6 months
[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 closed TEIID-3635.
--------------------------------
Resolution: Done
> 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.7.8.6_2, 8.7.5, 8.11.3, 8.12
>
>
> 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)
8 years, 6 months
[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)
8 years, 6 months