Return-Path: 
 <user-return-45636-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-user-archive@www.apache.org
Delivered-To: apmail-hbase-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3F85317E58
	for <apmail-hbase-user-archive@www.apache.org>;
 Thu,  2 Oct 2014 19:46:54 +0000 (UTC)
Received: (qmail 28389 invoked by uid 500); 2 Oct 2014 19:46:52 -0000
Delivered-To: apmail-hbase-user-archive@hbase.apache.org
Received: (qmail 28318 invoked by uid 500); 2 Oct 2014 19:46:52 -0000
Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hbase.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hbase.apache.org>
List-Post: <mailto:user@hbase.apache.org>
List-Id: <user.hbase.apache.org>
Reply-To: user@hbase.apache.org
Delivered-To: mailing list user@hbase.apache.org
Received: (qmail 28306 invoked by uid 99); 2 Oct 2014 19:46:52 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 19:46:52 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of serega.sheypak@gmail.com
 designates 209.85.215.44 as permitted sender)
Received: from [209.85.215.44] (HELO mail-la0-f44.google.com) (209.85.215.44)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Oct 2014 19:46:46 +0000
Received: by mail-la0-f44.google.com with SMTP id gb8so3124483lab.3
        for <user@hbase.apache.org>; Thu, 02 Oct 2014 12:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=u8978T3YiyTpRisnNxEX1g/SV4HRg+qR2riBWDGF5wA=;
        b=BEQEwBbupSbUCFyDdvItM9jW2m4MflshWkjm4f4NhLxzft7Rb4yT2OGWmutmtRfSMP
         IXHlxsifh3H6yg7uoylCZiisY73KEPRYwwCcIQWpp9Jsv964z0ggY8NF7akkr6COq73E
         fxVfDDaTxi6hIxsYMGi4K9LLQ8kOKB97xZ0bFV7CYNmG4RyIYb3FKRTq300oRuP7dsLt
         ySJ2mUt7H8/YwhDTy0lm7A21Fw4PBhfREj2zGpccZJWGnF7ufSmHXdouW508SlegJclQ
         QSjXH5A9eFhdWFxNnNItnssTBzY6ILBrMBFPP7D0U/Wgk73uzsIFx7JvHpULXUeYYmjD
         Vz3w==
X-Received: by 10.112.163.103 with SMTP id yh7mr809976lbb.73.1412279185352;
 Thu, 02 Oct 2014 12:46:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.157.131 with HTTP; Thu, 2 Oct 2014 12:46:05 -0700 (PDT)
From: Serega Sheypak <serega.sheypak@gmail.com>
Date: Thu, 2 Oct 2014 23:46:05 +0400
Message-ID: 
 <CABNOTEXbXQNH-XhEaEZZ9+GNmHpHYhLGFz==-bbbYwUaMitGww@mail.gmail.com>
Subject: Get default split policy
To: user <user@hbase.apache.org>
Content-Type: multipart/alternative; boundary=089e011832942aaf2e050475df00
X-Virus-Checked: Checked by ClamAV on apache.org

--089e011832942aaf2e050475df00
Content-Type: text/plain; charset=UTF-8

Hi,  is that true that I can set split policy per cluster or per table?
How can I get current split policy for cluster/table?

--089e011832942aaf2e050475df00--