February 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2660) OData procedure issues

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2660?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2660: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 1006961|https://bugzilla.redhat.com/show_bug.cgi?id=1006961] from ON_QA to VERIFIED > OData procedure issues > ---------------------- > > Key: TEIID-2660 > URL: https://issues.jboss.org/browse/TEIID-2660 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.3 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Priority: Critical > Fix For: 8.4.1, 8.5 > > > Calling a procedure through Teiid's odata interface has several issues. First is that joda time values are passed directly - which the runtime will not be able to convert to analogous Teiid time types. Ultimately this appears as a classcastexception, which is due to logic in the joda time AbstractPartial.compareTo method (which may be reported with an erroneous message and seems odd in general, but is their way of saying the comparison is invalid). > Another is that the logic assumes that the url will be called with the positional ordering of the parameters preserved. We should use named parameters instead. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1979) The RAR should be unbundled when packaged in the jboss kit

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-1979?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-1979: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 868964|https://bugzilla.redhat.com/show_bug.cgi?id=868964] from ON_QA to VERIFIED > The RAR should be unbundled when packaged in the jboss kit > ---------------------------------------------------------- > > Key: TEIID-1979 > URL: https://issues.jboss.org/browse/TEIID-1979 > Project: Teiid > Issue Type: Task > Components: Build/Kits > Reporter: Van Halbert > Assignee: Ramesh Reddy > Labels: Alpha1 > Fix For: 8.4 > > > The RAR file should be unbundled, instead of zipped up, when it is packaged in the jboss kit. This change is being pushed up stream. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2697) Change to use community bom

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2697?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2697: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 1018818|https://bugzilla.redhat.com/show_bug.cgi?id=1018818] from ON_QA to VERIFIED > Change to use community bom > --------------------------- > > Key: TEIID-2697 > URL: https://issues.jboss.org/browse/TEIID-2697 > Project: Teiid > Issue Type: Enhancement > Components: Build/Kits > Affects Versions: 8.4.1 > Reporter: Van Halbert > Assignee: Van Halbert > Fix For: 8.4.1, 8.6 > > > Teiid should import dependencies from the community bom (https://github.com/jboss-integration/jboss-integration-platform-bom/) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2574) HiveMetadata procesor typo in importer property name

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2574?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2574: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 984853|https://bugzilla.redhat.com/show_bug.cgi?id=984853] from ON_QA to VERIFIED > HiveMetadata procesor typo in importer property name > ---------------------------------------------------- > > Key: TEIID-2574 > URL: https://issues.jboss.org/browse/TEIID-2574 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Ramesh Reddy > Priority: Minor > Fix For: 8.4.1, 8.5 > > > HiveMetadatProcessor's method setTrimColumNames should be named setTrimColumnNames > Unfortunately, when the documentation is without typo so when user sets the importer property according to docs, the property is silently not set. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2665) Hive translator pushdown improvements

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2665?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2665: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 1016111|https://bugzilla.redhat.com/show_bug.cgi?id=1016111] from ON_QA to VERIFIED > Hive translator pushdown improvements > ------------------------------------- > > Key: TEIID-2665 > URL: https://issues.jboss.org/browse/TEIID-2665 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Labels: Alpha2 > Fix For: 8.4.1, 8.6 > > > - Hive 0.11 windowing functions: push down > - Native Queries support > - Test multi-source bindings with Hive Partition Tables - each binding to a discrete partition table > - validate that off-heap buffer management can be used with very large data sets from Hadoop/Hive -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2524) Hive metadata import leaves whitespace characters in column names

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2524?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-2524: ------------------------------------------------ Filip Nguyen <fnguyen(a)redhat.com> changed the Status of [bug 1024875|https://bugzilla.redhat.com/show_bug.cgi?id=1024875] from ON_QA to VERIFIED > Hive metadata import leaves whitespace characters in column names > ----------------------------------------------------------------- > > Key: TEIID-2524 > URL: https://issues.jboss.org/browse/TEIID-2524 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Filip Nguyen > Assignee: Steven Hawkins > Labels: 8.4CR2 > Fix For: 8.4 > > > When hive translator starts with the newest Hive it runs "describe" command which returns Hive column names with white spaces. > Maybe just use trim() in HiveMetadataProcessor.java? > String name = rs.getString(1).trim(); -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2849) MongoDB: Provide basic metadata support

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2849: ----------------------------------- Summary: MongoDB: Provide basic metadata support Key: TEIID-2849 URL: https://issues.jboss.org/browse/TEIID-2849 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Affects Versions: 8.7 Reporter: Ramesh Reddy Assignee: Ramesh Reddy Fix For: 8.7 Currently there is no native metadata import support in the MongoDB translator. It was avoided int he first run because there is no good way to interpret the complex document records. This position has not changed, but this enhancement request is to see if it can capture simple documents or top level documents as a starting point to capture and then to improve upon manually using tooling. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2848) MongoDB: Provide Array support

by Ramesh Reddy (JIRA)

Ramesh Reddy created TEIID-2848: ----------------------------------- Summary: MongoDB: Provide Array support Key: TEIID-2848 URL: https://issues.jboss.org/browse/TEIID-2848 Project: Teiid Issue Type: Enhancement Components: Misc. Connectors Reporter: Ramesh Reddy Assignee: Ramesh Reddy Provide array support for primitive data types in MongoDB translator. The arrays are supported but as embedded documents in the one-2-many situation. -- 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, 4 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 commented on TEIID-2826: ------------------------------------ Never mind. When I pulled the latest code, my local file system didn't update correctly. The translator directories were still there. I verified that they shouldn't be and removed them, and all is good. > 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, 4 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: --------------------------------------- Is this reproducible for you? > 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues February 2014