Bug 1296583
| Summary: | Redshift - RS does not support ASCII function | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Virtualization 6 | Reporter: | Juraj Duráni <jdurani> |
| Component: | Teiid | Assignee: | Van Halbert <vhalbert> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Juraj Duráni <jdurani> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.3.0 | CC: | aszczucz, blafond, jolee, mbaluch, thauser, vhalbert |
| Target Milestone: | ER1 | ||
| Target Release: | 6.3.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: |
driver - PostgreSQL 9.2
translator - postgresql
|
|
| Last Closed: | 2016-08-24 11:46:14 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Steven Hawkins <shawkins> updated the status of jira TEIID-3887 to Resolved Note: a new redshift translator has been created to account for the different capabilities than the postgresql translator. |
Description of problem: Redshift database does not support ASCII function E.g. *SELECT INTKEY, ASCII(INTKEY) FROM BQT1.SmallA ORDER BY INTKEY* is translated as *SELECT g_0.intkey AS c_0, ascii(cast(g_0.intkey AS varchar(4000))) AS c_1 FROM smalla AS g_0 ORDER BY c_0* Result: Caused by: org.postgresql.util.PSQLException: ERROR: Specified types or functions (one per INFO message) not supported on Redshift tables. Steps to Reproduce: <vdb name="test" version="1"> <model name="Source" type="PHYSICAL"> <source name="rs" connection-jndi-name="java:/Redshift" translator-name="postgresql"/> <metadata type="DDL"> <![CDATA[create foreign table SmallA ( intkey integer OPTIONS(NAMEINSOURCE 'intkey', NATIVE_TYPE 'int4'), timevalue timestamp OPTIONS(NAMEINSOURCE 'timevalue', NATIVE_TYPE 'timestamp')) OPTIONS(NAMEINSOURCE 'smalla'); ]]> </metadata> </model> </vdb> Actual results: Expected results: Additional info: