September 2015 - teiid-issues - Jboss List Archives

[JBoss JIRA] (TEIID-3677) Update the Teiid Community Home Page to show all the types of data sources being supported

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3677?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3677: ------------------------------------ Sure, as soon as I figure out how to build the community-website on my mac. Missing some of those dependencies. > Update the Teiid Community Home Page to show all the types of data sources being supported > ------------------------------------------------------------------------------------------ > > Key: TEIID-3677 > URL: https://issues.jboss.org/browse/TEIID-3677 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: teiid_architecture.png > > > With all the new types of data sources being supported by Teiid, it would be nice to indicate those on the Teiid Community home page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3677) Update the Teiid Community Home Page to show all the types of data sources being supported

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3677?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3677: --------------------------------------- Seems good, do you want to roll this into the pull request for the micro-services stuff? > Update the Teiid Community Home Page to show all the types of data sources being supported > ------------------------------------------------------------------------------------------ > > Key: TEIID-3677 > URL: https://issues.jboss.org/browse/TEIID-3677 > Project: Teiid > Issue Type: Enhancement > Components: Documentation > Reporter: Van Halbert > Assignee: Van Halbert > Attachments: teiid_architecture.png > > > With all the new types of data sources being supported by Teiid, it would be nice to indicate those on the Teiid Community home page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3642) RhinoScriptEngineFactory be removed in Java 8

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIID-3642?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on TEIID-3642: ------------------------------------------------ Jan Stastny <jstastny(a)redhat.com> changed the Status of [bug 1254399|https://bugzilla.redhat.com/show_bug.cgi?id=1254399] from ON_QA to ASSIGNED > RhinoScriptEngineFactory be removed in Java 8 > ---------------------------------------------- > > Key: TEIID-3642 > URL: https://issues.jboss.org/browse/TEIID-3642 > Project: Teiid > Issue Type: Quality Risk > Components: OData > Affects Versions: 8.7.1.6_2, 8.12 > Environment: * DV 6.2.0.ER4 > * Java 1.8.0_25 > Reporter: Kylin Soong > Assignee: Steven Hawkins > > RhinoScriptEngineFactory be removed in Java 8, this cause OData war deploy output Error: > {code} > 09:30:51,315 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-6) JBAS015868: Deployment "deployment.teiid-odata-8.7.1.6_2-redhat-2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice. > 09:30:51,424 ERROR [stderr] (MSC service thread 1-6) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,429 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,505 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,513 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > 09:30:51,583 ERROR [stderr] (MSC service thread 1-1) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found > {code} > *OData war* depend on *org.joda.time*, *org.joda.time* depend on *RhinoScriptEngineFactory*, due to RhinoScriptEngineFactory be removed in Java 8, so stderr output in console. > h3. how to reproduce > Start DV 6.2 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3512) produce a lighter weight embedded kit

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3512?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-3512: --------------------------------------- > how to use the"maven pull" replace optional, I still have no idea. Ramesh is talking about the path of not having an embedded kit and just using an appropriate set of maven dependencies to pull in what's needed. We aren't quite there yet though. > produce a lighter weight embedded kit > ------------------------------------- > > Key: TEIID-3512 > URL: https://issues.jboss.org/browse/TEIID-3512 > Project: Teiid > Issue Type: Feature Request > Components: Embedded > Reporter: Steven Hawkins > Assignee: Kylin Soong > > The embedded kit should be a small as possible, and it should be clear/easy to get dependency sets for each optional piece of functionality. This could include using maven to pull artifacts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3692) Impala/Hive string literals

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIID-3692?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-3692. ----------------------------------- Fix Version/s: 8.11.4 Resolution: Done Resolved with a new override. > Impala/Hive string literals > --------------------------- > > Key: TEIID-3692 > URL: https://issues.jboss.org/browse/TEIID-3692 > Project: Teiid > Issue Type: Bug > Components: Misc. Connectors > Reporter: Don Krapohl > Assignee: Steven Hawkins > Fix For: 8.12, 8.11.4 > > > The Hive/Impala logic does not account for the source using c-style strings and will currently for string literals in the source sql use ansi style instead. Bind values are unaffected. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3694) Netezza translator - add additional support for other regexp functions

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3694?page=com.atlassian.jira.plugin... ] Van Halbert updated TEIID-3694: ------------------------------- Description: Support for LIKE_REGEX predicate was added, now would like to add support for the following: 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. was: 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. > Netezza translator - add additional support for other regexp functions > ---------------------------------------------------------------------- > > Key: TEIID-3694 > URL: https://issues.jboss.org/browse/TEIID-3694 > Project: Teiid > Issue Type: Enhancement > Components: Misc. Connectors > Reporter: Debbie Steigner > Assignee: Steven Hawkins > Fix For: 8.9 > > > Support for LIKE_REGEX predicate was added, now would like to add support for the following: > 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.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TEIID-3694) Netezza translator - add additional support for other regexp functions

by Van Halbert (JIRA)

Van Halbert created TEIID-3694: ---------------------------------- Summary: Netezza translator - add additional support for other regexp functions Key: TEIID-3694 URL: https://issues.jboss.org/browse/TEIID-3694 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.4.11#64026)

10 years, 6 months

1
0
0 / 0

[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... ] Steven Hawkins commented on TEIID-3125: --------------------------------------- > As a pushdown function. Knowing that the workaround is the UDF modeling exercise. A new issue should be logged to cover the additional functions, since it wasn't explicit with this issue - with the understanding that this would be pushdown support for Netezza and not general system functions. Also Designer, if it hasn't already, should have functionality for TEIID-2785. > 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.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ] Van Halbert commented on TEIID-3125: ------------------------------------ As a pushdown function. Knowing that the workaround is the UDF modeling exercise. > 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.4.11#64026)

10 years, 6 months

1
0
0 / 0

[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... ] Steven Hawkins commented on TEIID-3125: --------------------------------------- > What needs to be done to get the rest of the functions supported? Or are you saying, the user must model them as push down to make them work? It depends on what is meant by the level of support: As a UDF it's a modeling exercise. As a pushdown funciton, it's a minor amount of translator work. As system functions that can pushdown to Netezza it's a significant amount of work. > 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.4.11#64026)

10 years, 6 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 September 2015