Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D76D118686 for ; Fri, 31 Jul 2015 15:01:10 +0000 (UTC) Received: (qmail 52352 invoked by uid 500); 31 Jul 2015 15:01:05 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 52300 invoked by uid 500); 31 Jul 2015 15:01: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 52286 invoked by uid 99); 31 Jul 2015 15:01:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 Jul 2015 15:01:05 +0000 Date: Fri, 31 Jul 2015 15:01:05 +0000 (UTC) From: "Michael Segel (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-12853) distributed write pattern to replace ad hoc 'salting' MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-12853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14649304#comment-14649304 ] Michael Segel commented on HBASE-12853: ---------------------------------------- Lars, If I respond, I'll be called argumentative. If I don't respond, it will leave readers with the incorrect perception. Again, Apache does not indemnify the contributor, leaving you with risk. You need to balance that risk against the benefits of contributing. Its a lot simpler to say "Apache won't indemnify me..." than to continually having to write out long paragraphs as to why and what that really means. Either you get it or you don't. Most of the committers here don't run their own shop or have to deal with the business side of software. > distributed write pattern to replace ad hoc 'salting' > ----------------------------------------------------- > > Key: HBASE-12853 > URL: https://issues.apache.org/jira/browse/HBASE-12853 > Project: HBase > Issue Type: New Feature > Reporter: Michael Segel > Fix For: 2.0.0 > > > In reviewing HBASE-11682 (Description of Hot Spotting), one of the issues is that while 'salting' alleviated regional hot spotting, it increased the complexity required to utilize the data. > Through the use of coprocessors, it should be possible to offer a method which distributes the data on write across the cluster and then manages reading the data returning a sort ordered result set, abstracting the underlying process. > On table creation, a flag is set to indicate that this is a parallel table. > On insert in to the table, if the flag is set to true then a prefix is added to the key. e.g. - or On read (scan) for each region server defined, a separate scan is created adding the prefix. Since each scan will be in sort order, its possible to strip the prefix and return the lowest value key from each of the subsets. -- This message was sent by Atlassian JIRA (v6.3.4#6332)