[jira] [Created] (ATLAS-209) Use testng and delete junit and scalatest

[liutongfeng (JIRA)]

liutongfeng created ATLAS-209:
-

 Summary: Use testng and delete junit and scalatest
 Key: ATLAS-209
 URL: https://issues.apache.org/jira/browse/ATLAS-209
 Project: Atlas
  Issue Type: Improvement
Reporter: liutongfeng
Assignee: liutongfeng


Currently, maven-surefire-plugin using both testng and junit, the tests will be 
run twice, resulting in wrong test results report.
Now, this issue will delete junit and scalatest, only use testng.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-209) Use testng and delete junit and scalatest

[liutongfeng (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948384#comment-14948384
 ] 

liutongfeng commented on ATLAS-209:
---

Tests using 'mvn clean install' and 'mvn clean package -Pdist' passed under OS 
windows using IEDA.

> Use testng and delete junit and scalatest
> -
>
> Key: ATLAS-209
> URL: https://issues.apache.org/jira/browse/ATLAS-209
> Project: Atlas
>  Issue Type: Improvement
>Reporter: liutongfeng
>Assignee: liutongfeng
> Attachments: ATLAS-209.v1.patch
>
>
> Currently, maven-surefire-plugin using both testng and junit, the tests will 
> be run twice, resulting in wrong test results report.
> Now, this issue will delete junit and scalatest, only use testng.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-209) Use testng and delete junit and scalatest

[liutongfeng (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

liutongfeng updated ATLAS-209:
--
Attachment: ATLAS-209.v1.patch

> Use testng and delete junit and scalatest
> -
>
> Key: ATLAS-209
> URL: https://issues.apache.org/jira/browse/ATLAS-209
> Project: Atlas
>  Issue Type: Improvement
>Reporter: liutongfeng
>Assignee: liutongfeng
> Attachments: ATLAS-209.v1.patch
>
>
> Currently, maven-surefire-plugin using both testng and junit, the tests will 
> be run twice, resulting in wrong test results report.
> Now, this issue will delete junit and scalatest, only use testng.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-163) New Trait UI (Tag)

[Erik Bergenholtz (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948500#comment-14948500
 ] 

Erik Bergenholtz commented on ATLAS-163:


+1 Review

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-209) Use testng and delete junit and scalatest

[Erik Bergenholtz (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erik Bergenholtz updated ATLAS-209:
---
Fix Version/s: 0.6-incubating

> Use testng and delete junit and scalatest
> -
>
> Key: ATLAS-209
> URL: https://issues.apache.org/jira/browse/ATLAS-209
> Project: Atlas
>  Issue Type: Improvement
>Reporter: liutongfeng
>Assignee: liutongfeng
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-209.v1.patch
>
>
> Currently, maven-surefire-plugin using both testng and junit, the tests will 
> be run twice, resulting in wrong test results report.
> Now, this issue will delete junit and scalatest, only use testng.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-188) Provide Ability to Add Tag to Entity

[Erik Bergenholtz (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948510#comment-14948510
 ] 

Erik Bergenholtz commented on ATLAS-188:


+1 Review.

> Provide Ability to Add Tag to Entity
> 
>
> Key: ATLAS-188
> URL: https://issues.apache.org/jira/browse/ATLAS-188
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-188.v1.patch
>
>
> Atlas UI needs to provide the ability to add a tag to an existing entity (see 
> attached mocks). 
> User Story:
> - User Searches for an entity (i.e. hive_table) from the main search screen
> - User identifies an entity that will get a tag associated with it
> - The user selects 'Add Tag' from the detailed entity screen and fills out 
> the necessary fields based on the tag definition.
> - The tag is attached to the Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-163) New Trait UI (Tag)

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948842#comment-14948842
 ] 

Suma Shivaprasad commented on ATLAS-163:


Is the patch attached the latest one ?

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-163) New Trait UI (Tag)

[Vishal Kadam (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948898#comment-14948898
 ] 

Vishal Kadam commented on ATLAS-163:


Yes, ATLAS-163-v1.patch is latest patch. We will make sure once file is 
attached comment is also added for better communication.

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-188) Provide Ability to Add Tag to Entity

