September 2014 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ] Work on TEIID-3125 started by Steven Hawkins. --------------------------------------------- > Netezza translator - add support for the LIKE_REGEX predicate. > -------------------------------------------------------------- > > Key: TEIID-3125 > URL: https://issues.jboss.org/browse/TEIID-3125 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.9 > > > With version 6 of Jboss DV the Netezza translator doesn't support the LIKE_REGEX predicate. > Netezza doesn't support regular expression by default, but with the installation of SQL Extensions toolkit this functionality is added. After installation Netezza provide the regular expression functions: > regexp_extract() > regexp_extract_all() > regexp_extract_all_sp() > regexp_extract_sp() > regexp_instr() > regexp_like() > regexp_match_count() > regexp_replace() > regexp_replace_sp() > IBM Netezza SQL Extensions toolkit is an optional package for IBM Netezza data warehouse appliances. > After installing this toolkit on Netezza and requires that regular expression in JBoss DV syntax are pushed down (delegated) to Netezza to prevent that filtering in the Jboss DV server most be done. > So please provide a configurable option in the Netezza translator of Jboss DV by which we can enable the LIKE_REGEX predicate for Netezza. This option when enabled will assume that the Netezza SQL extension toolkit is installed and the function regexp_like() is available. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3140?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3140: --------------------------------------- I'm fine with exposing whether it is an xml deployment - the VDBMetaData already has an isXmlDeployment method. However preview is currently a designer construct and can be checked via a property. Any notion of DDL or some other metadata type really depends upon the configuration of the metadata repositories associated with models. > Add getVDBType() method to the VDB interface > -------------------------------------------- > > Key: TEIID-3140 > URL: https://issues.jboss.org/browse/TEIID-3140 > Project: Teiid > Issue Type: Enhancement > Reporter: Barry LaFond > Assignee: Steven Hawkins > > Because Teiid supports mutliple VDB types, any tooling designed to interact (edit, deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly distinguish what each VDB type is. > Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata definitions. > The current VDB interface currently doesn't provide a type. > Request adding something like: > {code} > public enum VDBType {DEFAULT, PREVIEW, XML, DDL} > /** > * @return the vdb type > */ > public VDBType getVDBType(); > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3140) Add getVDBType() method to the VDB interface

by Barry LaFond (JIRA)

