You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/11/10 01:10:00 UTC

[jira] [Commented] (DRILL-6833) MapRDB queries with Run Time Filters with row_key/Secondary Index Should Support Pushdown

    [ https://issues.apache.org/jira/browse/DRILL-6833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16682123#comment-16682123 ] 

ASF GitHub Bot commented on DRILL-6833:
---------------------------------------

gparai opened a new pull request #1532: DRILL-6833: Support for pushdown of rowkey based joins
URL: https://github.com/apache/drill/pull/1532
 
 
   @amansinha100 can you please review the PR? Thanks!

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> MapRDB queries with Run Time Filters with row_key/Secondary Index Should Support Pushdown
> -----------------------------------------------------------------------------------------
>
>                 Key: DRILL-6833
>                 URL: https://issues.apache.org/jira/browse/DRILL-6833
>             Project: Apache Drill
>          Issue Type: New Feature
>    Affects Versions: 1.15.0
>            Reporter: Gautam Parai
>            Assignee: Gautam Parai
>            Priority: Major
>             Fix For: 1.15.0
>
>
> Drill should push down all row key filters to maprDB for queries that only have WHERE conditions on row_keys. In the following example, the query only has where clause on row_keys:
> select t.mscIdentities from dfs.root.`/user/mapr/MixTable` t where t.row_key=
> (select max(convert_fromutf8(i.KeyA.ENTRY_KEY)) from dfs.root.`/user/mapr/TableIMSI` i where i.row_key='460021050005636')
> row_keys can return at most 1 row. So the physical planning must leverage MapRDB row_key push down to execute the sub query, with its results execute the outer query. Currently only the inner query is pushed down. The outer query requires a table scan.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)