February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2458) Sybase15 subquery using HAVING clause failing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2458?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2458: ------------------------------------------------ David Le Sage <dlesage(a)redhat.com> changed the Status of [bug 996550|https://bugzilla.redhat.com/show_bug.cgi?id=996550] from VERIFIED to CLOSED > Sybase15 subquery using HAVING clause failing > --------------------------------------------- > > Key: TEIID-2458 > URL: https://issues.jboss.org/browse/TEIID-2458 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 7.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Example query is failing: SELECT INTKEY, STRINGKEY, FLOATNUM FROM BQT1.SMALLA GROUP BY INTKEY, STRINGKEY, FLOATNUM HAVING FLOATNUM = (SELECT FLOATNUM FROM BQT1.SMALLA WHERE STRINGKEY = 20) > When this query is submitted through EDS using Squirrel or BQT as a client it returns: > IntKey StringKey > 20 20 0 > When the resulting source-specific query generated from EDS is submitted direct to Sybase15 the same results are returned. > SELECT g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real) FROM SmallA g_0 WHERE cast(g_0.FloatNum AS real) = (SELECT cast(g_1.FloatNum AS real) FROM SmallA g_1 WHERE g_1.StringKey = '20') GROUP BY g_0.IntKey, g_0.StringKey, cast(g_0.FloatNum AS real)is submitted direct to Sybase15 > RESULTS > IntKey StringKey > 20 20 0 > However, when the GROUP BY is removed from the query it returns the expected results as shown below: > IntKey StringKey > 20 20 -4 > The supporting VDB can be provided if needed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2835: --------------------------------------- That exception is an expected by-product of a test - note that should not be a test failure. There is no change that should be to SSLAwareChannelHandler related to sizing. Is your issue that it is being logged as severe? > After switch to use io.netty, getting exception in TestJDBCSocketTransport > -------------------------------------------------------------------------- > > Key: TEIID-2835 > URL: https://issues.jboss.org/browse/TEIID-2835 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: Running build on mac > Reporter: Van Halbert > Assignee: Steven Hawkins > > When building off of master (which I see there's been a change to io.netty), I get the following error: > Running org.teiid.transport.TestJDBCSocketTransport > Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log > SEVERE: TEIID40113 Unhandled exception, aborting operation > org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405) > at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320) > at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108) > at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) > at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) > at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) > at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) > at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) > at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) > at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with: > =========== DEFAULT ===========2097152 > =========== Int Max ===========2147483647 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2835) After switch to use io.netty, getting exception in TestJDBCSocketTransport

by Van Halbert (JIRA)

Van Halbert created TEIID-2835: ---------------------------------- Summary: After switch to use io.netty, getting exception in TestJDBCSocketTransport Key: TEIID-2835 URL: https://issues.jboss.org/browse/TEIID-2835 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.7 Environment: Running build on mac Reporter: Van Halbert Assignee: Steven Hawkins When building off of master (which I see there's been a change to io.netty), I get the following error: Running org.teiid.transport.TestJDBCSocketTransport Feb 3, 2014 2:51:12 PM org.teiid.logging.JavaLogger log SEVERE: TEIID40113 Unhandled exception, aborting operation org.jboss.netty.handler.codec.frame.TooLongFrameException: Adjusted frame length exceeds 100000: 100293 - discarded at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.fail(LengthFieldBasedFrameDecoder.java:417) at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.failIfNecessary(LengthFieldBasedFrameDecoder.java:405) at org.jboss.netty.handler.codec.frame.LengthFieldBasedFrameDecoder.decode(LengthFieldBasedFrameDecoder.java:320) at org.teiid.transport.ObjectDecoder.decode(ObjectDecoder.java:108) at org.jboss.netty.handler.codec.frame.FrameDecoder.callDecode(FrameDecoder.java:425) at org.jboss.netty.handler.codec.frame.FrameDecoder.messageReceived(FrameDecoder.java:303) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:268) at org.jboss.netty.channel.Channels.fireMessageReceived(Channels.java:255) at org.jboss.netty.channel.socket.nio.NioWorker.read(NioWorker.java:88) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.process(AbstractNioWorker.java:107) at org.jboss.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:312) at org.jboss.netty.channel.socket.nio.AbstractNioWorker.run(AbstractNioWorker.java:88) at org.jboss.netty.channel.socket.nio.NioWorker.run(NioWorker.java:178) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:695) I made a change to SSLAwareChannelHandler to increase the estimated decoder size to Integer.MAX_VALUE and the problem was gone. Here's the difference in size estimates based on what the default was using and the MAX_VALUE I tested with: =========== DEFAULT ===========2097152 =========== Int Max ===========2147483647 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2803) Provide SAML support for OData Transport

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2803?page=com.atlassian.jira.plugin... ] Ramesh Reddy updated TEIID-2803: -------------------------------- Attachment: sales-metadata.war.tar.gz > Provide SAML support for OData Transport > ---------------------------------------- > > Key: TEIID-2803 > URL: https://issues.jboss.org/browse/TEIID-2803 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7 > > Attachments: sales-metadata.war.tar.gz > > > Provide SAML based security authentication support for OData transport. Provide a capability for user to configure their own STS provider. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2803) Provide SAML support for OData Transport

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2803?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2803. --------------------------------- Resolution: Done I was finally able to configure Shibboleth IDP with Picketlink as SP. Attaching zips for future reference. Based on above I added instructions on how one could configure OData WAR in Teiid with SAML base security. https://docs.jboss.org/author/display/TEIID/SAML+Based+Security+For+OData > Provide SAML support for OData Transport > ---------------------------------------- > > Key: TEIID-2803 > URL: https://issues.jboss.org/browse/TEIID-2803 > Project: Teiid > Issue Type: Feature Request > Components: OData > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.7 > > > Provide SAML based security authentication support for OData transport. Provide a capability for user to configure their own STS provider. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2826: --------------------------------------- Built on the pull request to simplify the main assembly. It will now just unzip all of the project module zips. One possible modification to the base logic is that the jar inclusion: {code} <fileSet> <directory>target</directory> <outputDirectory>org/jboss/teiid/translator/google/main</outputDirectory> <includes> <include>translator-google-${project.version}.jar</include> </includes> </fileSet> {code} could also be done as a dependencyset. > Change build to use zip translator packaging when building jboss kit > -------------------------------------------------------------------- > > Key: TEIID-2826 > URL: https://issues.jboss.org/browse/TEIID-2826 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Change build to use zip translator packaging when building jboss kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ] Work on TEIID-2826 stopped by Van Halbert. > Change build to use zip translator packaging when building jboss kit > -------------------------------------------------------------------- > > Key: TEIID-2826 > URL: https://issues.jboss.org/browse/TEIID-2826 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Change build to use zip translator packaging when building jboss kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ] Van Halbert reassigned TEIID-2826: ---------------------------------- Assignee: Steven Hawkins (was: Van Halbert) > Change build to use zip translator packaging when building jboss kit > -------------------------------------------------------------------- > > Key: TEIID-2826 > URL: https://issues.jboss.org/browse/TEIID-2826 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Steven Hawkins > > Change build to use zip translator packaging when building jboss kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2826) Change build to use zip translator packaging when building jboss kit

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2826?page=com.atlassian.jira.plugin... ] Work on TEIID-2826 started by Van Halbert. > Change build to use zip translator packaging when building jboss kit > -------------------------------------------------------------------- > > Key: TEIID-2826 > URL: https://issues.jboss.org/browse/TEIID-2826 > Project: Teiid > Issue Type: Sub-task > Components: Build/Kits > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Change build to use zip translator packaging when building jboss kit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014