May 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2930. ----------------------------------- Resolution: Done Added back with(out) hold parsing. > SCROLL keyword for DECLARE CURSOR not being parsed correctly > ------------------------------------------------------------ > > Key: TEIID-2930 > URL: https://issues.jboss.org/browse/TEIID-2930 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.7.9, 8.7.1, 8.8 > > > The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1] > [1] > http://www.postgresql.org/docs/8.4/static/sql-declare.html > [2] > https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii... > Example of error: > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"] > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0] > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0 > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8] > FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully. > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY> -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2930) SCROLL keyword for DECLARE CURSOR not being parsed correctly

by Johnathon Lee (JIRA)

[ https://issues.jboss.org/browse/TEIID-2930?page=com.atlassian.jira.plugin... ] Johnathon Lee reopened TEIID-2930: ---------------------------------- I have used isql and ODBC driver for RHEL5. I am not able to force isql to generate "..scroll cursor for..", however when I type the query[1] directly into isql, it is processed by teiid correctly. So the fix seems to be ok. However the query[2] fails and teiid throws an exception[3] Syntax "cursor with hold for" works correctly for the unpatched version of EDS 5.3.1 so I consider it as a regression. [1] declare "SQL_CUR0x11ad4120" scroll cursor for select intNum from bqt2.smalla;fetch 100 in "SQL_CUR0x11ad4120" [2] declare "SQL_CUR0xe61c20" cursor with hold for select * from pg_proc [3] org.teiid.jdbc.TeiidSQLException: Direct usage of XQuery is no longer supported, use XMLQUERY instead. > SCROLL keyword for DECLARE CURSOR not being parsed correctly > ------------------------------------------------------------ > > Key: TEIID-2930 > URL: https://issues.jboss.org/browse/TEIID-2930 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 7.7.8 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.7.9, 8.7.1, 8.8 > > > The DECLARE cursor is defined as [1]. However, in [2] line #155, the SCROLL keyword is not being matched. Correction would be to match the pattern fully as defined in [1] > [1] > http://www.postgresql.org/docs/8.4/static/sql-declare.html > [2] > https://github.com/teiid/teiid/blob/master/runtime/src/main/java/org/teii... > Example of error: > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking server method: executeQuery [BEGIN;declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY>;fetch 100 in "SQL_CUR0x11ad4120"] > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: START TRANSACTION > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [START TRANSACTION] expecting: EITHER > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as transaction statement > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: sendUpdateCount [BEGIN, 0] > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing: requestID -1 commands: [show client_encoding] expecting: RESULTSET > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Executing as show statement > FINER [org.teiid.jdbc] (New I/O server worker #3-1) Creating ResultSet requestID: -1 beginRow: 1 resultsColumns: 1 parameters: 0 > TRACE [org.teiid.ODBC] (New I/O server worker #3-1) invoking client method: setEncoding [UTF-8] > FINE [org.teiid.jdbc] (New I/O server worker #3-1) Statement closed successfully. > DEBUG [org.teiid.ODBC] (New I/O server worker #3-1) Modified Query: declare "SQL_CUR0x11ad4120" scroll cursor for <SQL QUERY> -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2971) wrong property name in max sessions message

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2971?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2971. ----------------------------------- Resolution: Done Updated the messsage > wrong property name in max sessions message > ------------------------------------------- > > Key: TEIID-2971 > URL: https://issues.jboss.org/browse/TEIID-2971 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > the error message references session-max-limit rather than max-session-allowed -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2971) wrong property name in max sessions message

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2971: ------------------------------------- Summary: wrong property name in max sessions message Key: TEIID-2971 URL: https://issues.jboss.org/browse/TEIID-2971 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 the error message references session-max-limit rather than max-session-allowed -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2481) common table (with) push down improvements

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2481?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2481: --------------------------------------- I think the first improvement to tackle is actually just allowing views with common tables to be mergable into the parent plans. Currently we treat them as subplans - which means that further pushdown, dependent joins toward the side with a common table, etc. will not be done. However this will require quite a few changes to the planning logic as it is currently geared solely to determining with pushdown on a single query/view layer at a time. > common table (with) push down improvements > ------------------------------------------ > > Key: TEIID-2481 > URL: https://issues.jboss.org/browse/TEIID-2481 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.8 > > > The general strategy for with pushdown should better handle: > - a with clause that can be pushed against a source that does not support common table. If a single reference or some other sufficient condition is met then we should just inline the pushdown rather than inhibiting the whole query from pushing down. > - even if a source supports with pushdown, it may be more performant in some circumstances to inline the common table reference (such as only a single reference). This is complicated slightly by subqueries. > - alternatively in some situations even if a with clause can be pushed, it may be better to not perform the pushdown -e.g. two separate pushdown accesses to a common table that is expensive to compute (this may need to be hint driven). -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2969) timestamp parse format issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2969?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2969. ----------------------------------- Resolution: Done Removed support for pg pushdown of timestampdiff. Corrected the format modifier to appropriately quote, and the pg format modifier will now account for differences with oracle. > timestamp parse format issues > ----------------------------- > > Key: TEIID-2969 > URL: https://issues.jboss.org/browse/TEIID-2969 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle. > Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2969) timestamp parse format issues

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2969?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2969: ---------------------------------- Forum Reference: https://community.jboss.org/thread/241234 > timestamp parse format issues > ----------------------------- > > Key: TEIID-2969 > URL: https://issues.jboss.org/browse/TEIID-2969 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Affects Versions: 7.7 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.8 > > > Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle. > Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2970) possible timing issue with transport services

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2970: ------------------------------------- Summary: possible timing issue with transport services Key: TEIID-2970 URL: https://issues.jboss.org/browse/TEIID-2970 Project: Teiid Issue Type: Bug Components: Server Affects Versions: 8.0 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 Since the listener start is creating other threads we should ensure that services are added prior to starting the listener. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2969) timestamp parse format issues

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2969: ------------------------------------- Summary: timestamp parse format issues Key: TEIID-2969 URL: https://issues.jboss.org/browse/TEIID-2969 Project: Teiid Issue Type: Bug Components: Misc. Connectors Affects Versions: 7.7 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.8 Oracle and Postgresql pushdown of parse/format of timestamps is generally incorrect as the format string is left unquoted. Also Postgresql does not support the same syntax as oracle. Also pushdown of timestampdiff is not correct for pg for fields other than DAY and YEAR. Fractional seconds are not implemented and all of the other fields seem to return just the calendar field difference, not the number of intervals different - e.g. the difference in hours for timestamps that are years apart is just the 24 hour difference. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TEIID-2913) Remove Logging Quickstart

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-2913?page=com.atlassian.jira.plugin... ] Van Halbert resolved TEIID-2913. -------------------------------- Resolution: Done Removed the the custom-log4j-db-logger quick start > Remove Logging Quickstart > ------------------------- > > Key: TEIID-2913 > URL: https://issues.jboss.org/browse/TEIID-2913 > Project: Teiid > Issue Type: Task > Components: Quick Starts > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Van Halbert > > Add the following enhancements to the logging quick start: > - add example for audit logging to a database (use h2) > - add dynamic VDB's to expose the audit and command logging schemas > - add a preconfigured dashboard to present the audit and command logs -- This message was sent by Atlassian JIRA (v6.2.3#6260)

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