You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Robert DeVito (JIRA)" <ji...@apache.org> on 2016/09/21 23:57:20 UTC

[jira] [Created] (DRILL-4900) Query across Sybase and Oracle plugins is dropping WHERE clause

Robert DeVito created DRILL-4900:
------------------------------------

             Summary: Query across Sybase and Oracle plugins is dropping WHERE clause
                 Key: DRILL-4900
                 URL: https://issues.apache.org/jira/browse/DRILL-4900
             Project: Apache Drill
          Issue Type: Bug
          Components: Client - JDBC, Storage - JDBC
    Affects Versions: 1.6.0
         Environment: Windows client. Sybase and Oracle hosts on unix
            Reporter: Robert DeVito


Have tried several approaches of joining simple queries with Oracle and Sybase. In all cases, we have sufficient WHERE clause on each side to really limit data. Each time, the Drill execution plan skips the WHERE clause on one side.
ex:
select a.f, b.b
from
(
	select * from  pl1.`owner`.`dbo`.`VIEW1` d
	where d.fid = '0000300769'
	and d.PDate = ('2013-10-31') 
) a,
(
	select * from pl2.owner.VIEW2 v
	where v.f = '0000300769'
	and v.d = 'M'
	and v.b  IN ('UK221','UK222','UK223','UK224','UK225','UK227','08843','BU5552','BU5543','BU5544')
	and v.dk = '20131031'
) b
where a.f = b.f
and a.S   = b.S

Please ignore the obfuscated column names. Syntax is valid, but Drill keeps sending selects with no WHERE clause for one subquery or the other. Can't understand why, or how to control it. This is a make or break for us.

Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)