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 39B09200CD3 for ; Fri, 14 Jul 2017 03:24:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 380A116D293; Fri, 14 Jul 2017 01:24:04 +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 7CB7816D291 for ; Fri, 14 Jul 2017 03:24:03 +0200 (CEST) Received: (qmail 44744 invoked by uid 500); 14 Jul 2017 01:24:02 -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 44733 invoked by uid 99); 14 Jul 2017 01:24:02 -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; Fri, 14 Jul 2017 01:24:02 +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 37A4D1806D2 for ; Fri, 14 Jul 2017 01:24:02 +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 zcjVEyO7w0o6 for ; Fri, 14 Jul 2017 01:24:01 +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 3884C5FD81 for ; Fri, 14 Jul 2017 01:24:01 +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 B5FC5E0D60 for ; Fri, 14 Jul 2017 01:24:00 +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 1397724748 for ; Fri, 14 Jul 2017 01:24:00 +0000 (UTC) Date: Fri, 14 Jul 2017 01:24:00 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (PHOENIX-4023) Handle drop of shared index when UPDATE_CACHE_FREQUENCY is set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 14 Jul 2017 01:24:04 -0000 [ https://issues.apache.org/jira/browse/PHOENIX-4023?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16086698#comment-16086698 ] James Taylor edited comment on PHOENIX-4023 at 7/14/17 1:23 AM: ---------------------------------------------------------------- Thoughts, [~lhofhansl], [~sukunaidu@gmail.com], [~tdsilva]? was (Author: jamestaylor): Thoughts, [~lhofhansl], [~sukunaidu@gmail.com]? > Handle drop of shared index when UPDATE_CACHE_FREQUENCY is set > -------------------------------------------------------------- > > Key: PHOENIX-4023 > URL: https://issues.apache.org/jira/browse/PHOENIX-4023 > Project: Phoenix > Issue Type: Bug > Reporter: James Taylor > > When UPDATE_CACHE_FREQUENCY is set, a client will continue to use a shared index (i.e. local index or view index). This is not good because once it's dropped, it will stop being maintained which will lead to incorrect query results. > Some potential options: > # Ignore UPDATE_CACHE_FREQUENCY if a table has a shared index. Not great because it defeats the purpose of the feature. > # Delay the index actually being dropped (or at least the stopping of the maintenance) until the cache frequency passes. Makes some assumptions about the UPDATE_CACHE_FREQUENCY as it could vary on a connection by connection basis. > #. Do nothing and let the index continue to be used (figuring it's usage will stop when the UPDATE_CACHE_FREQUENCY occurs and that's the cost of using this feature). > Option #2 seems the most viable. Perhaps a separate config for how long to continue to do index maintenance after an index is dropped. -- This message was sent by Atlassian JIRA (v6.4.14#64029)