From issues-return-6073-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Tue Apr 16 23:56:00 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B1094180630 for ; Wed, 17 Apr 2019 01:55:59 +0200 (CEST) Received: (qmail 78396 invoked by uid 500); 16 Apr 2019 23:55:53 -0000 Mailing-List: contact issues-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list issues@phoenix.apache.org Received: (qmail 78371 invoked by uid 99); 16 Apr 2019 23:55:53 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 16 Apr 2019 23:55:53 +0000 From: GitBox To: issues@phoenix.apache.org Subject: [GitHub] [phoenix] BinShi-SecularBird opened a new pull request #485: Add common utility function ScanUtil.splityKeyRangesByBoundaries() Message-ID: <155545894792.15211.7001400758748566616.gitbox@gitbox.apache.org> Date: Tue, 16 Apr 2019 23:55:47 -0000 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit BinShi-SecularBird opened a new pull request #485: Add common utility function ScanUtil.splityKeyRangesByBoundaries() URL: https://github.com/apache/phoenix/pull/485 #### What does this PR do? Which problem(s) does it fix and how? What does this PR add? #### Where should the reviewer start? Explain what should be set-up first in order to get the review started. Which page has to be viewed etc. #### How should this be manually tested? - [ ] Write down all - [ ] the steps a person - [ ] needs to take to test it. #### Documents ##### Screenshots (if appropriate) If this PR changes something that concerns UI changes, please post before and after screenshots here. ##### Other documents If you have any documents that have anything to do with this PR. #### Who should be notified? - [ ] Write down the name/department this branch needs - [ ] to be communicated to - [ ] Check the box(es) to indicate that it has been - [ ] communicated (add the label) #### What should happen on deployment? (check all that apply) - [x] The usual steps. - [ ] There are database changes, which should be run. - [ ] There are files that should be manually uploaded. #### Questions: - Does this require a blog post? - Does this require a knowledge base update? - Does support need training for this? - Does this has to be communicated to partners? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: users@infra.apache.org With regards, Apache Git Services