August 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2355) BigQuery integration

by Masilamani Subramanyam (JIRA)

[ https://issues.jboss.org/browse/TEIID-2355?page=com.atlassian.jira.plugin... ] Masilamani Subramanyam commented on TEIID-2355: ----------------------------------------------- I am trying to access BigQuery using Teiid with starsschema-bigquery-jdbc driver bqjdbc-1.4.jar but it's not working in teiid. Interesting is that it works fine when i try to access using SQuirrel SQL client. Just wondering whether anyone from teiid community tried already to connect and query successfully using starsschema-bigquery-jdbc driver ? > BigQuery integration > -------------------- > > Key: TEIID-2355 > URL: https://issues.jboss.org/browse/TEIID-2355 > Project: Teiid > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Misc. Connectors > Reporter: Steven Hawkins > Assignee: Kylin Soong > Fix For: Open To Community > > > http://code.google.com/p/starschema-bigquery-jdbc/ looks promising for simple support of BigQuery. Some of the dependencies could already be in the google-api module. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1910) Teiid support for EclipseLink persistance provider

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-1910?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-1910: ------------------------------------- We should do same thing as hibernate jar > Teiid support for EclipseLink persistance provider > -------------------------------------------------- > > Key: TEIID-1910 > URL: https://issues.jboss.org/browse/TEIID-1910 > Project: Teiid > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.0 > Reporter: Sunil Varma > Assignee: Kylin Soong > Fix For: Open To Community > > > We need a dialect support for Eclipselink similar to the one done for HIbernate. > See thread:https://community.jboss.org/thread/176306 > op -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-1910) Teiid support for EclipseLink persistance provider

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-1910?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-1910: --------------------------------------- The pull request has been committed. We should add a note about usage in the Client Developers Guide. Is there anything else we want to do for packaging besides availability in maven? > Teiid support for EclipseLink persistance provider > -------------------------------------------------- > > Key: TEIID-1910 > URL: https://issues.jboss.org/browse/TEIID-1910 > Project: Teiid > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Query Engine > Affects Versions: 8.0 > Reporter: Sunil Varma > Assignee: Kylin Soong > Fix For: Open To Community > > > We need a dialect support for Eclipselink similar to the one done for HIbernate. > See thread:https://community.jboss.org/thread/176306 > op -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2875) Metadata failed to load. No column found

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2875?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2875. ----------------------------------- Resolution: Incomplete Description Updated the logging to include the exception, and resolving as incomplete description as it's not clear what is happening. > Metadata failed to load. No column found > ---------------------------------------- > > Key: TEIID-2875 > URL: https://issues.jboss.org/browse/TEIID-2875 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 8.6 > Environment: Windows server 2003, Windows 7. > Reporter: SHI HONG CHIN > Assignee: Steven Hawkins > Attachments: JakkerData-vdb.xml > > > Affected database: Oracle > The following error displayed when Teiid loading a dynamic VDB: > 10:21:41,458 WARN [org.teiid.RUNTIME] (teiid-async-threads - 2) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > 10:23:29,994 WARN [org.teiid.RUNTIME] (teiid-async-threads - 4) TEIID50036 VDB JakkerData.1 model "IWMS" metadata failed to load. Reason:TEIID60011 No column found with name "RATE"."CHARGE_NAME" > I am not the one who design the database. But, I cannot find any table with above mentioned column name in Oracle database. So, I am not sure whether the above mentioned column name is a hidden column or not. > This bug does not exist in version 8.5. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 resolved TEIID-2835. ----------------------------------- Resolution: Out of Date > 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 > Security Level: Public(Everyone can see) > 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 was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2835?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2835: ------------------------------------ This can be closed, because I can't reproduce it using the latest. > 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 > Security Level: Public(Everyone can see) > 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 was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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: --------------------------------------- Any updates here or can this be resolved? > 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 > Security Level: Public(Everyone can see) > 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 was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2941) Add documentation that explains expected usage patterns

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2941?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2941: ---------------------------------- Assignee: (was: Steven Hawkins) > Add documentation that explains expected usage patterns > ------------------------------------------------------- > > Key: TEIID-2941 > URL: https://issues.jboss.org/browse/TEIID-2941 > Project: Teiid > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: Documentation > Reporter: Van Halbert > Priority: Optional > > Would like to see documentation added to explains certain data source usage patterns for which cannot be explained just by using the data source. Example is: > How to access a JSON REST service: > You read JSON using file or web service translator, then use the JSONToXML function, to convert to XML, then use the XMLTABLE function to parse. > This isn't straight forward in the documentation to a novice. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3097) Model names should not be allowed to contain .

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3097?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3097. ----------------------------------- Resolution: Done Added a validation before metadata is loaded. > Model names should not be allowed to contain . > ---------------------------------------------- > > Key: TEIID-3097 > URL: https://issues.jboss.org/browse/TEIID-3097 > Project: Teiid > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The server should not allow model names to contain a . as that is not allowed by our resolving conventions. This has been enforced in designer, but is not yet validated on the runtime side. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3097) Model names should not be allowed to contain .

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3097: ------------------------------------- Summary: Model names should not be allowed to contain . Key: TEIID-3097 URL: https://issues.jboss.org/browse/TEIID-3097 Project: Teiid Issue Type: Bug Security Level: Public (Everyone can see) Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.9 The server should not allow model names to contain a . as that is not allowed by our resolving conventions. This has been enforced in designer, but is not yet validated on the runtime side. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 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 August 2014