Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Fri, 23 Jan 2015 16:40:42 +0000 (UTC)
From: "Jacques Nadeau (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12769543.1421992004000.157811.1422031242875@Atlassian.JIRA>
In-Reply-To: <JIRA.12769543.1421992004000@Atlassian.JIRA>
References: <JIRA.12769543.1421992004000@Atlassian.JIRA>
 <JIRA.12769543.1421992004366@arcas>
Subject: [jira] [Commented] (DRILL-2059) Support push-down of Filters with
 conditions on a composite row_key
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jacques Nadeau commented on DRILL-2059:
---------------------------------------

This seems like an optimizer that would be specific to HBase. Can you please expound on how you see this as a general planning enhancement rather than just a new rule that the HBase storage plugin implements?

> Support push-down of Filters with conditions on a composite row_key
> -------------------------------------------------------------------
>
>                 Key: DRILL-2059
>                 URL: https://issues.apache.org/jira/browse/DRILL-2059
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Query Planning & Optimization, Storage - HBase
>            Reporter: Aditya Kishore
>            Assignee: Aditya Kishore
>
> If the HBase row_key stores multiple columns and a filter condition is specified on one or more of these columns, we should be able to push down the filter to HBase scan.


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