August 2017 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIID-5014 at 8/10/17 5:02 PM: ---------------------------------------------------------------- The problem was with our flush handling. Netty doesn't expect a null message there and was producing an NPE. The logging of those exceptions was bumped up to the debug log. The flush for us is effectively a no op as each write is performing a flush. The docs were also updated to include Ramesh's blog post, but updated to the latest node.js pg api. I should add that it appears that few clients use the flush message. It doesn't seem to appear in the JDBC or ODBC clients, so it's usage by node is uncommon. was (Author: shawkins): The problem was with our flush handling. Netty doesn't expect a null message there and was producing an NPE. The logging of those exceptions was bumped up to the debug log. The flush for us is effectively a no op as each write is performing a flush. The docs were also updated to include Ramesh's blog post, but updated to the latest node.js pg api. > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5014. ----------------------------------- Fix Version/s: 9.2.6 9.3.3 Resolution: Done The problem was with our flush handling. Netty doesn't expect a null message there and was producing an NPE. The logging of those exceptions was bumped up to the debug log. The flush for us is effectively a no op as each write is performing a flush. The docs were also updated to include Ramesh's blog post, but updated to the latest node.js pg api. > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0, 9.2.6, 9.3.3 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Work on TEIID-5014 started by Steven Hawkins. --------------------------------------------- > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Feature Request > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5014) Unable to use parameterized query with node pg module and Teiid/JBoss VDB

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5014?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5014: ---------------------------------- Issue Type: Bug (was: Feature Request) Component/s: ODBC Fix Version/s: 10.0 This appears to still be happening on master. > Unable to use parameterized query with node pg module and Teiid/JBoss VDB > ------------------------------------------------------------------------- > > Key: TEIID-5014 > URL: https://issues.jboss.org/browse/TEIID-5014 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.7.11.6_2 > Environment: Teiid runtime 8.7.11 > JBoss Data Virtualization 6.10 > NodeJS 6.9.4 > node pg 6.4.1 > Mac OSX 10.11.6 > Reporter: Brian M > Assignee: Steven Hawkins > Fix For: 10.0 > > > When using node pg 6.4.1 in a node application to connect to a JBoss VDB with Teiid, we are unable to successfully return data with a parameterized query. > Example from node js application (failure): > client.query("SELECT * FROM records WHERE recordType = $1", ['TYPE1'], function(err, result) { done(); }) > The above code will actually retrieve rows of data, but the connection will be terminated unexpectedly from the JBoss side, thus resulting in a failure. We can confirm though that the parameter is properly inserted into the variable, and rows of data can be retrieved without issue. > Also, we have confirmed that when sending a static query, we are able to successfully return data without JBoss terminating the connection. We found this approach from the Teiid blog: http://teiid.blogspot.com/2013/02/access-teiid-from-nodejs.html > Example from node js application (success): > client.query("SELECT * FROM records WHERE recordType = 'TYPE1'", function(err, result) { done(); }) > Is there something different about a parameterized query vs. a static query that may cause this issue? > Are you aware of other individuals who have successfully used parameterized queries with the node pg module and Teiid/JBoss VDB? > Is it possible that how the ODBC settings for Teiid are configured may have an impact on parameterized queries vs. static queries? > Link: https://teiid.gitbooks.io/documents/content/client-dev/ODBC_Support.html > Thank you so much for all your help! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5013) Google Spreadsheet Data Sources with custom client_id and client_secret

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5013?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5013. ----------------------------------- Fix Version/s: 9.3.3 Resolution: Done Updated the resource adapter to allow for the override of the default client id and secret. The docs were also updated that it is preferred for the user to create their own rather than relying on the default project. > Google Spreadsheet Data Sources with custom client_id and client_secret > ----------------------------------------------------------------------- > > Key: TEIID-5013 > URL: https://issues.jboss.org/browse/TEIID-5013 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.12.x > Environment: JDV6.3 / Teiid 8.12 / Teiid Desinger 10.0.1 > Reporter: Hiroki Daicho > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > When getting an OAuth Refresh Token, it needs to use a fixed client_id and client_secret such as > "217138521084.apps.googleusercontent.com" and "gXQ6-lOkEjE1lVcz7giB4Poy". > Currently, no way to change another client_id/client_secret. > It had better to be able to use the client_id/client_secret from each google account. > - Teiid 8.13 : Getting an OAuth Refresh Token > https://docs.jboss.org/author/display/teiid813final/Google+Spreadsheet+Da... > - Teiid 9.3 : Getting an OAuth Refresh Token > https://teiid.gitbooks.io/documents/content/v/9.3.x/admin/Google_Spreadsh... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5019) Makedep hint using @ syntax sometimes ignored

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5019?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-5019. ----------------------------------- Resolution: Done This occurred because the logic was only looking at the first child of the set operation. This was corrected to look at all children. > Makedep hint using @ syntax sometimes ignored > --------------------------------------------- > > Key: TEIID-5019 > URL: https://issues.jboss.org/browse/TEIID-5019 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > I’m using Teiid version 9.2.2. In some cases, using the makedep @<table> feature results in the makedep hint being ignored. > I use this feature to apply a makedep to only one branch of a set operation, since makedep hints are not applied when placed on the individual queries in the set operation . > My query looks like this: > > (Select bbb from ccc > Intersect > select abc.yyy from (select yyy from zzz) abc > ) option makedep @abc.zzz > > In the debug plan in the “GENERATE CANONICAL” section, I see: > > MEDIUM [Hints] Unknown group specified in OPTION MAKEDEP/MAKENOTDEP: @abc.zzz - ignoring hint > > This only occurs if the query has no limit applied to it. If I add a limit option, it does find the table and apply the hint correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5019) Makedep hint using @ syntax sometimes ignored

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5019?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-5019: ---------------------------------- Component/s: Query Engine Fix Version/s: 10.0 9.3.3 > Makedep hint using @ syntax sometimes ignored > --------------------------------------------- > > Key: TEIID-5019 > URL: https://issues.jboss.org/browse/TEIID-5019 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Reporter: Mike Higgins > Assignee: Steven Hawkins > Fix For: 10.0, 9.3.3 > > > I’m using Teiid version 9.2.2. In some cases, using the makedep @<table> feature results in the makedep hint being ignored. > I use this feature to apply a makedep to only one branch of a set operation, since makedep hints are not applied when placed on the individual queries in the set operation . > My query looks like this: > > (Select bbb from ccc > Intersect > select abc.yyy from (select yyy from zzz) abc > ) option makedep @abc.zzz > > In the debug plan in the “GENERATE CANONICAL” section, I see: > > MEDIUM [Hints] Unknown group specified in OPTION MAKEDEP/MAKENOTDEP: @abc.zzz - ignoring hint > > This only occurs if the query has no limit applied to it. If I add a limit option, it does find the table and apply the hint correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5007) Changes to reduce Teiid in the cloud footprint

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-5007?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5007: --------------------------------------- Another issue that affects non-Wildfly usage are the defaults for command logging. For backwards compatibility the splitting of logging source/user level queries means that the user queries are logged at an info level - this may be too verbose. We could introduce a breaking/configurable change to alter this behavior. > Changes to reduce Teiid in the cloud footprint > ---------------------------------------------- > > Key: TEIID-5007 > URL: https://issues.jboss.org/browse/TEIID-5007 > Project: Teiid > Issue Type: Quality Risk > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 10.x > > > A Teiid instance even as swarm or springboot needs additional considerations to minimize the runtime footprint. This includes: > * container aware auto-sizing. Detection of the number of cpus and available memory need refined - there are experimental settings being considered for containerized vms to better report these values and there is logic in WildFly and other projects that attempts better auto-detection. We also need to utilize the memory buffer space more and probably as off-heap space (and ideally direct operations on the serialized data) > * Subsystems required include JTA, webserver, security, which could be satisfied by slimmer alternative versions - especially if we make new assumptions, such as not utilizing xa transactions. > * Engine dependencies could be application specific - removing xml/xsl support, geometry support, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5019) Makedep hint using @ syntax sometimes ignored