[Vishal Kadam (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948900#comment-14948900
 ] 

Vishal Kadam commented on ATLAS-188:


Patch ATLAS-188.v1.patch is added

> Provide Ability to Add Tag to Entity
> 
>
> Key: ATLAS-188
> URL: https://issues.apache.org/jira/browse/ATLAS-188
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-188.v1.patch
>
>
> Atlas UI needs to provide the ability to add a tag to an existing entity (see 
> attached mocks). 
> User Story:
> - User Searches for an entity (i.e. hive_table) from the main search screen
> - User identifies an entity that will get a tag associated with it
> - The user selects 'Add Tag' from the detailed entity screen and fills out 
> the necessary fields based on the tag definition.
> - The tag is attached to the Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-210) UI: Display left hand navigation in hierarchical tree structure

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-210:
--

 Summary: UI: Display left hand navigation in hierarchical tree 
structure
 Key: ATLAS-210
 URL: https://issues.apache.org/jira/browse/ATLAS-210
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.6-incubating
Reporter: Erik Bergenholtz
Assignee: Rohit
 Fix For: 0.6-incubating


As shown here: http://mprhost.com/hw/atlas/rahul/atlashtml/toolsdetails.html

The left hand navigation needs to display traits in a hierarchical structure 
based on super-type (parent) trait relationship.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-188) Provide Ability to Add Tag to Entity

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948934#comment-14948934
 ] 

Suma Shivaprasad commented on ATLAS-188:


[~bholya] [~vkadam] Patch is not applying . Can you reattach?

> Provide Ability to Add Tag to Entity
> 
>
> Key: ATLAS-188
> URL: https://issues.apache.org/jira/browse/ATLAS-188
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Sanjay Patel
>Priority: Critical
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-188.v1.patch
>
>
> Atlas UI needs to provide the ability to add a tag to an existing entity (see 
> attached mocks). 
> User Story:
> - User Searches for an entity (i.e. hive_table) from the main search screen
> - User identifies an entity that will get a tag associated with it
> - The user selects 'Add Tag' from the detailed entity screen and fills out 
> the necessary fields based on the tag definition.
> - The tag is attached to the Entity



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-211) UI: UI Facelift

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-211:
--

 Summary: UI: UI Facelift
 Key: ATLAS-211
 URL: https://issues.apache.org/jira/browse/ATLAS-211
 Project: Atlas
  Issue Type: Improvement
Affects Versions: 0.6-incubating
Reporter: Erik Bergenholtz
Assignee: Rohit
 Fix For: 0.6-incubating


Adopt new look and feel for all screens as shown here: 
http://mprhost.com/hw/atlas/rahul/atlashtml/search.html




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-203) Bridge-Hive.html- configuration name don't match configuration name in import-hive.sh

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948923#comment-14948923
 ] 

Suma Shivaprasad commented on ATLAS-203:


Committed. Thanks [~ndjouhr]

> Bridge-Hive.html- configuration name don't match configuration name in 
> import-hive.sh
> -
>
> Key: ATLAS-203
> URL: https://issues.apache.org/jira/browse/ATLAS-203
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Naima Djouhri
>Priority: Minor
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-203-V0.patch, ATLAS-203-V1.patch
>
>
> In “Bridge-Hive.html”, the configuration name variable is mentioned as 
> "HIVE_CONFIG" whereas in "import-hive.sh" script it is set to "HIVE_CONF_DIR"
> A change to the "import-hive.sh" can be made to match the variable names.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-203) Bridge-Hive.html- configuration name don't match configuration name in import-hive.sh

[Suma Shivaprasad (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948911#comment-14948911
 ] 

Suma Shivaprasad commented on ATLAS-203:


+1

> Bridge-Hive.html- configuration name don't match configuration name in 
> import-hive.sh
> -
>
> Key: ATLAS-203
> URL: https://issues.apache.org/jira/browse/ATLAS-203
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Naima Djouhri
>Priority: Minor
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-203-V0.patch, ATLAS-203-V1.patch
>
>
> In “Bridge-Hive.html”, the configuration name variable is mentioned as 
> "HIVE_CONFIG" whereas in "import-hive.sh" script it is set to "HIVE_CONF_DIR"
> A change to the "import-hive.sh" can be made to match the variable names.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-163) New Trait UI (Tag)

[Vishal Kadam (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14948938#comment-14948938
 ] 

Vishal Kadam commented on ATLAS-163:


Thanks Suma.

> New Trait UI (Tag)
> --
>
> Key: ATLAS-163
> URL: https://issues.apache.org/jira/browse/ATLAS-163
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-163-v0.patch, ATLAS-163-v1.patch, TagDefinition.png
>
>
> Atlas needs a UI to create new Tag definitions.
> See attached screen-shots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-183) Add a Hook in Storm to post the topology metadata

