Return-Path: X-Original-To: apmail-atlas-dev-archive@minotaur.apache.org Delivered-To: apmail-atlas-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9687718D93 for ; Tue, 19 Jan 2016 05:42:41 +0000 (UTC) Received: (qmail 35714 invoked by uid 500); 19 Jan 2016 05:42:41 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 35666 invoked by uid 500); 19 Jan 2016 05:42:41 -0000 Mailing-List: contact dev-help@atlas.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@atlas.incubator.apache.org Delivered-To: mailing list dev@atlas.incubator.apache.org Received: (qmail 35655 invoked by uid 99); 19 Jan 2016 05:42:41 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 05:42:41 +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 170451804C9 for ; Tue, 19 Jan 2016 05:42:41 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.426 X-Spam-Level: X-Spam-Status: No, score=0.426 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id J79-YNeN8aqj for ; Tue, 19 Jan 2016 05:42:40 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 5DC61213AE for ; Tue, 19 Jan 2016 05:42:40 +0000 (UTC) Received: (qmail 35648 invoked by uid 99); 19 Jan 2016 05:42:39 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jan 2016 05:42:39 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id CCB562C14F0 for ; Tue, 19 Jan 2016 05:42:39 +0000 (UTC) Date: Tue, 19 Jan 2016 05:42:39 +0000 (UTC) From: "Shwetha G S (JIRA)" To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ATLAS-442) Hive model to handle cascaded deletes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Shwetha G S created ATLAS-442: --------------------------------- Summary: Hive model to handle cascaded deletes Key: ATLAS-442 URL: https://issues.apache.org/jira/browse/ATLAS-442 Project: Atlas Issue Type: Bug Reporter: Shwetha G S Ideally, hive model should be like this: type - attributes hive_table - ..., partitions(list), ... hive_partition - values(list), ... partitions attribute in hive_table is composite. Add partition is frequent in hive, and this would result in create new partition and add this reference to table. So, this results in create entity + update array for hive_table entity. Since the number of partitions can be large, we want to avoid updates to hive_table entity every time. Hence hive model is implemented now as: hive_table - ... hive_partition - table(hive_table), values(list), ... In this model, there is no way to indicate that partitions are composite attributes of table and hence deleting table will nor result in deleting of partitions. But we need the cascading delete of partitions in this case. We need to figure out a way to solve this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)