November 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3803) Kerberos with ODBC with MutualAuth fails

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-3803: ----------------------------------- Summary: Kerberos with ODBC with MutualAuth fails Key: TEIID-3803 URL: https://issues.jboss.org/browse/TEIID-3803 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.4 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.12.x When Active Directory is used for Kerberos authentication, and Windows ODBC client issues connection request it may fail with following exception. {code} 00:29:15,561 ERROR [org.teiid.ODBC] (New I/O worker #19) TEIID40015 Unexpected error occurred: org.teiid.client.security.LogonException: TEIID40014 Kerberos context login failed at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:203) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.odbc.ODBCServerRemoteImpl.logon(ODBCServerRemoteImpl.java:236) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.7.0_79] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) [rt.jar:1.7.0_79] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.7.0_79] at java.lang.reflect.Method.invoke(Method.java:606) [rt.jar:1.7.0_79] at org.teiid.transport.ODBCClientInstance.processMessage(ODBCClientInstance.java:127) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.transport.ODBCClientInstance.receivedMessage(ODBCClientInstance.java:116) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.transport.SSLAwareChannelHandler.messageReceived(SSLAwareChannelHandler.java:211) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.jboss.netty.channel.SimpleChannelHandler.handleUpstream(SimpleChannelHandler.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:296) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.handler.codec.frame.FrameDecoder.unfoldAndFireMessageReceived(FrameDecoder.java:462) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:443) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:310) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:559) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:109) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:328) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:90) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at org.jboss.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42) [netty-3.6.10.Final-redhat-1.jar:3.6.10.Final-redhat-1] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_79] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_79] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_79] Caused by: javax.security.auth.login.LoginException: TEIID50103 Wrong Response returned from teiid-security security domain; Expecting a Kerberoes response at org.teiid.jboss.JBossSessionService.buildGSSResult(JBossSessionService.java:138) [teiid-jboss-integration-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.jboss.JBossSessionService.neogitiateGssLogin(JBossSessionService.java:106) [teiid-jboss-integration-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.services.SessionServiceImpl.neogitiateGssLogin(SessionServiceImpl.java:545) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] at org.teiid.transport.LogonImpl.neogitiateGssLogin(LogonImpl.java:173) [teiid-runtime-8.7.4.redhat-1.jar:8.7.4.redhat-1] ... 30 more {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3802) HANA translator modifies boolean to tinyint in type conversion

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3802?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3802: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1278409 Bugzilla Update: Perform > HANA translator modifies boolean to tinyint in type conversion > -------------------------------------------------------------- > > Key: TEIID-3802 > URL: https://issues.jboss.org/browse/TEIID-3802 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.7.1.6_2 > Reporter: Jan Stastny > Assignee: Steven Hawkins > > Teiid modifies boolean data type to tinyint before pushing the query down to the HANA instance. > This brings following issue while having a query similar to this one: > {code:sql} > SELECT BQT1.SMallA.BooleanValue,cast(BQT2.SmallB.CharValue as boolean) FROM BQT1.SmallA,BQT2.SmallB WHERE BQT1.SmallA.BooleanValue = cast(BQT2.SmallB.CharValue as boolean) > {code} > which Teiid modifies to: > {code:sql} > SELECT g_0."BOOLEANVALUE", cast(g_1."CHARVALUE" AS tinyint) FROM "BQT1"."SMALLA" AS g_0, "BQT2"."SMALLB" AS g_1 WHERE g_0."BOOLEANVALUE" = cast(g_1."CHARVALUE" AS tinyint) > {code} > But the problem is not present for: > {code:sql} > SELECT BQT1.SMallA.BooleanValue FROM BQT1.SmallA WHERE BQT1.SmallA.BooleanValue = cast(BQT1.SmallA.CharValue as boolean) > {code} > It seems that the Cartesian product and comparing values from different sources are the cause of the issue. But HANA has internal type BOOLEAN, so there might be no point at modifying the type to TINYINT after all. I also checked, that the pushed query (which causes the issue) with the casting altered to BOOLEAN runs well on HANA. The following query returns expected results when pushed directly to HANA instance: > {code:sql} > SELECT g_0."BOOLEANVALUE", cast(g_1."CHARVALUE" AS boolean) FROM "BQT1"."SMALLA" AS g_0, "BQT2"."SMALLB" AS g_1 WHERE g_0."BOOLEANVALUE" = cast(g_1."CHARVALUE" AS boolean) > {code} > NOTE: The CharValue columns are modelled as VARCHAR/string in fact. Thus the cast is a valid operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3802) HANA translator modifies boolean to tinyint in type conversion

by Jan Stastny (JIRA)

