October 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3095) Expose system and pushdown functions

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3095?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3095: --------------------------------------- Added system and pushdown functions to the system tables. The only other place it makes sense to add them is in the generated ddl. > Expose system and pushdown functions > ------------------------------------ > > Key: TEIID-3095 > URL: https://issues.jboss.org/browse/TEIID-3095 > Project: Teiid > Issue Type: Sub-task > Components: Query Engine > Affects Versions: 8.9 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > The system functions and pushdown functions are not added as normal schema scoped functions, and thus were not exposed by TEIID-3044. We should properly expose them and if possible also add uuids and the ability to lookup system properties. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3174) integer operation within LEFT command

by Bram Gadeyne (JIRA)

[ https://issues.jboss.org/browse/TEIID-3174?page=com.atlassian.jira.plugin... ] Bram Gadeyne closed TEIID-3174. ------------------------------- Resolution: Done This was not a bug. In some database row a string did not contain a ,. That's why I got the error. > integer operation within LEFT command > ------------------------------------- > > Key: TEIID-3174 > URL: https://issues.jboss.org/browse/TEIID-3174 > Project: Teiid > Issue Type: Bug > Affects Versions: 8.7 > Reporter: Bram Gadeyne > Assignee: Steven Hawkins > Labels: left, stringfunction > > When executing a command of the following form > LEFT(Description,((LOCATE(',',Description))-1)) > I get an Exception like this: > 14:31:00,038 WARN [org.teiid.PROCESSOR] (Worker3295_QueryProcessorQueue53347) 5tz38FpQ/WJw TEIID30020 Processing exception for request 5tz38FpQ/WJw.50 'TEIID30328 Unable to evaluate LEFT(sometable.Description, (LOCATE(',', sometable.Description) - 1)): TEIID30384 Error while evaluating function left'. Originally ExpressionEvaluationException 'TEIID30396 Left/Right count -1 is invalid. It must be >= 0.' FunctionMethods.java:758. Enable more detailed logging to see the entire stacktrace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3177) Enforce SSL connections over ODBC when Encryption Mode is enabled

by Cristiano Nicolai (JIRA)

Cristiano Nicolai created TEIID-3177: ---------------------------------------- Summary: Enforce SSL connections over ODBC when Encryption Mode is enabled Key: TEIID-3177 URL: https://issues.jboss.org/browse/TEIID-3177 Project: Teiid Issue Type: Feature Request Components: ODBC Affects Versions: 8.8 Reporter: Cristiano Nicolai Assignee: Steven Hawkins Priority: Critical When connecting via ODBC transport, even if the encryption mode is set to enabled is still possible to establish non ssl connections. This allows clients to connect via insecure method. We would like that the Teiid transport could reject connections if they are not properly set up using SSL transport. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3168) SQL Server requires N prefix for unicode literals

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3168?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated TEIID-3168: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1153394 > SQL Server requires N prefix for unicode literals > ------------------------------------------------- > > Key: TEIID-3168 > URL: https://issues.jboss.org/browse/TEIID-3168 > Project: Teiid > Issue Type: Bug > Components: JDBC Connector > Affects Versions: 6.0.0 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > SQL Server requires the use of the N prefix for string literals when there are non-ascii/windows characters present. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3176) Processing exception with function/procedure column and non-short scale

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3176?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-3176: ---------------------------------- Component/s: JDBC Driver (was: Query Engine) > Processing exception with function/procedure column and non-short scale > ----------------------------------------------------------------------- > > Key: TEIID-3176 > URL: https://issues.jboss.org/browse/TEIID-3176 > Project: Teiid > Issue Type: Bug > Components: JDBC Driver > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.7.1, 8.9 > > > The DatabaseMetadata.getProcedureColumns method expects scale to be reported as a short, but our scale metadata is an integer - and by default a bigdecimal column will have a max integer scale. This results in a processing when getting the metadata. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3176) Processing exception with function/procedure column and non-short scale

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3176: ------------------------------------- Summary: Processing exception with function/procedure column and non-short scale Key: TEIID-3176 URL: https://issues.jboss.org/browse/TEIID-3176 Project: Teiid Issue Type: Bug Components: Query Engine Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7.1, 8.9 The DatabaseMetadata.getProcedureColumns method expects scale to be reported as a short, but our scale metadata is an integer - and by default a bigdecimal column will have a max integer scale. This results in a processing when getting the metadata. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3044) Add function metadata to system tables / databasemetadata

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3044?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3044. ----------------------------------- Resolution: Done Marking as resolved with remaining work to be performed by the subtasks. > Add function metadata to system tables / databasemetadata > --------------------------------------------------------- > > Key: TEIID-3044 > URL: https://issues.jboss.org/browse/TEIID-3044 > Project: Teiid > Issue Type: Feature Request > Components: JDBC Driver, Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > We should expose source/system/udf functions via system metadata. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3175) Allow property lookup on function parameters

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3175: ------------------------------------- Summary: Allow property lookup on function parameters Key: TEIID-3175 URL: https://issues.jboss.org/browse/TEIID-3175 Project: Teiid Issue Type: Sub-task Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.9 FunctionParameters until TEIID-3044 were not first class metadata objects, so now we need to round out support them including extension metadata lookup. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 8 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 updated TEIID-2481: ---------------------------------- Fix Version/s: 8.10 (was: 8.9) > 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.10 > > > 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.3.1#6329)

9 years, 8 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... ] Work on TEIID-2481 stopped by Steven Hawkins. --------------------------------------------- > 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.10 > > > 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.3.1#6329)

9 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues October 2014