May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2906) bind variables and sql appear when exception thrown

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2906?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2906: ---------------------------------- Fix Version/s: 8.4.2 > bind variables and sql appear when exception thrown > --------------------------------------------------- > > Key: TEIID-2906 > URL: https://issues.jboss.org/browse/TEIID-2906 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 8.4 > Environment: - JDV 6.0.0 > Reporter: Hisanobu Okuda > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7 > > Attachments: PreparedStatementTest.java, test.vdb > > > When a query causes an exception, bind variables and sql are written in teiid-command.log and are sent to a client. > teiid-command.log:- > {code} > 19:36:19,942 WARN [org.teiid.PROCESSOR] (Worker8_QueryProcessorQueue29) TEIID30020 Processing exception for request 6jFRdyvDG5bU.0 > 'TEIID30504 New_MySQL: 0 TEIID11008:TEIID11004 Error executing statement(s): [Prepared Values: ['hokuda'] SQL: SELECT g_0.`USERNAM > E`, g_0.`PASSWORD`, g_0.`USERROLE` FROM `LOGIN`.`USERS` AS g_0 WHERE g_0.`USERNAME` = ?]'. Originally TeiidProcessingException 'Can > not read response from server. Expected to read 4 bytes, read 0 bytes before connection was unexpectedly lost.' MysqlIO.java:3039. > Enable more detailed logging to see the entire stacktrace. > {code} > printStackTrace() at client side:- > {code} > org.teiid.jdbc.TeiidSQLException: TEIID30504 Remote org.teiid.core.TeiidProcessingException: TEIID30504 New_MySQL: 0 TEIID11008:TEI > ID11004 Error executing statement(s): [Prepared Values: ['hokuda'] SQL: SELECT g_0.`USERNAME`, g_0.`PASSWORD`, g_0.`USERROLE` FROM > `LOGIN`.`USERS` AS g_0 WHERE g_0.`USERNAME` = ?] > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:135) > at org.teiid.jdbc.TeiidSQLException.create(TeiidSQLException.java:71) > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2940) SQL naming issue with several layers of inline views

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2940?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2940: ---------------------------------- Fix Version/s: 8.4.2 > SQL naming issue with several layers of inline views > ---------------------------------------------------- > > Key: TEIID-2940 > URL: https://issues.jboss.org/browse/TEIID-2940 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.4.2, 8.7.1, 8.8 > > > Several layers of inline views in a source query can cause the alias generation logic to use improper names for higher level symbols resulting in invalid source sql. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2929: --------------------------------------- > I was thinking, at the connection time session service set all the vdb properties on server. Execution properties are not maintained on the server side. It's all client side, and then with each request method we'll send the set of relevant values. So all of that would need to be re-worked for this logic to make sense for JDBC and/or we'd have to introduce initialization logic after logon that will send the default values to the client (similar to pg). However with ODBC we're acting on the server side against our client, so it's quite simple there just to set execution properties (or even connection properties) directly. > Provide ability define "execution properties" as VDB properties > --------------------------------------------------------------- > > Key: TEIID-2929 > URL: https://issues.jboss.org/browse/TEIID-2929 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.8 > > > Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. > However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. > This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2929: ------------------------------------- Steve, I was thinking this available for both ODBC and JDBC or any protocol with following being true > have the vdb properties simply be default values for the session/execution properties. I think this makes sense for well known properties at least. Using this VDB developer can set/force properties on all connections to be made to that VDB, I do not understand the concerns you mention above. I was thinking, at the connection time session service set all the vdb properties on server. > Provide ability define "execution properties" as VDB properties > --------------------------------------------------------------- > > Key: TEIID-2929 > URL: https://issues.jboss.org/browse/TEIID-2929 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.8 > > > Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. > However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. > This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2902) More incremental join when a limit is present

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2902?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2902: --------------------------------------- My first thought was to use the SortUtility singlePassSort logic and merge in subsets, but that will require additional work as even the single pass currently reads all results prior to returning the sorted sublists. We need it to be iterative in this scenario. > More incremental join when a limit is present > --------------------------------------------- > > Key: TEIID-2902 > URL: https://issues.jboss.org/browse/TEIID-2902 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Affects Versions: 8.7 > Reporter: Ivan Chan > Assignee: Steven Hawkins > Fix For: 8.8 > > > For SQL like: > SELECT > t1.column1, > t2.column1 > FROM > schema1.table1 t1, > schema2.table1 t2 > WHERE > t1.column2=t2.column2 > LIMIT 100 > Teiid may get the whole schema1.table1 content and the whole schema2.table1 content, do the join in memory and then, limit the resultset to 100 records. > However, I think teiid can fetch smaller set of data then do a join. If the join result set is less than number of rows asking, keep fetching next set of data and do a join until hits the limit number. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2929: --------------------------------------- A possible solution would be to treat any vdb with a property of the form "connection.xxx" as a name value pair to be set as an execution property after the connection has been made. This would only occur for ODBC connections. If there are no objections or other suggestions, I'll go ahead and commit it. > Provide ability define "execution properties" as VDB properties > --------------------------------------------------------------- > > Key: TEIID-2929 > URL: https://issues.jboss.org/browse/TEIID-2929 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.8 > > > Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. > However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. > This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2947) Implement ODBC cancel

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2947: ------------------------------------- Summary: Implement ODBC cancel Key: TEIID-2947 URL: https://issues.jboss.org/browse/TEIID-2947 Project: Teiid Issue Type: Enhancement Components: ODBC Reporter: Steven Hawkins The ODBC cancel logic would take sending a different set of backend key data and recognizing a different set of initial message flow (as the cancel is issued in a separate connection). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2929) Provide ability define "execution properties" as VDB properties

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2929?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2929: --------------------------------------- The next set of thoughts here is that this may require revamping the way we handle properties. Currently the request message will level the values to booleans, which means that the server side won't know if they are default values. Another approach is to make the logic specific to ODBC, which would then inject the properties at connection time on the server side. A somewhat related scenario was the recent TEIID-2945 issue. For simplicity I'll probably take this approach. > Provide ability define "execution properties" as VDB properties > --------------------------------------------------------------- > > Key: TEIID-2929 > URL: https://issues.jboss.org/browse/TEIID-2929 > Project: Teiid > Issue Type: Enhancement > Components: Server > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.8 > > > Currently if user needs to set any execution properties on their connection, with JDBC they can define on the URL or use "SET " statement to issue a query. In ODBC can also use "SET " method. > However, when working with packaged applications and ODBC or in some situations it may be better to configure these properties VDB wide so that all the connections are using same execution properties. > This JIRA proposes ability to add execution properties as vdb properties in vdb.xml file. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2881) Add support to use DSL when querying remote JDG 6.2

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2881?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-2881: ------------------------------------ Yes, I would agree this logic could be applied to the Object translator, and probably should be. I did notice object translator metadataprocessor doesn't handle associations. So this would be an enhancement, rather than having to worry about backwards compatibility. > Add support to use DSL when querying remote JDG 6.2 > --------------------------------------------------- > > Key: TEIID-2881 > URL: https://issues.jboss.org/browse/TEIID-2881 > Project: Teiid > Issue Type: Feature Request > Components: Misc. Connectors > Affects Versions: 8.7 > Reporter: Van Halbert > Assignee: Van Halbert > > Add support for querying remote JDG 6.2 using DSL. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2472) Create quickstart(s) demonstrating security

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2472?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2472. ----------------------------------- Resolution: Done > Create quickstart(s) demonstrating security > ------------------------------------------- > > Key: TEIID-2472 > URL: https://issues.jboss.org/browse/TEIID-2472 > Project: Teiid > Issue Type: Sub-task > Components: Quick Starts > Reporter: Steven Hawkins > Assignee: Van Halbert > Fix For: 8.4.1 > > > There should be quickstarts (or an expanded dataroles quickstart) covering row based security, column masking, and possibly the use of a udf that uses the subject, a credential mapping security domain, or credential pass-through to highlight other common scenarios. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues May 2014