November 2013 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-2740) Support Direct Query Execution with MongoDB

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2740?page=com.atlassian.jira.plugin... ] Ramesh Reddy resolved TEIID-2740. --------------------------------- Resolution: Done Added support for direct execution of aggregation based pipeline command that user can execute using javascript style command. The result is returned as Blob. Currently the BSON document is serialized to string and then back into Blob at the translator level, however when the MongoDB java driver supports streaming then this needs to be fixed to use streaming interface to avoid any memory issues with very large documents. Also updated document for this feature. > Support Direct Query Execution with MongoDB > ------------------------------------------- > > Key: TEIID-2740 > URL: https://issues.jboss.org/browse/TEIID-2740 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Affects Versions: 8.4 > Reporter: Ramesh Reddy > Assignee: Ramesh Reddy > Fix For: 8.6 > > > Direct query execution in the MongoDB was not implemented completely. This needs to be fixed as this would be a very helpful enhancement. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2744) Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-2744?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-2744: ------------------------------------- Run with the debug on server and provide the exact SQL statement being handled by the ODBC layer. Or log. > Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server > ---------------------------------------------------------------------- > > Key: TEIID-2744 > URL: https://issues.jboss.org/browse/TEIID-2744 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4.1 > Environment: Windows 2008 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > When running ODBC driver on windows, the querying works but weird WARNinig is showed in the server console. > The warning message: > 03:31:58,965 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue5) TEIID30020 Processing exception for request xS0DtHsdmG7n.9 'TEIID31100 Parsing error: Encountered "('\"customer\"' AS [*]regclass[*])" at line 1, column 106. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'. Originally QueryParserException QueryParser.java:215. Enable more detailed logging to see the entire stacktrace. > See BZ for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2744) Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2744?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2744: --------------------------------------- How is a warning a blocker? > Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server > ---------------------------------------------------------------------- > > Key: TEIID-2744 > URL: https://issues.jboss.org/browse/TEIID-2744 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4.1 > Environment: Windows 2008 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > When running ODBC driver on windows, the querying works but weird WARNinig is showed in the server console. > The warning message: > 03:31:58,965 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue5) TEIID30020 Processing exception for request xS0DtHsdmG7n.9 'TEIID31100 Parsing error: Encountered "('\"customer\"' AS [*]regclass[*])" at line 1, column 106. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'. Originally QueryParserException QueryParser.java:215. Enable more detailed logging to see the entire stacktrace. > See BZ for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2744) Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-2744?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-2744: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1031606 > Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server > ---------------------------------------------------------------------- > > Key: TEIID-2744 > URL: https://issues.jboss.org/browse/TEIID-2744 > Project: Teiid > Issue Type: Bug > Components: ODBC > Affects Versions: 8.4.1 > Environment: Windows 2008 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Blocker > > When running ODBC driver on windows, the querying works but weird WARNinig is showed in the server console. > The warning message: > 03:31:58,965 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue5) TEIID30020 Processing exception for request xS0DtHsdmG7n.9 'TEIID31100 Parsing error: Encountered "('\"customer\"' AS [*]regclass[*])" at line 1, column 106. > Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'. Originally QueryParserException QueryParser.java:215. Enable more detailed logging to see the entire stacktrace. > See BZ for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2744) Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server

by Van Halbert (JIRA)

Van Halbert created TEIID-2744: ---------------------------------- Summary: Windows 2008 ODBC Driver works but throwing exceptions on Teiid Server Key: TEIID-2744 URL: https://issues.jboss.org/browse/TEIID-2744 Project: Teiid Issue Type: Bug Components: ODBC Affects Versions: 8.4.1 Environment: Windows 2008 Reporter: Van Halbert Assignee: Steven Hawkins Priority: Blocker When running ODBC driver on windows, the querying works but weird WARNinig is showed in the server console. The warning message: 03:31:58,965 WARN [org.teiid.PROCESSOR] (Worker1_QueryProcessorQueue5) TEIID30020 Processing exception for request xS0DtHsdmG7n.9 'TEIID31100 Parsing error: Encountered "('\"customer\"' AS [*]regclass[*])" at line 1, column 106. Was expecting: "string" | "varbinary" | "varchar" | "boolean" | "byte" | "tinyint" | "short" | "smallint" | "char" | "integer" ...'. Originally QueryParserException QueryParser.java:215. Enable more detailed logging to see the entire stacktrace. See BZ for more details. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2743) XMLTable does not account for DST

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2743?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2743. ----------------------------------- Resolution: Done Added a check for dst to use the offset from the particular UTC. > XMLTable does not account for DST > --------------------------------- > > Key: TEIID-2743 > URL: https://issues.jboss.org/browse/TEIID-2743 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 8.2 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.6 > > > The fix for TEIID-2112 does not consider DST server timezones. While it is not typically expected for a server to be running in DST, we should still handle this situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2743) XMLTable does not account for DST

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-2743: ------------------------------------- Summary: XMLTable does not account for DST Key: TEIID-2743 URL: https://issues.jboss.org/browse/TEIID-2743 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.2 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.6 The fix for TEIID-2112 does not consider DST server timezones. While it is not typically expected for a server to be running in DST, we should still handle this situation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2112) consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2112?page=com.atlassian.jira.plugin... ] Steven Hawkins closed TEIID-2112. --------------------------------- > consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. > --------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2112 > URL: https://issues.jboss.org/browse/TEIID-2112 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.4.4, 8.2 > > > The server is taking the incoming ts string and converting it to a Z value via the server timezone (handled by STax). When the response document is delivered Saxon converts a non-timezoned value into an assumed Z value - which is not consistent with the STax handling. This is within the bounds of XML processing as the absence of timezone information leaves the timezone interpretation up to the implementation - "timezone of some unspecified locality as prescribed by the appropriate legal authority". > However, these two paths should be consistent,so a patch would set the local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2112) consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2112?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2112. ----------------------------------- Resolution: Done > consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. > --------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2112 > URL: https://issues.jboss.org/browse/TEIID-2112 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 8.2, 7.4.4 > > > The server is taking the incoming ts string and converting it to a Z value via the server timezone (handled by STax). When the response document is delivered Saxon converts a non-timezoned value into an assumed Z value - which is not consistent with the STax handling. This is within the bounds of XML processing as the absence of timezone information leaves the timezone interpretation up to the implementation - "timezone of some unspecified locality as prescribed by the appropriate legal authority". > However, these two paths should be consistent,so a patch would set the local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TEIID-2112) consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-2112?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-2112: ---------------------------------- Fix Version/s: (was: 8.1) > consistent handling of local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. > --------------------------------------------------------------------------------------------------------------------- > > Key: TEIID-2112 > URL: https://issues.jboss.org/browse/TEIID-2112 > Project: Teiid > Issue Type: Bug > Components: Query Engine > Affects Versions: 7.1 > Reporter: Johnathon Lee > Assignee: Steven Hawkins > Fix For: 7.4.4, 8.2 > > > The server is taking the incoming ts string and converting it to a Z value via the server timezone (handled by STax). When the response document is delivered Saxon converts a non-timezoned value into an assumed Z value - which is not consistent with the STax handling. This is within the bounds of XML processing as the absence of timezone information leaves the timezone interpretation up to the implementation - "timezone of some unspecified locality as prescribed by the appropriate legal authority". > However, these two paths should be consistent,so a patch would set the local timezone on xsd:date, xsd:datetime, and xsd:time values that have no timezone specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues November 2013