From issues-return-6575-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Fri May 3 20:55:03 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 EB93218064D for ; Fri, 3 May 2019 22:55:02 +0200 (CEST) Received: (qmail 77786 invoked by uid 500); 3 May 2019 20:55:02 -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 77698 invoked by uid 99); 3 May 2019 20:55:02 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 May 2019 20:55:02 +0000 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 0D06FE2B90 for ; Fri, 3 May 2019 20:55:01 +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 5A10225820 for ; Fri, 3 May 2019 20:55:00 +0000 (UTC) Date: Fri, 3 May 2019 20:55:00 +0000 (UTC) From: "Geoffrey Jacoby (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4703) Provide an option to fully rebuild indexes asynchronously through SQL MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-4703?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 832822#comment-16832822 ]=20 Geoffrey Jacoby commented on PHOENIX-4703: ------------------------------------------ [~giskender] - I +1'ed on the PR, but you could please submit a patch for t= he test run? Also, please check to make sure your patch works with the 4.x = branches and if not please submit a backport. Thanks! > Provide an option to fully rebuild indexes asynchronously through SQL > --------------------------------------------------------------------- > > Key: PHOENIX-4703 > URL: https://issues.apache.org/jira/browse/PHOENIX-4703 > Project: Phoenix > Issue Type: Bug > Reporter: Vincent Poon > Assignee: Gokcen Iskender > Priority: Major > Time Spent: 4h 50m > Remaining Estimate: 0h > > Currently if we run "ALTER INDEX ... REBUILD" , all the rows in the index= are deleted and the index is rebuilt synchronously. > "ALTER INEX ... REBUILD ASYNC" seems to be used for the IndexTool's parti= al rebuild option, rebuilding from ASYNC_REBUILD_TIMESTAMP (PHOENIX-2890) > So it seems currently the only way to fully rebuild is the drop the index= , and recreate it.=C2=A0 This is burdensome as it requires have the schema = DDL. > We should have an option to fully rebuild asynchronously, that has the sa= me semantics as dropping and recreating the index.=C2=A0 A further advantag= e of this is we can maintain the splits of the index table while dropping i= ts data.=C2=A0 We are currently seeing issues where rebuilding a large tabl= e via a MR job results in hotspotting due to all data regions writing to th= e same index region at the start. > =C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)