Barry LaFond created TEIID-3140: ----------------------------------- Summary: Add getVDBType() method to the VDB interface Key: TEIID-3140 URL: https://issues.jboss.org/browse/TEIID-3140 Project: Teiid Issue Type: Enhancement Reporter: Barry LaFond Assignee: Steven Hawkins Because Teiid supports mutliple VDB types, any tooling designed to interact (edit, deploy, undeploy, display etc...) with the runtime VDBs will need to be able to easilly distinguish what each VDB type is. Currently Teiid Designer utilizes PREVIEW and defeault VDBs with *vdb* file extensions and there are 2 types of dynamic VDBs, *xml* and *zip* files backed by DDL model metadata definitions. The current VDB interface currently doesn't provide a type. Request adding something like: {code} public enum VDBType {DEFAULT, PREVIEW, XML, DDL} /** * @return the vdb type */ public VDBType getVDBType(); {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3139) Common table expressions are not pre-evaluated

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3139?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3139. ----------------------------------- Resolution: Done Ensured that queries with pushdown common table expressions are always pre-evaluated. > Common table expressions are not pre-evaluated > ---------------------------------------------- > > Key: TEIID-3139 > URL: https://issues.jboss.org/browse/TEIID-3139 > 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 > > > With sql such as: > {code} > with test as ( > select CURDATE() as startDate > from schema.table) > select startDate from test > {code} > The curdate function will be pushed to the source regardless of whether it is supported. It should be pre-evaluated prior to pushdown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3121) Teiid Standalone Server

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ] Ramesh Reddy commented on TEIID-3121: ------------------------------------- For me bundling the libraries/frameworks seems ok, but bundling the whole platform seems not correct, especially when they can be accomplished using scripts like one referenced. > Teiid Standalone Server > ----------------------- > > Key: TEIID-3121 > URL: https://issues.jboss.org/browse/TEIID-3121 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Tom Arnold > Fix For: Open To Community > > > Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss. > * Teiid Runtime > * Teiid Web Console > * JBoss EAP 6.1 Alpha > * Resteasy JAX-RS Patch > End result would simplify the installation process to: > 1. Unzip Teiid server. > 2. Run `bin/add-user.sh` script. > 3. Deploy custom translators, VDB, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3121) Teiid Standalone Server

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3121?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3121: --------------------------------------- > My script would only add at most 10 minutes to the release process, but would lower the barrier to entry for people looking to develop against Teiid. The script isn't written from the perspective of the release process. It's written more as a developer aid and dependent upon a unix shell. > If you'd like to go a different direction though, I can change my script accordingly. For it to be a formal part of the build process we'd probably want it mavenized and ideally pulling the other artifacts from maven managed dependencies so that the download urls don't need to be separately maintained. > Teiid Standalone Server > ----------------------- > > Key: TEIID-3121 > URL: https://issues.jboss.org/browse/TEIID-3121 > Project: Teiid > Issue Type: Feature Request > Components: Build/Kits > Reporter: Tom Arnold > Fix For: Open To Community > > > Perform the server installation steps as part of the build and add the result to the downloads page. It seems like this is something that everyone who isn't using the embedded kit has to do anyways, and would hopefully eliminate confusion caused by people trying to deploy the runtime in unsupported versions of JBoss. > * Teiid Runtime > * Teiid Web Console > * JBoss EAP 6.1 Alpha > * Resteasy JAX-RS Patch > End result would simplify the installation process to: > 1. Unzip Teiid server. > 2. Run `bin/add-user.sh` script. > 3. Deploy custom translators, VDB, etc. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3139) Common table expressions are not pre-evaluated

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3139: ------------------------------------- Summary: Common table expressions are not pre-evaluated Key: TEIID-3139 URL: https://issues.jboss.org/browse/TEIID-3139 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 With sql such as: {code} with test as ( select CURDATE() as startDate from schema.table) select startDate from test {code} The curdate function will be pushed to the source regardless of whether it is supported. It should be pre-evaluated prior to pushdown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3116) Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked)

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3116?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3116. ----------------------------------- Resolution: Done For 8.9 the exception thrown will include more detail and https://docs.jboss.org/author/display/TEIID/Partial+Results+Mode was updated to include a warning about not determining capabilities. To address this more fully we'd need to ensure that plans using invalid capabilities are marked in such a way as to not be cachable. > Teiid Partial Results Mode: unavailability of datasource causes error (which is not masked) > ------------------------------------------------------------------------------------------- > > Key: TEIID-3116 > URL: https://issues.jboss.org/browse/TEIID-3116 > Project: Teiid > Issue Type: Bug > Components: Server > Affects Versions: 8.7.1 > Reporter: Van Halbert > Assignee: Steven Hawkins > Priority: Minor > > Description of problem: > Querying a vdb-table which is formed as union of two tables from different datasources. Even though "set partialresultsmode true" is run as initial query, instead of retreiving 0 rows from a datasources that is down, exception is promoted. > Version-Release number of selected component (if applicable): > DV 6.1 ER1 > How reproducible: > Every time > Steps to Reproduce: > 1. Define one valid and one invalid datasource(invalid connection-url). > 2. Create vdb which maps tables from both datasources. > 3. Set partialresultsmode to true > 4. Execute query on the given vdb-table > Actual results: > TeiidSQLException > TEIID30498 Remote org.teiid.api.exception.query.QueryPlannerException: TEIID30498 Capabilities for ORBQT were not avaialable. The command could not be planned properly. > Expected results: > 0 rows from invalid datasource. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3138) EmbeddedServer does not shutdown the session monitor

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3138?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3138. ----------------------------------- Fix Version/s: 8.9 (was: 8.7) Resolution: Done Added the appropriate shutdown logic. > EmbeddedServer does not shutdown the session monitor > ---------------------------------------------------- > > Key: TEIID-3138 > URL: https://issues.jboss.org/browse/TEIID-3138 > Project: Teiid > Issue Type: Bug > Components: Embedded > Affects Versions: 8.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 8.9 > > > The session service has a timer thread which should be shutdown when the embedded server is shutdown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3138) EmbeddedServer does not shutdown the session monitor

by Steven Hawkins (JIRA)

Steven Hawkins created TEIID-3138: ------------------------------------- Summary: EmbeddedServer does not shutdown the session monitor Key: TEIID-3138 URL: https://issues.jboss.org/browse/TEIID-3138 Project: Teiid Issue Type: Bug Components: Embedded Affects Versions: 8.4 Reporter: Steven Hawkins Assignee: Steven Hawkins Fix For: 8.7 The session service has a timer thread which should be shutdown when the embedded server is shutdown. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 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 2014