Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id F31CC18D7E for ; Thu, 20 Aug 2015 04:06:46 +0000 (UTC) Received: (qmail 58812 invoked by uid 500); 20 Aug 2015 04:06:46 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 58646 invoked by uid 500); 20 Aug 2015 04:06:46 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 58449 invoked by uid 99); 20 Aug 2015 04:06:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Aug 2015 04:06:46 +0000 Date: Thu, 20 Aug 2015 04:06:46 +0000 (UTC) From: "Swarnim Kulkarni (JIRA)" To: dev@hive.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HIVE-11609) Capability to add a filter to hbase scan via composite key doesn't work MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Swarnim Kulkarni created HIVE-11609: --------------------------------------- Summary: Capability to add a filter to hbase scan via composite key doesn't work Key: HIVE-11609 URL: https://issues.apache.org/jira/browse/HIVE-11609 Project: Hive Issue Type: Bug Components: HBase Handler Reporter: Swarnim Kulkarni It seems like the capability to add filter to an hbase scan which was added as part of HIVE-6411 doesn't work. This is primarily because in the HiveHBaseInputFormat, the filter is added in the getsplits instead of getrecordreader. This works fine for start and stop keys but not for filter because a filter is respected only when an actual scan is performed. This is also related to the initial refactoring that was done as part of HIVE-3420. -- This message was sent by Atlassian JIRA (v6.3.4#6332)