Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Wed, 26 Apr 2017 18:49:04 +0000 (UTC)
From: "Matthew Van Wely (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13067140.1493232499000.58614.1493232544125@Atlassian.JIRA>
In-Reply-To: <JIRA.13067140.1493232499000@Atlassian.JIRA>
References: <JIRA.13067140.1493232499000@Atlassian.JIRA> <JIRA.13067140.1493232499294@jira-lw-us.apache.org>
Subject: [jira] [Created] (PHOENIX-3813) Allow reads on a disabled index to
 avoid blocking both read and write when index is out of sync with table.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 26 Apr 2017 18:49:08 -0000

Matthew Van Wely created PHOENIX-3813:
-----------------------------------------

             Summary: Allow reads on a disabled index to avoid blocking both read and write when index is out of sync with table.
                 Key: PHOENIX-3813
                 URL: https://issues.apache.org/jira/browse/PHOENIX-3813
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Matthew Van Wely
            Priority: Minor


Some use cases could benefit from the ability to read from a Phoenix index which has been marked disabled, because a write to the index failed.  While the missed events are being replayed, it would be useful for the index to allow reads. 

This is likely use case specific and could be something that the index defines at creation.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)