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 1DD7A200B84 for ; Tue, 20 Sep 2016 21:04:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1C79C160AC0; Tue, 20 Sep 2016 19:04:25 +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 5AE86160AC9 for ; Tue, 20 Sep 2016 21:04:24 +0200 (CEST) Received: (qmail 91901 invoked by uid 500); 20 Sep 2016 19:04:23 -0000 Mailing-List: contact issues-help@carbondata.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@carbondata.incubator.apache.org Delivered-To: mailing list issues@carbondata.incubator.apache.org Received: (qmail 91892 invoked by uid 99); 20 Sep 2016 19:04:23 -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; Tue, 20 Sep 2016 19:04:23 +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 2E6471804D2 for ; Tue, 20 Sep 2016 19:04:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.646 X-Spam-Level: X-Spam-Status: No, score=-4.646 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id nPVSU1tSBM3m for ; Tue, 20 Sep 2016 19:04:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 831F860D39 for ; Tue, 20 Sep 2016 19:04:21 +0000 (UTC) Received: (qmail 91739 invoked by uid 99); 20 Sep 2016 19:04:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Sep 2016 19:04:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 74E0C2C2A61 for ; Tue, 20 Sep 2016 19:04:20 +0000 (UTC) Date: Tue, 20 Sep 2016 19:04:20 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@carbondata.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CARBONDATA-261) clean files is updating the stale segments to the table status. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 20 Sep 2016 19:04:25 -0000 [ https://issues.apache.org/jira/browse/CARBONDATA-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15507462#comment-15507462 ] ASF GitHub Bot commented on CARBONDATA-261: ------------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/incubator-carbondata/pull/181 > clean files is updating the stale segments to the table status. > --------------------------------------------------------------- > > Key: CARBONDATA-261 > URL: https://issues.apache.org/jira/browse/CARBONDATA-261 > Project: CarbonData > Issue Type: Bug > Components: data-load, data-query > Affects Versions: 0.1.0-incubating > Reporter: ravikiran > Assignee: ravikiran > Fix For: 0.2.0-incubating > > > in clean files it will read the table status first and it will delete the physical locations and update the table metadata and then take the lock for writing and after that it will write the old read list to the file. > but this is wrong as in the time between the read and write the table status would have been changed. > so before writing it should read the table status again and update the changes and then write. -- This message was sent by Atlassian JIRA (v6.3.4#6332)