Mailing-List: contact dev-help@phoenix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@phoenix.apache.org
Date: Thu, 20 Jul 2017 21:02:00 +0000 (UTC)
From: "Samarth Jain (JIRA)" <jira@apache.org>
To: dev@phoenix.apache.org
Message-ID: <JIRA.13026589.1481180467000.296625.1500584520263@Atlassian.JIRA>
In-Reply-To: <JIRA.13026589.1481180467000@Atlassian.JIRA>
References: <JIRA.13026589.1481180467000@Atlassian.JIRA> <JIRA.13026589.1481180467565@jira-lw-us.apache.org>
Subject: [jira] [Commented] (PHOENIX-3525) Cap automatic index rebuilding to
 inactive timestamp.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 20 Jul 2017 21:02:04 -0000


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

Samarth Jain commented on PHOENIX-3525:
---------------------------------------

Ah, I didn't know that. The documentation completely tripped me. I will make sure to leave the lock acquisition as it is then.

The internal code doc does say the following though:

{code}
/**
   *
   * Get a row lock for the specified row. All locks are reentrant.
   *
   * Before calling this function make sure that a region operation has already been
   * started (the calling thread has already acquired the region-close-guard lock).
   * @param row The row actions will be performed against
   * @param readLock is the lock reader or writer. True indicates that a non-exlcusive
   *                 lock is requested
   */
{code}

So looks like we need to provide another guard with region.startRegionOperation().


> Cap automatic index rebuilding to inactive timestamp.
> -----------------------------------------------------
>
>                 Key: PHOENIX-3525
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3525
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Ankit Singhal
>         Attachments: PHOENIX-3525_wip.patch
>
>
> From [~chrajeshbabu32@gmail.com] review comment on 
> https://github.com/apache/phoenix/pull/210
> For automatic rebuilding ,DISABLED_TIMESTAMP is lower bound but there is no upper bound so we are going rebuild all the new writes written after DISABLED_TIMESTAMP even though indexes updated properly. So we can introduce an upper bound of time where we are going to start a rebuild thread so we can limit the data to rebuild. In case If there are frequent writes then we can increment the rebuild period exponentially


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