Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Mon, 17 Jul 2017 18:00:00 +0000 (UTC)
From: "Samarth Jain (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13087335.1500075919000.265133.1500314400149@Atlassian.JIRA>
In-Reply-To: <JIRA.13087335.1500075919000@Atlassian.JIRA>
References: <JIRA.13087335.1500075919000@Atlassian.JIRA> <JIRA.13087335.1500075919986@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-4028) Provide option to not throw index
 write failure back to client
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 17 Jul 2017 18:00:04 -0000


    [ https://issues.apache.org/jira/browse/PHOENIX-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090181#comment-16090181 ] 

Samarth Jain commented on PHOENIX-4028:
---------------------------------------

I think it is worth testing that the phoenix connection we get for index rebuild works correctly when namespace mapping is enabled. There was one mistake in my comment - the last two parameters were the same. One should have false for name space mapping and the other should have true. +1 to the patch once that change is made. Thanks, [~jamestaylor]!

> Provide option to not throw index write failure back to client
> --------------------------------------------------------------
>
>                 Key: PHOENIX-4028
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4028
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: James Taylor
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4028.patch, PHOENIX-4028_v2.patch, PHOENIX-4028_v3.patch, PHOENIX-4028_wip.patch
>
>
> Much like our DISABLE_INDEX_ON_WRITE_FAILURE and REBUILD_INDEX_ON_WRITE_FAILURE table properties, we need a THROW_INDEX_WRITE_FAILURE boolean option that can be used to prevent the index write from being thrown back to the client. In this case, the index failure policy would still be executed (i.e. disabling the index on a write failure), but any retry logic for the client would be avoided. The index would be eventually consistent based on the background partial index rebuild thread.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)