Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 08DDC200C7C for ; Mon, 5 Jun 2017 22:55:08 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 07648160BE1; Mon, 5 Jun 2017 20:55:08 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4DEE0160BBB for ; Mon, 5 Jun 2017 22:55:07 +0200 (CEST) Received: (qmail 40022 invoked by uid 500); 5 Jun 2017 20:55:05 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 40011 invoked by uid 99); 5 Jun 2017 20:55:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 05 Jun 2017 20:55:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 88175C12A8 for ; Mon, 5 Jun 2017 20:55:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id sgsMTzpUZqXr for ; Mon, 5 Jun 2017 20:55:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CDA995F36B for ; Mon, 5 Jun 2017 20:55:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 5D92EE0041 for ; Mon, 5 Jun 2017 20:55:04 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1A85921E0B for ; Mon, 5 Jun 2017 20:55:04 +0000 (UTC) Date: Mon, 5 Jun 2017 20:55:04 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (HBASE-18165) Predicate based deletion during major compactions MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 05 Jun 2017 20:55:08 -0000 Lars Hofhansl created HBASE-18165: ------------------------------------- Summary: Predicate based deletion during major compactions Key: HBASE-18165 URL: https://issues.apache.org/jira/browse/HBASE-18165 Project: HBase Issue Type: Brainstorming Reporter: Lars Hofhansl In many cases it is expensive to place a delete per version, column, or family. HBase should have way to specify a predicate and remove all Cells matching the predicate during the next compactions (major and minor). Nothing more concrete. The tricky part would be to know when it is safe to remove the predicate, i.e. when we can be sure that all Cells matching the predicate actually have been removed. Could potentially use HBASE-12859 for that. -- This message was sent by Atlassian JIRA (v6.3.15#6346)