by Mike Higgins (JIRA)

Mike Higgins created TEIID-5019: ----------------------------------- Summary: Makedep hint using @ syntax sometimes ignored Key: TEIID-5019 URL: https://issues.jboss.org/browse/TEIID-5019 Project: Teiid Issue Type: Bug Reporter: Mike Higgins Assignee: Steven Hawkins I’m using Teiid version 9.2.2. In some cases, using the makedep @<table> feature results in the makedep hint being ignored. I use this feature to apply a makedep to only one branch of a set operation, since makedep hints are not applied when placed on the individual queries in the set operation . My query looks like this: (Select bbb from ccc Intersect select abc.yyy from (select yyy from zzz) abc ) option makedep @abc.zzz In the debug plan in the “GENERATE CANONICAL” section, I see: MEDIUM [Hints] Unknown group specified in OPTION MAKEDEP/MAKENOTDEP: @abc.zzz - ignoring hint This only occurs if the query has no limit applied to it. If I add a limit option, it does find the table and apply the hint correctly. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-5018) Unable to deploy war using Quickstart: hibernate-on-top-of-teiid using "mvn package jboss-as:deploy" method

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-5018?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-5018: ------------------------------- Fix Version/s: 8.12.x-6.4 10.x > Unable to deploy war using Quickstart: hibernate-on-top-of-teiid using "mvn package jboss-as:deploy" method > ------------------------------------------------------------------------------------------------------------ > > Key: TEIID-5018 > URL: https://issues.jboss.org/browse/TEIID-5018 > Project: Teiid > Issue Type: Bug > Components: Quick Starts > Affects Versions: 8.12.x-6.4, 10.x > Reporter: Van Halbert > Assignee: Van Halbert > Priority: Minor > Fix For: 8.12.x-6.4, 10.x > > > When trying to deploy the vdb as part of the hibernate-on-top-of-teiid quickstart, unable to run the command: mvn -s ../settings.xml package jboss-as:deploy > had to manually deploy the war. > Would suggest changing to use a CLI script. example: > execute: ./jboss-cli.sh --connect --file=../quickstarts/hibernate-on-top-of-teiid/src/scripts/deploy-vdb.cli -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 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 August 2017