Jan Stastny created TEIID-3802: ---------------------------------- Summary: HANA translator modifies boolean to tinyint in type conversion Key: TEIID-3802 URL: https://issues.jboss.org/browse/TEIID-3802 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 8.7.1.6_2 Reporter: Jan Stastny Assignee: Steven Hawkins Teiid modifies boolean data type to tinyint before pushing the query down to the HANA instance. This brings following issue while having a query similar to this one: {code:sql} SELECT BQT1.SMallA.BooleanValue,cast(BQT2.SmallB.CharValue as boolean) FROM BQT1.SmallA,BQT2.SmallB WHERE BQT1.SmallA.BooleanValue = cast(BQT2.SmallB.CharValue as boolean) {code} which Teiid modifies to: {code:sql} SELECT g_0."BOOLEANVALUE", cast(g_1."CHARVALUE" AS tinyint) FROM "BQT1"."SMALLA" AS g_0, "BQT2"."SMALLB" AS g_1 WHERE g_0."BOOLEANVALUE" = cast(g_1."CHARVALUE" AS tinyint) {code} But the problem is not present for: {code:sql} SELECT BQT1.SMallA.BooleanValue FROM BQT1.SmallA WHERE BQT1.SmallA.BooleanValue = cast(BQT1.SmallA.CharValue as boolean) {code} It seems that the Cartesian product and comparing values from different sources are the cause of the issue. But HANA has internal type BOOLEAN, so there might be no point at modifying the type to TINYINT after all. I also checked, that the pushed query (which causes the issue) with the casting altered to BOOLEAN runs well on HANA. The following query returns expected results when pushed directly to HANA instance: {code:sql} SELECT g_0."BOOLEANVALUE", cast(g_1."CHARVALUE" AS boolean) FROM "BQT1"."SMALLA" AS g_0, "BQT2"."SMALLB" AS g_1 WHERE g_0."BOOLEANVALUE" = cast(g_1."CHARVALUE" AS boolean) {code} NOTE: The CharValue columns are modelled as VARCHAR/string in fact. Thus the cast is a valid operation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

Van Halbert created TEIID-3801: ---------------------------------- Summary: Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) Key: TEIID-3801 URL: https://issues.jboss.org/browse/TEIID-3801 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 9.x, 8.12.x Reporter: Van Halbert Assignee: Steven Hawkins Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3801) Upgrade Infinispan translator to support 6.4.x version (JDG 6.6)

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3801?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-3801: ---------------------------------- Assignee: Van Halbert (was: Steven Hawkins) > Upgrade Infinispan translator to support 6.4.x version (JDG 6.6) > ---------------------------------------------------------------- > > Key: TEIID-3801 > URL: https://issues.jboss.org/browse/TEIID-3801 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 9.x, 8.12.x > Reporter: Van Halbert > Assignee: Van Halbert > > Upgrade Infinispan translator to support version 6.4 (JDG 6.6). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3792) Add support for searching in array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3792?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3792: ---------------------------------- Fix Version/s: 9.0 (was: 8.12.2) After looking this over I'm moving to 9.0. The array_iterate logic isn't a much larger change than adding a new system function and could be backported for this functionality in older branches. For 9.0 I'll add the quantified comparison syntax support to simplify this. > Add support for searching in array types > ---------------------------------------- > > Key: TEIID-3792 > URL: https://issues.jboss.org/browse/TEIID-3792 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 9.0 > > > We should support a simple syntax for searching within an array, such as the quantified comparison and/or a function to get the index of a value in an array. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3792) Add support for searching in array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3792?page=com.atlassian.jira.plugin... ] Work on TEIID-3792 started by Steven Hawkins. --------------------------------------------- > Add support for searching in array types > ---------------------------------------- > > Key: TEIID-3792 > URL: https://issues.jboss.org/browse/TEIID-3792 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > We should support a simple syntax for searching within an array, such as the quantified comparison and/or a function to get the index of a value in an array. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3581) Add a system function to return Teiid Server Name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3581?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3581: --------------------------------------- The workaround for this is to allow the env function and call env('jboss.node.name'). With 8.12.2 there will be a node_id system function that will return the jboss.node.name property value. The docs were updated as well. > Add a system function to return Teiid Server Name > ------------------------------------------------- > > Key: TEIID-3581 > URL: https://issues.jboss.org/browse/TEIID-3581 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Fix For: 8.12.2 > > > A user has a 4 node Cluster and would like to get not only the sessionid, vdb and user but the node of the cluster that the user is connected to -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3581) Add a system function to return Teiid Server Name

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3581?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3581. ----------------------------------- Assignee: Steven Hawkins Resolution: Done > Add a system function to return Teiid Server Name > ------------------------------------------------- > > Key: TEIID-3581 > URL: https://issues.jboss.org/browse/TEIID-3581 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Van Halbert > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > A user has a 4 node Cluster and would like to get not only the sessionid, vdb and user but the node of the cluster that the user is connected to -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3792) Add support for searching in array types

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3792?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3792: ---------------------------------- Fix Version/s: 8.12.2 (was: 8.12.x) > Add support for searching in array types > ---------------------------------------- > > Key: TEIID-3792 > URL: https://issues.jboss.org/browse/TEIID-3792 > Project: Teiid > Issue Type: Feature Request > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12.2 > > > We should support a simple syntax for searching within an array, such as the quantified comparison and/or a function to get the index of a value in an array. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 November 2015