Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Mon, 31 Aug 2015 22:13:45 +0000 (UTC)
From: "Devaraj Das (JIRA)" <jira@apache.org>
To: dev@phoenix.incubator.apache.org
Message-ID: <JIRA.12860828.1441059175000.215188.1441059225856@Atlassian.JIRA>
In-Reply-To: <JIRA.12860828.1441059175000@Atlassian.JIRA>
References: <JIRA.12860828.1441059175000@Atlassian.JIRA>
 <JIRA.12860828.1441059175003@arcas>
Subject: [jira] [Created] (PHOENIX-2221) Option to make data regions not
 writable when index regions are not available
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Devaraj Das created PHOENIX-2221:
------------------------------------

             Summary: Option to make data regions not writable when index regions are not available
                 Key: PHOENIX-2221
                 URL: https://issues.apache.org/jira/browse/PHOENIX-2221
             Project: Phoenix
          Issue Type: Improvement
            Reporter: Devaraj Das


In one usecase, it was deemed better to not accept writes when the index regions are unavailable for any reason (as opposed to disabling the index and the queries doing bigger data-table scans).
The idea is that the index regions are kept consistent with the data regions, and when a query runs against the index regions, one can be reasonably sure that the query ran with the most recent data in the data regions. When the index regions are unavailable, the writes to the data table are rejected. Read queries off of the index regions would have deterministic performance (and on the other hand if the index is disabled, then the read queries would have to go to the data regions until the indexes are rebuilt, and the queries would suffer).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)