Bug 1530236 - Osisoft translator - correlated subquery on HAVING clause fails
Summary: Osisoft translator - correlated subquery on HAVING clause fails
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Data Virtualization 6
Classification: JBoss
Component: Teiid, Documentation
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: CR5
: 6.4.0
Assignee: David Le Sage
QA Contact: Andrej Smigala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-02 10:54 UTC by Andrej Smigala
Modified: 2018-02-27 10:30 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Running a query with a correlated subquery in a HAVING clause fails on the data source with an exception. This is due to an issue with the Osisoft PI data source.
Clone Of:
Environment:
Last Closed: 2018-02-19 04:34:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker TEIID-5193 0 Major Resolved Osisoft translator - correlated subquery on HAVING clause fails 2018-03-12 22:25:56 UTC

Description Andrej Smigala 2018-01-02 10:54:35 UTC 
Running a query with a correlated subquery in a HAVING clause, such as

SELECT INTKEY, STRINGKEY FROM BQT1.SMALLA AS A WHERE NOT (INTKEY IN (10)) GROUP BY INTKEY, STRINGKEY HAVING INTKEY = (SELECT MIN(STRINGKEY) FROM BQT1.SMALLA AS B WHERE A.INTKEY = B.INTKEY) 

fails on the datasource with

    com.osisoft.rdsa.RdsaException: [PIOLEDBENT] HAVING condition cannot be nonaggregate.

This seems to be an issue on the Osisoft PI datasource side, as running the query directly against the datasource produces the same failure.
Comment 2 Andrej Smigala 2018-01-09 14:29:25 UTC 
You're right, but I think it's still worth documenting as a known issue.
Comment 7 David Le Sage 2018-02-19 04:12:04 UTC 
Release note drafted.
Comment 8 David Le Sage 2018-02-19 04:34:33 UTC 
Release note added.
Engineering aspect set to WONTFIX for this release.
Note You need to log in before you can comment on or make changes to this bug.