From dev-return-56859-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Tue Jun 4 22:25:02 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 16AB8180763 for ; Wed, 5 Jun 2019 00:25:01 +0200 (CEST) Received: (qmail 19689 invoked by uid 500); 4 Jun 2019 22:25:01 -0000 Mailing-List: contact dev-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 dev@phoenix.apache.org Received: (qmail 19670 invoked by uid 99); 4 Jun 2019 22:25:01 -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; Tue, 04 Jun 2019 22:25:01 +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 E2EA6E2D05 for ; Tue, 4 Jun 2019 22:25:00 +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 6482C20FEB for ; Tue, 4 Jun 2019 22:25:00 +0000 (UTC) Date: Tue, 4 Jun 2019 22:25:00 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (PHOENIX-5315) Cross cluster replication of the base table only should be sufficient MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Purtell created PHOENIX-5315: --------------------------------------- Summary: Cross cluster replication of the base table only should be sufficient Key: PHOENIX-5315 URL: https://issues.apache.org/jira/browse/PHOENIX-5315 Project: Phoenix Issue Type: Improvement Reporter: Andrew Purtell When replicating Phoenix tables using the HBase cross cluster replication facility, it should be sufficient (and must, for correctness and avoidance of race conditions and inconsistencies) to replicate the base table only. On the sink cluster the replication client's application of mutations from the replication stream to the local base table should trigger all necessary index update operations. To the extent that won't happen now due to implementation details, those details should be reworked. This also has important efficiency benefits: no matter how many indexes are defined for a base table, only the base table updates need be replicated (presuming Phoenix schema is synchronized over all sites by some other external means). -- This message was sent by Atlassian JIRA (v7.6.3#76005)