[ https://issues.apache.org/jira/browse/ATLAS-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048046#comment-15048046 ]
Venkat Ranganathan commented on ATLAS-379: ------------------------------------------ The patch adds two new metadata models - for Falcon and Sqoop. The falcon model introduces a Falcon Service (AtlasService) and handles process entity creation and updates. Other entity types and entity operations will be supported later For Sqoop we support hive import and hcatalog imports. As part of working on this, I fixed the intermittent failures with embedded failure which was caused by the use of both IPv4 and V6 stacks enabled. With both the IPv4 and V6 addresses listed in the /etc/hosts file, we were seeing failures in some environments. Fixed this. Fixed the Hive model so that the locationUri is optional. I think I made it required when creating the initial Hive model, but given the new integration scenarios, it is good to relax it. These models can be enhanced later [~sowmyaramesh] and [~bvellanki] worked on portions of the Falcon and Sqoop models > Create sqoop and falcon metadata addons > --------------------------------------- > > Key: ATLAS-379 > URL: https://issues.apache.org/jira/browse/ATLAS-379 > Project: Atlas > Issue Type: Bug > Reporter: Venkat Ranganathan > > We need to create a model for Falcon and Sqoop similar to what we did for > Hive with an initial implementation that caters to most common usage patterns -- This message was sent by Atlassian JIRA (v6.3.4#6332)