[Andrew Ahn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Ahn updated ATLAS-183:
-
Description: 
Apache Storm Integration with Apache Atlas (incubating)
Introduction
Apache Storm is a distributed real-time computation system. Storm makes it easy 
to reliably process unbounded streams of data, doing for real-time processing 
what Hadoop did for batch processing.  The process is essentially a DAG of 
nodes, which is called topology.

Apache Atlas is a metadata repository that enables end-to-end data lineage, 
search and associate business classification. 
Overview
The goal of this integration is to at minimum push the operational topology 
metadata along with the underlying data source(s), target(s), derivation 
processes and any available business context so Atlas can capture the lineage 
for this topology.

It would also help to support custom user annotations per node in the topology.

There are 2 parts in this process detailed below:
Data model to represent the concepts in Storm
Storm Bridge to update metadata in Atlas
Data Model
A data model is represented as a Type in Atlas. It contains the descriptions of 
various nodes in the DAG, such as spouts and bolts and the corresponding source 
and target types.  These need to be expressed as Types in Atlas type system. At 
the least, we need to create types for:
Storm topology containing spouts, bolts, etc. with associations between them
Source (typically Kafka, etc.)
Target (typically Hive, HBase, HDFS, etc.)

You can take a look at the data model code for Hive. Storm should only be 
simpler than Hive from a data modeling perspective.
Pushing Metadata into Atlas
There are 2 parts to the bridge:
Storm Bridge 
This is a one-time import for Storm to list all the active topologies and push 
the metadata into Atlas to address cases where Storm deployments exist before 
Atlas.

You can refer to the bridge code for Hive.

Post-execution Hook
Atlas needs to be notified when a new topology is registered successfully in 
Storm or when someone changes the definition of an existing topology.

You can refer to the hook code for Hive.
 
Example use case:
Custom annotations associated with each node in the topology.  
For example: Data Quality Rules, Error Handling, etc. A set of annotations that 
enumerates rules handling nulls– all nulls for a column get filtered, etc.



> Add a Hook in Storm to post the topology metadata
> -
>
> Key: ATLAS-183
> URL: https://issues.apache.org/jira/browse/ATLAS-183
> Project: Atlas
>  Issue Type: Sub-task
>Affects Versions: 0.6-incubating
>Reporter: Venkatesh Seetharam
> Fix For: 0.6-incubating
>
>
> Apache Storm Integration with Apache Atlas (incubating)
> Introduction
> Apache Storm is a distributed real-time computation system. Storm makes it 
> easy to reliably process unbounded streams of data, doing for real-time 
> processing what Hadoop did for batch processing.  The process is essentially 
> a DAG of nodes, which is called topology.
> Apache Atlas is a metadata repository that enables end-to-end data lineage, 
> search and associate business classification. 
> Overview
> The goal of this integration is to at minimum push the operational topology 
> metadata along with the underlying data source(s), target(s), derivation 
> processes and any available business context so Atlas can capture the lineage 
> for this topology.
> It would also help to support custom user annotations per node in the 
> topology.
> There are 2 parts in this process detailed below:
> Data model to represent the concepts in Storm
> Storm Bridge to update metadata in Atlas
> Data Model
> A data model is represented as a Type in Atlas. It contains the descriptions 
> of various nodes in the DAG, such as spouts and bolts and the corresponding 
> source and target types.  These need to be expressed as Types in Atlas type 
> system. At the least, we need to create types for:
> Storm topology containing spouts, bolts, etc. with associations between them
> Source (typically Kafka, etc.)
> Target (typically Hive, HBase, HDFS, etc.)
> You can take a look at the data model code for Hive. Storm should only be 
> simpler than Hive from a data modeling perspective.
> Pushing Metadata into Atlas
> There are 2 parts to the bridge:
> Storm Bridge 
> This is a one-time import for Storm to list all the active topologies and 
> push the metadata into Atlas to address cases where Storm deployments exist 
> before Atlas.
> You can refer to the bridge code for Hive.
> Post-execution Hook
> Atlas needs to be notified when a new topology is registered successfully in 
> Storm or when someone changes the definition of an existing topology.
> You can refer to the hook code for Hive.
>  
> Example use case:
> Custom annotations associated with each 

[jira] [Commented] (ATLAS-181) Integrate storm topology metadata into Atlas

[Andrew Ahn (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949035#comment-14949035
 ] 

Andrew Ahn commented on ATLAS-181:
--

Please reference additional info with Storm Jira:

https://issues.apache.org/jira/browse/STORM-1098

> Integrate storm topology metadata into Atlas
> 
>
> Key: ATLAS-181
> URL: https://issues.apache.org/jira/browse/ATLAS-181
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Venkatesh Seetharam
> Fix For: 0.6-incubating
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: apache-atlas-nightly #86

[Apache Jenkins Server]

See 

Changes:

[sumasai.shivaprasad] ATLAS-203 Bridge-Hive.html- configuration name don't 
match configuration

[sumasai.shivaprasad] ATLAS-163 New Trait UI (Tag) darshankumar89 via sumasai

--
[...truncated 4944 lines...]
[INFO] Deleting 

[INFO] Deleting 
 (includes 
= [**/*.pyc], excludes = [])
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.0:create (default) @ atlas-notification 
---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[WARNING] Cannot get the revision information from the scm repository, 
proceeding with revision of release : 
No such provider: 'https'.
[INFO] Storing buildNumber: release at timestamp: 1444326364419
[WARNING] Cannot get the branch information from the scm repository, proceeding 
with UNKNOWN_BRANCH : 
No such provider: 'https'.
[INFO] Storing buildScmBranch: UNKNOWN_BRANCH
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-notification ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-notification ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:compile (scala-compile-first) @ 
atlas-notification ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 8 Java sources to 

[WARNING] Note: 

 uses unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-notification ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 8 source files to 

[WARNING] 
:
 

 uses unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-notification ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- scala-maven-plugin:3.2.0:testCompile (scala-test-compile-first) @ 
atlas-notification ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 1 Java source to 

[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-notification ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 1 source file to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ 
atlas-notification ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.5:jar (default-jar) @ atlas-notification ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-notification ---
[INFO] 
[INFO] >>> maven-javadoc-plugin:2.8.1:javadoc (javadoc) @ atlas-notification >>>
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.0:create (default) @ atlas-notification 
---
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[WARNING] Cannot get the revision information from the scm repository, 
proceeding with revision of release : 
No such provider: 'https'.
[INFO] Storing buildNumber: release at timestamp: 1444326367961
[WARNING] Cannot get the branch information from the scm repository, proceeding 
with UNKNOWN_BRANCH : 
No such provider: 'https'.
[INFO] Storing 

Review Request 39134: Remove test class usage of hive configuration property "atlas.rest.address"

[John Speidel]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39134/
---

Review request for atlas, Shwetha GS and Tom Beerbower.


Bugs: ATLAS-212
https://issues.apache.org/jira/browse/ATLAS-212


Repository: atlas


Description
---

The property "atlas.rest.address" has been removed from hive-site configuration 
but is still referenced by the class HiveHookIT.


Diffs
-

  addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
f4b9350 

Diff: https://reviews.apache.org/r/39134/diff/


Testing
---

All existing unit tests pass.
[INFO] Reactor Summary:
[INFO]
[INFO] apache-atlas ... SUCCESS [  1.864 s]
[INFO] Apache Atlas Typesystem  SUCCESS [ 40.979 s]
[INFO] Apache Atlas Common  SUCCESS [  1.325 s]
[INFO] Apache Atlas Client  SUCCESS [  5.037 s]
[INFO] Apache Atlas Notification .. SUCCESS [  4.545 s]
[INFO] Apache Atlas Repository  SUCCESS [03:20 min]
[INFO] Apache Atlas Web Application ... SUCCESS [ 28.044 s]
[INFO] Apache Atlas Documentation . SUCCESS [ 11.518 s]
[INFO] Apache Atlas Hive Bridge ... SUCCESS [  7.604 s]
[INFO] Apache Atlas Distribution .. SUCCESS [  0.922 s]
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 


Thanks,

John Speidel

[jira] [Created] (ATLAS-214) UI : For any hive_table, schema/input/output tabs are not displayed

[Ayub Khan (JIRA)]

Ayub Khan created ATLAS-214:
---

 Summary: UI : For any hive_table, schema/input/output tabs are not 
displayed
 Key: ATLAS-214
 URL: https://issues.apache.org/jira/browse/ATLAS-214
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Ayub Khan


In Atlas UI, for any hive_tables schema/input/output tabs are not displayed. 
whereas for other tables these tabs are shown.

Please take a look at the UI snapshots.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ATLAS-213) UI: When searching for Tag/Trait, Search results show guid instead of name

[Erik Bergenholtz (JIRA)]

Erik Bergenholtz created ATLAS-213:
--

 Summary: UI: When searching for Tag/Trait, Search results show 
guid instead of name
 Key: ATLAS-213
 URL: https://issues.apache.org/jira/browse/ATLAS-213
 Project: Atlas
  Issue Type: Bug
Affects Versions: 0.6-incubating
Reporter: Erik Bergenholtz
Assignee: Rohit
 Fix For: 0.6-incubating


UI: When searching for Tag/Trait, Search results show guid instead of name.

See: https://monosnap.com/file/m9857DlVtUWCwkAbRQ3kcOZla6pdaa



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ATLAS-184) Integrate Sqoop metadata into Atlas

[Andrew Ahn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/ATLAS-184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Ahn updated ATLAS-184:
-
Description: 
Apache Sqoop Integration with Apache Atlas (incubating)
Introduction
Apache Sqoop is a tool designed for efficiently transferring bulk data between 
Apache Hadoop and structured data stores such as relational databases.

Apache Atlas is a metadata repository that enables end-to-end data lineage, 
search and associate business classification. 
Overview
The goal of this integration is to at minimum push the Sqoop generated query 
metadata along with the source provenance, target(s), and any available 
business context so Atlas can capture the lineage for this topology.

There are 2 parts in this process detailed below:
1.  Data model to represent the concepts in Sqoop
2.  Sqoop Bridge/Hook to update metadata in Atlas
Data Model
A data model is represented as a Type in Atlas. This can reuse or closely be 
modeled after Hive data types that already exist. At the least, we need to 
create types for:
•   Sqoop processes containing the SQL query text, start/end times, user, 
etc. 
•   Source Provenance, fine-grained at DB, Table, Column, etc. so we have a 
1-1 mapping between source and target assets
•   Target (typically Hive, HBase, HDFS, etc.)

You can take a look at the data model code for Hive. Sqoop should reuse the 
data model from Hive or closely model after that.
Pushing Metadata into Atlas
There are 2 parts to the bridge:
1.  Sqoop Bridge 
This does not apply to Sqoop tool. However, will apply if and when we migrate 
to Sqoop 2.
2.  Post-execution Hook
Atlas needs to be notified when a new Sqoop Ingest is executed successfully or 
when someone changes the definition of an existing Sqoop Job.
You can refer to the hook code for Hive.
3.  Column-level lineage
It would be good to have column level lineage for data flowing from the source 
database/WH into Hive. 


> Integrate Sqoop metadata into Atlas
> ---
>
> Key: ATLAS-184
> URL: https://issues.apache.org/jira/browse/ATLAS-184
> Project: Atlas
>  Issue Type: Improvement
>Affects Versions: 0.6-incubating
>Reporter: Venkatesh Seetharam
> Fix For: 0.6-incubating
>
>
> Apache Sqoop Integration with Apache Atlas (incubating)
> Introduction
> Apache Sqoop is a tool designed for efficiently transferring bulk data 
> between Apache Hadoop and structured data stores such as relational databases.
> Apache Atlas is a metadata repository that enables end-to-end data lineage, 
> search and associate business classification. 
> Overview
> The goal of this integration is to at minimum push the Sqoop generated query 
> metadata along with the source provenance, target(s), and any available 
> business context so Atlas can capture the lineage for this topology.
> There are 2 parts in this process detailed below:
> 1.Data model to represent the concepts in Sqoop
> 2.Sqoop Bridge/Hook to update metadata in Atlas
> Data Model
> A data model is represented as a Type in Atlas. This can reuse or closely be 
> modeled after Hive data types that already exist. At the least, we need to 
> create types for:
> • Sqoop processes containing the SQL query text, start/end times, user, 
> etc. 
> • Source Provenance, fine-grained at DB, Table, Column, etc. so we have a 
> 1-1 mapping between source and target assets
> • Target (typically Hive, HBase, HDFS, etc.)
> You can take a look at the data model code for Hive. Sqoop should reuse the 
> data model from Hive or closely model after that.
> Pushing Metadata into Atlas
> There are 2 parts to the bridge:
> 1.Sqoop Bridge 
> This does not apply to Sqoop tool. However, will apply if and when we migrate 
> to Sqoop 2.
> 2.Post-execution Hook
> Atlas needs to be notified when a new Sqoop Ingest is executed successfully 
> or when someone changes the definition of an existing Sqoop Job.
> You can refer to the hook code for Hive.
> 3.Column-level lineage
> It would be good to have column level lineage for data flowing from the 
> source database/WH into Hive. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 39134: Remove test class usage of hive configuration property "atlas.rest.address"

[Tom Beerbower]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/39134/#review101936
---

Ship it!


Ship It!

- Tom Beerbower


On Oct. 8, 2015, 4:20 p.m., John Speidel wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/39134/
> ---
> 
> (Updated Oct. 8, 2015, 4:20 p.m.)
> 
> 
> Review request for atlas, Shwetha GS and Tom Beerbower.
> 
> 
> Bugs: ATLAS-212
> https://issues.apache.org/jira/browse/ATLAS-212
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> The property "atlas.rest.address" has been removed from hive-site 
> configuration but is still referenced by the class HiveHookIT.
> 
> 
> Diffs
> -
> 
>   addons/hive-bridge/src/test/java/org/apache/atlas/hive/hook/HiveHookIT.java 
> f4b9350 
> 
> Diff: https://reviews.apache.org/r/39134/diff/
> 
> 
> Testing
> ---
> 
> All existing unit tests pass.
> [INFO] Reactor Summary:
> [INFO]
> [INFO] apache-atlas ... SUCCESS [  1.864 
> s]
> [INFO] Apache Atlas Typesystem  SUCCESS [ 40.979 
> s]
> [INFO] Apache Atlas Common  SUCCESS [  1.325 
> s]
> [INFO] Apache Atlas Client  SUCCESS [  5.037 
> s]
> [INFO] Apache Atlas Notification .. SUCCESS [  4.545 
> s]
> [INFO] Apache Atlas Repository  SUCCESS [03:20 
> min]
> [INFO] Apache Atlas Web Application ... SUCCESS [ 28.044 
> s]
> [INFO] Apache Atlas Documentation . SUCCESS [ 11.518 
> s]
> [INFO] Apache Atlas Hive Bridge ... SUCCESS [  7.604 
> s]
> [INFO] Apache Atlas Distribution .. SUCCESS [  0.922 
> s]
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> 
> 
> Thanks,
> 
> John Speidel
> 
>

[jira] [Commented] (ATLAS-209) Use testng and delete junit and scalatest

[Shwetha G S (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949179#comment-14949179
 ] 

Shwetha G S commented on ATLAS-209:
---

Nice, +1. Thanks for doing this

> Use testng and delete junit and scalatest
> -
>
> Key: ATLAS-209
> URL: https://issues.apache.org/jira/browse/ATLAS-209
> Project: Atlas
>  Issue Type: Improvement
>Reporter: liutongfeng
>Assignee: liutongfeng
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-209.v1.patch
>
>
> Currently, maven-surefire-plugin using both testng and junit, the tests will 
> be run twice, resulting in wrong test results report.
> Now, this issue will delete junit and scalatest, only use testng.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ATLAS-199) webapp build fails (grunt + tests)

[Darshan Kumar (JIRA)]

[ 
https://issues.apache.org/jira/browse/ATLAS-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14949241#comment-14949241
 ] 

Darshan Kumar commented on ATLAS-199:
-

ok I will also check. Thanks  [~shwethags]

> webapp build fails (grunt + tests)
> --
>
> Key: ATLAS-199
> URL: https://issues.apache.org/jira/browse/ATLAS-199
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.6-incubating
>Reporter: Erik Bergenholtz
>Assignee: Darshan Kumar
>Priority: Critical
>  Labels: patch-available
> Fix For: 0.6-incubating
>
> Attachments: ATLAS-199-v0.patch
>
>
> When building Atlas webapp, I see the following issues:
> mvn clean install:
> {code}
> [INFO] Running 'grunt bower --no-color' in 
> /Users/ebergenholtz/git3/incubator-atlas/dashboard
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 34.282 s
> [INFO] Finished at: 2015-09-30T13:55:30-05:00
> [INFO] Final Memory: 35M/420M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> com.github.eirslett:frontend-maven-plugin:0.0.23:grunt (install bower) on 
> project atlas-webapp: Failed to run task: 'grunt bower --no-color' failed. 
> java.io.IOException: Cannot run program 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard/node/node" (in directory 
> "/Users/ebergenholtz/git3/incubator-atlas/dashboard"): error=2, No such file 
> or directory -> [Help 1]
> {code}
> Also, if I bypass the grunt task some of the tests fail.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)