From dev-return-1101-apmail-atlas-dev-archive=atlas.apache.org@atlas.incubator.apache.org Thu Sep 17 10:01:54 2015 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 A8F4817779 for ; Thu, 17 Sep 2015 10:01:54 +0000 (UTC) Received: (qmail 98287 invoked by uid 500); 17 Sep 2015 10:01:49 -0000 Delivered-To: apmail-atlas-dev-archive@atlas.apache.org Received: (qmail 98242 invoked by uid 500); 17 Sep 2015 10:01:49 -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 98231 invoked by uid 99); 17 Sep 2015 10:01:49 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Sep 2015 10:01:49 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 05E39C0BC9 for ; Thu, 17 Sep 2015 10:01:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.974 X-Spam-Level: X-Spam-Status: No, score=0.974 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.006] autolearn=disabled Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id KGJxu9rdt_fj for ; Thu, 17 Sep 2015 10:01:47 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with SMTP id D98FD204DD for ; Thu, 17 Sep 2015 10:01:46 +0000 (UTC) Received: (qmail 97923 invoked by uid 99); 17 Sep 2015 10:01:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Sep 2015 10:01:46 +0000 Date: Thu, 17 Sep 2015 10:01:45 +0000 (UTC) From: =?utf-8?Q?R=C3=A9my_SAISSY_=28JIRA=29?= To: dev@atlas.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ATLAS-164) DFS addon for Atlas MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ATLAS-164?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D14802= 696#comment-14802696 ]=20 R=C3=A9my SAISSY commented on ATLAS-164: ----------------------------------- Hi Venkatesh, thanks. * DfsDataModel=20 I agree, at first I started by considering three classes: file, dir and sym= link. I reverted back to 1:1 mapping because handling symlink required to use two= different properties wether I had a file or a directory target. I thought = that it would not be an issue to map inodes since the query language enable= s to show files, dirs and symlinks separately. A question, can we model class inheritance? If so, I could have dir,file an= d symlink classes to inherit from inode and provide a clean symlink_target = attribute with the parent class as the type. * Import Thanks for the pointer, I will check how falcon does it. Appart from the te= chnical standpoint, I will also document myself a bit one regulatory needs = since implementing as data sets is that it will reduce the granularity thus= maybe it might not be precise enough for some regulatory needs. Also, I see two approaches to data sets: - one that requires to manually define data sets using the webapp so the b= ridge will log only those data sets (and forget about the other events on H= DFS) - one that consider that a data set is a non-recursive directory. Any acti= on on a file will log an event for its directory The latter has the advantage to process all actions in HDFS and to be easie= r to configure and use for the end user so I would prefer it. * Lineage This is because I haven't yet fully understood how lineage should be handle= d in by Atlas addons. - should I also keep track of who executed what action on a data set / fil= e / dir / symlink? I haven't seen support for it in the hive-bridge but I g= uess it is required to comply with regulatory needs. Speaking about set of files consumed by a PIG,MR,Spark or whatever job, sin= ce HDFS sees actions as they happen, I see two approaches: - HDFS level: considering a data set as being a non-recursive directory. T= hat would be a lot of events but all for the same node in Atlas (the source= / target directory of the job) - processing framework level: hook an addon for each framework that log ev= ents into atlas on the same data as the hdfs bridge ones. --> I prefer doing it at the HDFS level only. It is more generic. * Unit Tests I've made a typo, I meant the integration test. > DFS addon for Atlas > ------------------- > > Key: ATLAS-164 > URL: https://issues.apache.org/jira/browse/ATLAS-164 > Project: Atlas > Issue Type: New Feature > Affects Versions: 0.6-incubating > Reporter: R=C3=A9my SAISSY > Assignee: R=C3=A9my SAISSY > Attachments: ATLAS-164.15092015.patch, ATLAS-164.15092015.patch > > > Hi, > I have wrote an addon for sending DFS metadata into Atlas. > The patch is attached. > However, I have a hard time getting the unit tests working properly thus = some advices would be welcome. > Thanks. -- This message was sent by Atlassian JIRA (v6.3.4#6332)