September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3128) Issue while querying Salesforce.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3128?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3128. ----------------------------------- Resolution: Done Moved the inner join handling into the translator. This will then appropriately handle both the parent to child (converted to child to parent) and child to parent to cases. > Issue while querying Salesforce. > --------------------------------- > > Key: TEIID-3128 > URL: https://issues.jboss.org/browse/TEIID-3128 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.4 > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 8.9 > > > (I am using Teiid Embedded 8.8.0.Final) > Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 > Steps to reproduce at my end: > 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. > 2) Execute the queries as shown in the steps below > 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) > -Changing the order of the From part makes it run fine -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3128) Issue while querying Salesforce.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3128?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3128: ---------------------------------- Summary: Issue while querying Salesforce. (was: Issue while querying Salesforce using Teiid embedded. ) Fix Version/s: 8.9 Steps to Reproduce: Steps to reproduce at my end: 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. 2) Execute the queries as shown in the steps below 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) -Changing the order of the From part makes it run fine was: Steps to reproduce at my end: 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. 2) Execute the queries as shown in the steps below 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) -Changing the order of the From part makes it run fine Affects Version/s: 8.4 Component/s: Salesforce Connector Forum Reference: https://developer.jboss.org/thread/248796 > Issue while querying Salesforce. > --------------------------------- > > Key: TEIID-3128 > URL: https://issues.jboss.org/browse/TEIID-3128 > Project: Teiid > Issue Type: Bug > Components: Salesforce Connector > Affects Versions: 8.4 > Reporter: Pranav K > Assignee: Steven Hawkins > Fix For: 8.9 > > > (I am using Teiid Embedded 8.8.0.Final) > Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 > Steps to reproduce at my end: > 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. > 2) Execute the queries as shown in the steps below > 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) > -Changing the order of the From part makes it run fine -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3120) honor javax.sql.DataSource LoginTimeout

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3120?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3120. ----------------------------------- Fix Version/s: 8.9 Resolution: Done Added support for the DataSource loginTimeout via a new driver property loginTimeout, which is the time in seconds before we'll an exception will be thrown on connecting. This is based upon checking a timeout value when a socket timeout occurs, so it is dependent upon the soTimeout rather than on another thread to explicitly interrupt. The soTimeout default was changed to 1000 (rather than 3000 / 3 seconds) so that it's resolution will roughly correspond to the second interval of login timeout. We can introduce usage of the Statement enhanced timer if we want to allow shorter timeouts and/or more precise control over when they occur via an interrupt. Also the handshake retries were modified to instead be based upon the synch ttl rather than being hard coded - but that has the effect of lengthening the handshake timeout from the current default of effectively 30 seconds to 240 seconds. However since users can now set the login timeout that is a more effective value to control that behavior rather than tuning soTimeout / synch ttl. > honor javax.sql.DataSource LoginTimeout > --------------------------------------- > > Key: TEIID-3120 > URL: https://issues.jboss.org/browse/TEIID-3120 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 8.4.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.9 > > > setLoginTimeout is currently not honored. > Modify [1] to generate a reproducer. Use [2] in order to simulate an unresponsive Teiid instance. > > [1] > https://github.com/teiid/teiid-quickstarts/tree/8.4.x/simpleclient > add ds.setLoginTimeout(1) to JDBCClient.getDataSourceConnection > [2] > sudo iptables -I INPUT 1 -m state --state NEW -m tcp -p tcp --dport 31000 -j DROP -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3070) Netty worker threads cause system high cpu

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3070?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3070: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1134393, https://bugzilla.redhat.com/show_bug.cgi?id=1141826 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1134393) > Netty worker threads cause system high cpu > ------------------------------------------ > > Key: TEIID-3070 > URL: https://issues.jboss.org/browse/TEIID-3070 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7 > Environment: JDV 6.1.0.DR2 > JDV 6.0 > Reporter: Kylin Soong > Assignee: Kylin Soong > > I have hit this issue many times in deploying a VDB to JDV, All CPU be used by netty worker threads: > ~~~ > "New I/O worker #3" daemon prio=10 tid=0x00007fc71c0d2000 nid=0x320b runnable [0x00007fc7074f3000] > java.lang.Thread.State: RUNNABLE > at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method) > at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269) > at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:79) > at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:87) > - locked <0x00000000c42b4318> (a sun.nio.ch.Util$2) > - locked <0x00000000c42b4328> (a java.util.Collections$UnmodifiableSet) > - locked <0x00000000c42b42d0> (a sun.nio.ch.EPollSelectorImpl) > at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:98) > at org.jboss.netty.channel.socket.nio.SelectorUtil.select(SelectorUtil.java:64) > ~~~ > Seems this is a exist netty issue, search "jboss netty high cpu" via google we can get lots of result. > Below link have detailed depiction about this issue; > https://github.com/kylinsoong/teiid-samples/tree/master/highcpu -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3128) Issue while querying Salesforce using Teiid embedded.

