[JBoss JIRA] Created: (TEIID-756) Oracle Connector is not producing the correct queries when using a LIMIT clause
by Larry O'Leary (JIRA)
Oracle Connector is not producing the correct queries when using a LIMIT clause
-------------------------------------------------------------------------------
Key: TEIID-756
URL: https://jira.jboss.org/jira/browse/TEIID-756
Project: Teiid
Issue Type: Bug
Components: JDBC Connector
Affects Versions: 6.1.0, 6.0.0, 6.2.0
Reporter: Larry O'Leary
Assignee: Steven Hawkins
When using a LIMIT clause in a query, the Oracle Connector rewrites it to something that Oracle will understand. The problem is that the rewritten version of the query is not returning the expected results.
For example:
SELECT INTKEY FROM BQT1.MEDIUMA LIMIT 50, 100
Should return 50 rows starting at row 100 but instead returns 0 rows when executed via the Oracle Connector. Currently the above query is rewritten as:
SELECT * FROM (SELECT VIEW_FOR_LIMIT.*, ROWNUM ROWNUM_ FROM (SELECT MediumA.IntKey FROM MediumA) VIEW_FOR_LIMIT WHERE ROWNUM <= 150) WHERE ROWNUM_ > 50
Further more, the rewritten version of the query is also projecting a column named ROWNUM_ which would be invalid based on our query processing.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Updated: (TEIID-962) Create new system function to dump temp table contents to file.
by Steve Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIID-962?page=com.atlassian.jira.plugin.sy... ]
Steve Hawkins updated TEIID-962:
--------------------------------
Fix Version/s: 7.1
Affects Version/s: 6.0.0
The file resource adapter will also have the ability to save. The save will be relative to the configured parent directory. I would also add a textagg aggregate function to handle the creation of a csv clob:
textagg(expression [as name], ... [DELIMITER char] [QUOTE char] [HEADER] [order by ...])
when header is specified, then all expression must be column references or have names.
usage example:
<file model>.saveFile('newFile.csv', (select textagg(col1, col2, col3 HEADER) from t))
> Create new system function to dump temp table contents to file.
> -----------------------------------------------------------------
>
> Key: TEIID-962
> URL: https://jira.jboss.org/browse/TEIID-962
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Affects Versions: 6.0.0
> Environment: All
> Reporter: Ken Johnson
> Assignee: Steve Hawkins
> Fix For: 7.1
>
>
> A requirement to produce a CSV file reflecting the contents of a query result set so it can be subsequently FTP'd or email'd. In Nov 07 implemented this feature using the exec connector, a shell script and mods to JDBCISQL.
> Suggested capability: function will take the following parameters:
> - Temp table name as string
> - Target file name (path qualified) as string
> - Delimiter as string
> When invoked, the specified temp table contents will be written out to the specified file using the specified delimiter to separate the column values.
> This generic capability will allow the CSV file thats needed and subsequently process it with other UDF functionality as necessary.
> Open questions:
> 1. How does file path behave in a clustered environment? Is it relative to the MM Server install dir or fully qualified?
> Suggest this feature remain undocumented for the short term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Assigned: (TEIID-962) Create new system function to dump temp table contents to file.
by Steve Hawkins (JIRA)
[ https://jira.jboss.org/browse/TEIID-962?page=com.atlassian.jira.plugin.sy... ]
Steve Hawkins reassigned TEIID-962:
-----------------------------------
Assignee: Steve Hawkins
> Create new system function to dump temp table contents to file.
> -----------------------------------------------------------------
>
> Key: TEIID-962
> URL: https://jira.jboss.org/browse/TEIID-962
> Project: Teiid
> Issue Type: Feature Request
> Components: Query Engine
> Environment: All
> Reporter: Ken Johnson
> Assignee: Steve Hawkins
>
> A requirement to produce a CSV file reflecting the contents of a query result set so it can be subsequently FTP'd or email'd. In Nov 07 implemented this feature using the exec connector, a shell script and mods to JDBCISQL.
> Suggested capability: function will take the following parameters:
> - Temp table name as string
> - Target file name (path qualified) as string
> - Delimiter as string
> When invoked, the specified temp table contents will be written out to the specified file using the specified delimiter to separate the column values.
> This generic capability will allow the CSV file thats needed and subsequently process it with other UDF functionality as necessary.
> Open questions:
> 1. How does file path behave in a clustered environment? Is it relative to the MM Server install dir or fully qualified?
> Suggest this feature remain undocumented for the short term.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Resolved: (TEIID-974) XML-Relational connectors have trouble with reponse XMLs that contain DTD reference
by Ramesh Reddy (JIRA)
[ https://jira.jboss.org/browse/TEIID-974?page=com.atlassian.jira.plugin.sy... ]
Ramesh Reddy resolved TEIID-974.
--------------------------------
Resolution: Won't Fix
The challenge here is by time the XML is parsed and loaded, the processing is happening at the "engine" level, where all the references to original URL location are not there to get it from the correct place. If we decide to do this at the connector level, then Teiid need to load the document, i.e memory hog. Since this is relatively low frequency use case with file and http connectors, the workaround is fine. We just need to document as KI. Reopen if you feel otherwise.
> XML-Relational connectors have trouble with reponse XMLs that contain DTD reference
> -----------------------------------------------------------------------------------
>
> Key: TEIID-974
> URL: https://jira.jboss.org/browse/TEIID-974
> Project: Teiid
> Issue Type: Bug
> Components: Misc. Connectors
> Affects Versions: 6.2.0, 7.1
> Reporter: John Doyle
> Assignee: Ramesh Reddy
> Fix For: 7.0
>
>
> Whenever we tried to query the document with the XML-Relational HTTP Connector, the following error occured:
> java.io.FileNotFoundException: <designer_home>/<docname>_XML.dtd (No such file or directory).
> What it looks like is happening is that this XML document contains a relative reference to a DTD, but instead we look for it in the working directory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months