Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 752D7200D3E for ; Thu, 2 Nov 2017 06:24:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 6D499160BFA; Thu, 2 Nov 2017 05:24:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id B13A4160BEA for ; Thu, 2 Nov 2017 06:24:08 +0100 (CET) Received: (qmail 21856 invoked by uid 500); 2 Nov 2017 05:24:07 -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 21845 invoked by uid 99); 2 Nov 2017 05:24:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Nov 2017 05:24:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EBE2518440D for ; Thu, 2 Nov 2017 05:24:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 6FITw4593moL for ; Thu, 2 Nov 2017 05:24:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 95ADA5FE0E for ; Thu, 2 Nov 2017 05:24:05 +0000 (UTC) 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 E5B10E0A3A for ; Thu, 2 Nov 2017 05:24:03 +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 689A324415 for ; Thu, 2 Nov 2017 05:24:01 +0000 (UTC) Date: Thu, 2 Nov 2017 05:24:01 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-4323) LocalIndexes could fail if your data row is not in the same region as your index region MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 02 Nov 2017 05:24:09 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-4323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235199#comment-16235199 ] James Taylor commented on PHOENIX-4323: --------------------------------------- Like I commented before, whether adding a 0 byte helps or not depends on the row key. It's not clear if this makes things very much unlikely. You need to consider the data table schema. We should think more on this one. > LocalIndexes could fail if your data row is not in the same region as your index region > --------------------------------------------------------------------------------------- > > Key: PHOENIX-4323 > URL: https://issues.apache.org/jira/browse/PHOENIX-4323 > Project: Phoenix > Issue Type: Bug > Reporter: churro morales > Assignee: Vincent Poon > Priority: Major > Attachments: LocalIndexIT.java > > > This is not likely to happen, but if this does your data table and index write will never succeed. > In HRegion.doMiniBatchMutation() > You create index rows in the preBatchMutate() then when you call checkRow() on that index row the exception will bubble up if the index row is not in the same region as your data row. > Like I said this is unlikely, but you would have to do a region merge to fix this issue if encountered. > [~vincentpoon] has a test which he will attach to this JIRA showing an example how this can happen. The write will never succeed unless you merge regions if this ever happens. -- This message was sent by Atlassian JIRA (v6.4.14#64029)