[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.
by Debbie Steigner (JIRA)
[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ]
Debbie Steigner commented on TEIID-3125:
----------------------------------------
Ramesh, yes it does and that is what they are currently using as a workaround. The customer requests a generic solution which is implemented with the
already available LIKE_REGEX predicate in the TEIDD SQL language.
> Netezza translator - add support for the LIKE_REGEX predicate.
> --------------------------------------------------------------
>
> Key: TEIID-3125
> URL: https://issues.jboss.org/browse/TEIID-3125
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> 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, 4 months
[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 updated TEIID-3116:
----------------------------------
Priority: Minor (was: Critical)
Workaround Description: Set the database version on the translator.
Workaround: Workaround Exists
It's much easier to address this as a doc issue. The rationales for not letting planning proceed is that we don't want to end up caching an invalid plan and there can be variations in planning based upon the database version (although that's more of a limitation of the design of partial results, such that it's not aware of performing aggregation for example).
> 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, 4 months
[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ]
Ramesh Reddy commented on TEIID-3125:
-------------------------------------
Creating a push down function on model did not work? That can be a workaround.
> Netezza translator - add support for the LIKE_REGEX predicate.
> --------------------------------------------------------------
>
> Key: TEIID-3125
> URL: https://issues.jboss.org/browse/TEIID-3125
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> 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, 4 months
[JBoss JIRA] (TEIID-3125) Netezza translator - add support for the LIKE_REGEX predicate.
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIID-3125?page=com.atlassian.jira.plugin... ]
Ramesh Reddy updated TEIID-3125:
--------------------------------
Description:
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.
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.
Our client (ASML) has installed 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 support for the LIKE_REGEX predicate.
> --------------------------------------------------------------
>
> Key: TEIID-3125
> URL: https://issues.jboss.org/browse/TEIID-3125
> Project: Teiid
> Issue Type: Feature Request
> Components: Misc. Connectors
> Reporter: Debbie Steigner
> Assignee: Steven Hawkins
>
> 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, 4 months
[JBoss JIRA] (TEIID-3123) Exception when using dense_rank() in Teiid Development
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3123?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3123:
---------------------------------------
Actually this is more of a SQL Server limitation as the same sql works fine when processed in Teiid, Oracle, etc. With rank/dense_rank we can replace the whole window function with constant, but that won't work for row_number, so we'll at least need additional SQL Server translator logic.
> Exception when using dense_rank() in Teiid Development
> ------------------------------------------------------
>
> Key: TEIID-3123
> URL: https://issues.jboss.org/browse/TEIID-3123
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.8
> Reporter: Joseph CHIDIAC
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.9, 9.x
>
>
> SELECT DISTINCT
> subQueryTable.jiraissue_ASSIGNEE AS jiraissue_ASSIGNEE,
> dense_rank() over(order by subQueryTable.jiraissue_ID DESC) as CalculatedField1
> FROM jiraissue
> LEFT OUTER JOIN
> (SELECT jiraissue_sub.ASSIGNEE AS jiraissue_ASSIGNEE,
> COUNT(IFNULL(jiraissue_sub.ID, -2147483648))
> AS jiraissue_ID
> FROM jiraissue jiraissue_sub
> WHERE ((jiraissue_sub.RESOLUTIONDATE BETWEEN NULL
> AND PARSETIMESTAMP(
> '2014-09-10 18:46:28',
> 'yyyy-MM-dd HH:mm:ss')))
> GROUP BY jiraissue_sub.ASSIGNEE) subQueryTable
> ON jiraissue.ASSIGNEE =
> subQueryTable.jiraissue_ASSIGNEE
>
> The query sent to the JDBC :
> SELECT DISTINCT DENSE_RANK() OVER (ORDER BY NULL DESC) FROM "JIRADB"."dbo"."jiraissue" g_0
>
> and i got this error :
>
> java.sql.SQLException: Windowed functions do not support constants as ORDER BY clause expressions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3123) Exception when using dense_rank() in Teiid Development
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3123?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-3123:
---------------------------------------
Rule raise null is projecting nulls upwards into the plan without ensuring that the plan is correct. We should be able to just use a different order by key instead.
> Exception when using dense_rank() in Teiid Development
> ------------------------------------------------------
>
> Key: TEIID-3123
> URL: https://issues.jboss.org/browse/TEIID-3123
> Project: Teiid
> Issue Type: Bug
> Components: Query Engine
> Affects Versions: 8.8
> Reporter: Joseph CHIDIAC
> Assignee: Steven Hawkins
> Fix For: 8.8, 8.9, 9.x
>
>
> SELECT DISTINCT
> subQueryTable.jiraissue_ASSIGNEE AS jiraissue_ASSIGNEE,
> dense_rank() over(order by subQueryTable.jiraissue_ID DESC) as CalculatedField1
> FROM jiraissue
> LEFT OUTER JOIN
> (SELECT jiraissue_sub.ASSIGNEE AS jiraissue_ASSIGNEE,
> COUNT(IFNULL(jiraissue_sub.ID, -2147483648))
> AS jiraissue_ID
> FROM jiraissue jiraissue_sub
> WHERE ((jiraissue_sub.RESOLUTIONDATE BETWEEN NULL
> AND PARSETIMESTAMP(
> '2014-09-10 18:46:28',
> 'yyyy-MM-dd HH:mm:ss')))
> GROUP BY jiraissue_sub.ASSIGNEE) subQueryTable
> ON jiraissue.ASSIGNEE =
> subQueryTable.jiraissue_ASSIGNEE
>
> The query sent to the JDBC :
> SELECT DISTINCT DENSE_RANK() OVER (ORDER BY NULL DESC) FROM "JIRADB"."dbo"."jiraissue" g_0
>
> and i got this error :
>
> java.sql.SQLException: Windowed functions do not support constants as ORDER BY clause expressions.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-3124) InetAddress getLocalHost return UnknownHostException cause Teiid service start failed in JBoss Server
by Steven Hawkins (JIRA)
[ https://issues.jboss.org/browse/TEIID-3124?page=com.atlassian.jira.plugin... ]
Steven Hawkins updated TEIID-3124:
----------------------------------
Issue Type: Bug (was: Enhancement)
Fix Version/s: 8.7.1
8.9
Affects Version/s: 8.7
(was: 8.9)
> InetAddress getLocalHost return UnknownHostException cause Teiid service start failed in JBoss Server
> -----------------------------------------------------------------------------------------------------
>
> Key: TEIID-3124
> URL: https://issues.jboss.org/browse/TEIID-3124
> Project: Teiid
> Issue Type: Bug
> Components: Server
> Affects Versions: 8.7
> Environment: JDV 6.x
> Reporter: Kylin Soong
> Assignee: Kylin Soong
> Fix For: 8.7.1, 8.9
>
>
> After install JDV 6.0.0.GA via
> java -jar jboss-dv-installer-6.0.0.GA-redhat-4.jar
> start JDV throw the following exception cause some of servers start failed:
> ~~~
> 17:17:35,824 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.teiid.transport.jdbc: org.jboss.msc.service.StartException in service jboss.teiid.transport.jdbc: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> Caused by: org.teiid.core.TeiidRuntimeException: TEIID40065 Failed to resolve the bind address
> at org.teiid.transport.SocketConfiguration.resolveHostName(SocketConfiguration.java:82)
> at org.teiid.transport.SocketConfiguration.getHostAddress(SocketConfiguration.java:103)
> at org.teiid.transport.SocketListener.<init>(SocketListener.java:55)
> at org.teiid.jboss.TransportService.start(TransportService.java:157)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> 17:17:35,844 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.teiid.transport.odbc: org.jboss.msc.service.StartException in service jboss.teiid.transport.odbc: Failed to start service
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_55]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_55]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_55]
> Caused by: org.teiid.core.TeiidRuntimeException: TEIID40065 Failed to resolve the bind address
> at org.teiid.transport.SocketConfiguration.resolveHostName(SocketConfiguration.java:82)
> at org.teiid.transport.SocketConfiguration.getHostAddress(SocketConfiguration.java:103)
> at org.teiid.transport.SocketListener.<init>(SocketListener.java:55)
> at org.teiid.transport.ODBCSocketListener.<init>(ODBCSocketListener.java:43)
> at org.teiid.jboss.TransportService.start(TransportService.java:181)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA-redhat-1.jar:1.0.4.GA-redhat-1]
> ... 3 more
> ~~~
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months
[JBoss JIRA] (TEIID-2998) problems with DDL returned for dynamic vdb with google spreadsheet source
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIID-2998?page=com.atlassian.jira.plugin... ]
RH Bugzilla Integration commented on TEIID-2998:
------------------------------------------------
jolee(a)redhat.com changed the Status of [bug 1109421|https://bugzilla.redhat.com/show_bug.cgi?id=1109421] from NEW to ASSIGNED
> problems with DDL returned for dynamic vdb with google spreadsheet source
> -------------------------------------------------------------------------
>
> Key: TEIID-2998
> URL: https://issues.jboss.org/browse/TEIID-2998
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 8.4
> Reporter: Mark Drilling
> Attachments: ChromeSheet.png, FirefoxSheet.png, GoogleSpreadsheetJIRA.txt
>
>
> I am seeing inconsistent DDL returned for dynamic VDB with a google spreadsheet source. In the same google account, I created two spreadsheets. One was created in firefox browser, one was created in chrome browser (don't know why that matters)
> See the attached document showing a comparison of the dynamic VDBs and the DDL that I got back. The only difference is that the source was pointing to a different spreadsheet.
> Notice that the DDL for the "ChromeSheet" returns the concatenated datavalues for the column name. But it includes a NIS OPTION for the column name.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 4 months