by Pranav K (JIRA)

[ https://issues.jboss.org/browse/TEIID-3128?page=com.atlassian.jira.plugin... ] Pranav K updated TEIID-3128: ---------------------------- Description: (I am using Teiid Embedded 8.8.0.Final) Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 Steps to reproduce at my end: 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. 2) Execute the queries as shown in the steps below 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) -Changing the order of the From part makes it run fine was: Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 Steps to reproduce at my end: 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. 2) Execute the queries as shown in the steps below 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) -Changing the order of the From part makes it run fine > Issue while querying Salesforce using Teiid embedded. > ------------------------------------------------------ > > Key: TEIID-3128 > URL: https://issues.jboss.org/browse/TEIID-3128 > Project: Teiid > Issue Type: Bug > Reporter: Pranav K > Assignee: Steven Hawkins > > (I am using Teiid Embedded 8.8.0.Final) > Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 > Steps to reproduce at my end: > 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. > 2) Execute the queries as shown in the steps below > 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) > -Changing the order of the From part makes it run fine -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3128) Issue while querying Salesforce using Teiid embedded.

by Pranav K (JIRA)

Pranav K created TEIID-3128: ------------------------------- Summary: Issue while querying Salesforce using Teiid embedded. Key: TEIID-3128 URL: https://issues.jboss.org/browse/TEIID-3128 Project: Teiid Issue Type: Bug Reporter: Pranav K Assignee: Steven Hawkins Please refer to this forum thread for exact analysis/details: https://developer.jboss.org/thread/248796 Steps to reproduce at my end: 1) Use tables Account and Contact where AccountId in Contact is the child field for Id in Account. 2) Execute the queries as shown in the steps below 3)Execute the query: SELECT Account.Phone, Account.Name, Account.Type, Contact.LastName FROM Account, Contact WHERE Account.Id = Contact.AccountId (GIVES ERROR) -Changing the order of the From part makes it run fine -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

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

by Ivan Chan (JIRA)

[ https://issues.jboss.org/browse/TEIID-2848?page=com.atlassian.jira.plugin... ] Ivan Chan commented on TEIID-2848: ---------------------------------- Would the fix be included in 8.9? If so, when is the target release date for 8.9? Thanks. > 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 > Labels: CR1 > Fix For: 8.8, 8.7.1 > > > 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 was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3120) honor javax.sql.DataSource LoginTimeout

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3120?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3120: --------------------------------------- This is slightly involved to implement as our connection logic is a series of calls and can involve failover. It will probably take about a days effort to get something in. > honor javax.sql.DataSource LoginTimeout > --------------------------------------- > > Key: TEIID-3120 > URL: https://issues.jboss.org/browse/TEIID-3120 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver > Affects Versions: 8.4.2 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > > setLoginTimeout is currently not honored. > Modify [1] to generate a reproducer. Use [2] in order to simulate an unresponsive Teiid instance. > > [1] > https://github.com/teiid/teiid-quickstarts/tree/8.4.x/simpleclient > add ds.setLoginTimeout(1) to JDBCClient.getDataSourceConnection > [2] > sudo iptables -I INPUT 1 -m state --state NEW -m tcp -p tcp --dport 31000 -j DROP -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3127) Multiple subquery arguments prevent plan completion

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3127?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3127. ----------------------------------- Resolution: Done Saved the values for the parameters and elevated the scope of the evaluator closure to push/pop of a program. > Multiple subquery arguments prevent plan completion > --------------------------------------------------- > > Key: TEIID-3127 > URL: https://issues.jboss.org/browse/TEIID-3127 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The evaluator is closed after each successful evaluation, but the values are not saved so multiple subqueries in the same logical operation will cause indefinite blocking. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3127) Multiple subquery arguments prevent plan completion

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3127: ------------------------------------- Summary: Multiple subquery arguments prevent plan completion Key: TEIID-3127 URL: https://issues.jboss.org/browse/TEIID-3127 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.9 The evaluator is closed after each successful evaluation, but the values are not saved so multiple subqueries in the same logical operation will cause indefinite blocking. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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