September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3725) In the JDG translators, enable named cache swapping so that materialization can be supported

by Van Halbert (JIRA)

Van Halbert created TEIID-3725: ---------------------------------- Summary: In the JDG translators, enable named cache swapping so that materialization can be supported Key: TEIID-3725 URL: https://issues.jboss.org/browse/TEIID-3725 Project: Teiid Issue Type: Feature Request Components: Misc. Connectors Affects Versions: 8.12 Reporter: Van Halbert Assignee: Van Halbert The JDG translators, that in order to support materialization, will need to enable the named cache that's referenced by the connection, to be swapped. This is due to JDG doesn't currently support renaming a cache (i.e., like table rename in JDBC). And because of that, it limits how the cache can be refreshed (don't want to clear it before re-loading). Ideas are: 1. configure translator with the 2 cache names to use (a) initial cache to read from and (b) the staging cache to use perform materialize load call SYSADMIN.setProperty to trigger the swapping of the cache names 2 ??? Note: because there's no persistence in Teiid so that any cache name changes will outlive a server restart, when a restart occurs, the translator will read from the cache identified as the initial cache to read from. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3724) Add an option to not widen comparisons to string

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3724: ------------------------------------- Summary: Add an option to not widen comparisons to string Key: TEIID-3724 URL: https://issues.jboss.org/browse/TEIID-3724 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: int_col = '1a' will effectively become cast(int_col as string) = '1a' Or with timestamps: timestamp_col = '1970-01-01' becomes cast(timestamp_col as string) = '1970-01-01' In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3723) Add OPTIONS capability to Procedure ResultSet

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3723: ------------------------------------- Summary: Add OPTIONS capability to Procedure ResultSet Key: TEIID-3723 URL: https://issues.jboss.org/browse/TEIID-3723 Project: Teiid Issue Type: Enhancement Components: Connector API, Query Engine Reporter: Ramesh Reddy Assignee: Steven Hawkins Fix For: 8.12 Currently there is no way to add metadata on Procedures return value if the return value is "ResultSet". Actually you can call _setProperty_ add on _ColumnSet<Procedure>_ metadata object, but _DDLStringFactory_ will not recognize it, also I believe JAVACC file needs to updated for this to recognize. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3721) Add OPTIONS capability to Procedure ResultSet

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3721?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3721. ----------------------------------- Resolution: Done Added support, but the syntax is slightly different as it appears after the returns keyword - so that there is no ambiguity with the procedure options. ... RETURNS (options ...) type ... RETURNS (options ...) TABLE (...) > Add OPTIONS capability to Procedure ResultSet > --------------------------------------------- > > Key: TEIID-3721 > URL: https://issues.jboss.org/browse/TEIID-3721 > Project: Teiid > Issue Type: Enhancement > Components: Connector API, Query Engine > Reporter: Ramesh Reddy > Assignee: Steven Hawkins > Fix For: 8.12 > > > Currently there is no way to add metadata on Procedures return value if the return value is "ResultSet". > Actually you can call _setProperty_ add on _ColumnSet<Procedure>_ metadata object, but _DDLStringFactory_ will not recognize it, also I believe JAVACC file needs to updated for this to recognize. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3718: --------------------------------------- Yes, if we add them they can go in a different repository. For the project I think we'll simply promote JBoss Logging to the engine. > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Steven Hawkins > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3722) Add an option to not widen comparisons to string

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3722?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3722. ----------------------------------- Resolution: Done Added a system property org.teiid.widenComparisonToString and updated the release notes / docs. We should consider having this default to false for Teiid 9. > Add an option to not widen comparisons to string > ------------------------------------------------ > > Key: TEIID-3722 > URL: https://issues.jboss.org/browse/TEIID-3722 > Project: Teiid > Issue Type: Quality Risk > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: > int_col = '1a' > will effectively become cast(int_col as string) = '1a' > Or with timestamps: > timestamp_col = '1970-01-01' > becomes cast(timestamp_col as string) = '1970-01-01' > In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. > This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3718) Add Log4j 2 Logger Adapter

by Kylin Soong (JIRA)

[ https://issues.jboss.org/browse/TEIID-3718?page=com.atlassian.jira.plugin... ] Kylin Soong commented on TEIID-3718: ------------------------------------ To consist with other component like SecurityHelper, TransactionManager, I think these 2 implements should not going to teiid api module, these may go to a separate repository [1]. [1] https://github.com/teiid/teiid-embedded > Add Log4j 2 Logger Adapter > -------------------------- > > Key: TEIID-3718 > URL: https://issues.jboss.org/browse/TEIID-3718 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Affects Versions: 8.11.4 > Environment: Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06; 2015-04-22T04:57:37-07:00) > Maven home: C:\Java\apache-maven-3.3.3 > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Steven Hawkins > Attachments: Log4j2LoggerAdapter.java > > > Add a Log4j 2 Logger Adapter. See attached. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3362) Additional language constructs for arrays

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3362?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3362: ------------------------------------------------ Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 1266586|https://bugzilla.redhat.com/show_bug.cgi?id=1266586] from NEW to ASSIGNED > Additional language constructs for arrays > ----------------------------------------- > > Key: TEIID-3362 > URL: https://issues.jboss.org/browse/TEIID-3362 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.11 > > > Additional handling for arrays, such as an unnest function (columns to rows), a 2 dimensional form or arraytable, array concat etc. would be beneficial. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3712) Add support for DATE/TIME/TIMESTAMP keyword literals

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3712?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3712. ----------------------------------- Resolution: Done Added parsing support and updated the documentation. Will also update the grammar before the release. > Add support for DATE/TIME/TIMESTAMP keyword literals > ---------------------------------------------------- > > Key: TEIID-3712 > URL: https://issues.jboss.org/browse/TEIID-3712 > Project: Teiid > Issue Type: Enhancement > Components: Query Engine > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.12 > > > As per the spec we should support the literal format: > DATE '...' > TIME '...' > TIMESTAMP '...' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3722) Add an option to not widen comparisons to string

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3722: ------------------------------------- Summary: Add an option to not widen comparisons to string Key: TEIID-3722 URL: https://issues.jboss.org/browse/TEIID-3722 Project: Teiid Issue Type: Quality Risk Components: Query Engine Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.12 Our resolving logic considers anything with an implicit conversion to string to be a valid widening conversion in a comparison. For example: int_col = '1a' will effectively become cast(int_col as string) = '1a' Or with timestamps: timestamp_col = '1970-01-01' becomes cast(timestamp_col as string) = '1970-01-01' In equality cases the optimizer will infer that the predicate is simply false, but when used with greater/less than comparison we'll still attempt the query with the widening conversion. This is most likely not the intent of the user. It would be best to provide an option that would allow an exception to be thrown rather than assuming a query that may not match the user's expectations. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-issues September 2015