Re: Review Request 49941: ATLAS-998: determine HA mode from property atlas.server.ids, instead of atlas.server.ha.enabled

[Shwetha GS]

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




common/src/main/java/org/apache/atlas/ha/HAConfiguration.java (line 55)


move it to tests



common/src/main/java/org/apache/atlas/ha/HAConfiguration.java (line 64)


To make it backward compatible, as 0.7 is already out, can the check be if 
ha.enabled or ids > 1?


- Shwetha GS


On July 12, 2016, 1:29 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49941/
> ---
> 
> (Updated July 12, 2016, 1:29 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-998
> https://issues.apache.org/jira/browse/ATLAS-998
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Updated to use atlas.server.ids property to determine if multiple instances 
> of Atlas are configured to run (in HA mode), instead of 
> atlas.server.ha.enabled
> 
> 
> Diffs
> -
> 
>   common/src/main/java/org/apache/atlas/ha/HAConfiguration.java f3c9bc5 
>   common/src/test/java/org/apache/atlas/ha/HAConfigurationTest.java a3129c9 
>   
> repository/src/test/java/org/apache/atlas/repository/audit/HBaseBasedAuditRepositoryHATest.java
>  2f7edb4 
>   
> repository/src/test/java/org/apache/atlas/repository/graph/GraphBackedSearchIndexerMockTest.java
>  94dd298 
>   
> repository/src/test/java/org/apache/atlas/services/DefaultMetadataServiceMockTest.java
>  393b539 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  7860eb6 
>   
> webapp/src/test/java/org/apache/atlas/web/service/ActiveInstanceElectorServiceTest.java
>  2b7691f 
>   webapp/src/test/java/org/apache/atlas/web/service/ServiceStateTest.java 
> 77aba88 
> 
> Diff: https://reviews.apache.org/r/49941/diff/
> 
> 
> Testing
> ---
> 
> - Verified that all unit tests succeed
> - Verified that when multiple instances are listed in 'atlas.server.ids' 
> configuration, Atlas server takes HA code path
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

[jira] [Updated] (ATLAS-1002) Create default user rangertagsync in atlas file authentication for Ranger tag sync module.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1002:
---
Attachment: ATLAS-1002-1.patch

> Create default user rangertagsync in atlas file authentication for Ranger tag 
> sync module.
> --
>
> Key: ATLAS-1002
> URL: https://issues.apache.org/jira/browse/ATLAS-1002
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Minor
> Attachments: ATLAS-1002-1.patch, ATLAS-1002.patch
>
>
> Create default user *rangertagsync* in atlas file authentication for Ranger 
> tag sync module.



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

Re: Review Request 49896: ATLAS-1002 - Create default user rangertagsync in atlas file authentication for Ranger tag sync module

[Nixon Rodrigues]

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

(Updated July 12, 2016, 5:42 a.m.)


Review request for atlas, keval bhatt, Madhan Neethiraj, Mehul Parikh, Shwetha 
GS, Suma Shivaprasad, and Hemanth Yamijala.


Changes
---

Handled review comment to add permission for entity.


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


Repository: atlas


Description
---

Create default user rangertagsync in atlas file authentication for Ranger tag 
sync module.


Diffs (updated)
-

  distro/src/conf/policy-store.txt e4e77fc 
  distro/src/conf/users-credentials.properties 1758be2 

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


Testing
---

Tested Atlas UI login with (rangertagsync:rangertagsync), UI loaded with only 
tags.

Tested the types api with curl following commands
curl -kv -u rangertagsync:rangertagsync http://localhost:21000/api/atlas/types
curl -kv -u rangertagsync:rangertagsync 
http://localhost:21000/api/atlas/types?type=CLASS
curl -kv -u rangertagsync:rangertagsync 
http://localhost:21000/api/atlas/types/Metric


Thanks,

Nixon Rodrigues

[jira] [Assigned] (ATLAS-1004) Option to enable taxonomy feature

[Keval Bhatt (JIRA)]

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

Keval Bhatt reassigned ATLAS-1004:
--

Assignee: Keval Bhatt

> Option to enable taxonomy feature
> -
>
> Key: ATLAS-1004
> URL: https://issues.apache.org/jira/browse/ATLAS-1004
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Madhan Neethiraj
>Assignee: Keval Bhatt
>
> Currently 'term' object used in taxonomy feature implementation is modeled as 
> a trait. However, unlike tags, all the associations of a term (with entities) 
> share the attribute values of the term object. This and few other aspects of 
> taxonomy implementation would need to be reviewed. Until then, this feature 
> should be available in the UI only for users who opt-in to enable, via a 
> configuration - like atlas.feature.taxonomy.enable=true.



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

Re: Review Request 49633: ATLAS-949 : UI improvement for modal and tag styling in table

[Madhan Neethiraj]

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


Ship it!




Ship It!

- Madhan Neethiraj


On July 7, 2016, 10:15 a.m., Kalyani Kashikar wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/49633/
> ---
> 
> (Updated July 7, 2016, 10:15 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj, Shwetha GS, Suma Shivaprasad, and 
> Hemanth Yamijala.
> 
> 
> Bugs: ATLAS-949
> https://issues.apache.org/jira/browse/ATLAS-949
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> * Style change for Tag.
> * Popup(Modal) beautify for assign term to Asset from search table and same 
> for schema.
> * In table by default only one tag is shown and if there are more Tags they 
> are shown by "..." button insted of "Show more" - "Show less" button.
> * UI(Modal) changes for Add tag.
> * Text change from "delete" to "remove" in assign term/tag Modal.
> 
> 
> Diffs
> -
> 
>   dashboardv2/public/css/scss/main.scss 6b88639 
>   dashboardv2/public/css/scss/tag.scss 8eb0ac2 
>   dashboardv2/public/css/scss/tree.scss 5574137 
>   dashboardv2/public/js/collection/BaseCollection.js e4ac1ae 
>   dashboardv2/public/js/collection/VCatalogList.js 410a35a 
>   
> dashboardv2/public/js/templates/business_catalog/BusinessCatalogDetailLayoutView_tmpl.html
>  5e1cfca 
>   dashboardv2/public/js/templates/business_catalog/TreeLayoutView_tmpl.html 
> b915680 
>   dashboardv2/public/js/templates/detail_page/DetailPageLayoutView_tmpl.html 
> f638bac 
>   dashboardv2/public/js/templates/search/SearchDetailLayoutView_tmpl.html 
> 3fd1b7a 
>   dashboardv2/public/js/templates/tag/addTagModalView_tmpl.html 2aa82f6 
>   dashboardv2/public/js/utils/CommonViewFunction.js 6d88dc8 
>   dashboardv2/public/js/utils/Messages.js f78ec87 
>   dashboardv2/public/js/utils/Utils.js 5e75e59 
>   
> dashboardv2/public/js/views/business_catalog/BusinessCatalogDetailLayoutView.js
>  7e3e586 
>   dashboardv2/public/js/views/business_catalog/TreeLayoutView.js 63eaa3e 
>   dashboardv2/public/js/views/detail_page/DetailPageLayoutView.js 7f31141 
>   dashboardv2/public/js/views/graph/LineageLayoutView.js ecbbe51 
>   dashboardv2/public/js/views/schema/SchemaLayoutView.js 55e7093 
>   dashboardv2/public/js/views/search/SearchResultLayoutView.js 75bf6ef 
>   dashboardv2/public/js/views/tag/TagDetailTableLayoutView.js e9d4b57 
>   dashboardv2/public/js/views/tag/addTagModalView.js 58f4918 
> 
> Diff: https://reviews.apache.org/r/49633/diff/
> 
> 
> Testing
> ---
> 
> Ran Quick start and did sanity test for tags / entity / lineage UI.
> 
> ** Verified following scenarios:**
> 
> * Tags UI shown properly.
> * UI of modal for assign term to Asset from search table/ schema table  and 
> Add tag shown properly.
> * In table by default only one tag is shown and if there are more Tags they 
> are shown by "..." button insted of "Show more" - "Show less" button - 
> verified this case.
> * Text changed from "delete" to "remove" in assign term/tag Modal- verified.
> 
> 
> Thanks,
> 
> Kalyani Kashikar
> 
>

[jira] [Commented] (ATLAS-499) Automatically update inverse references to prevent repository corruption

[David Kantor (JIRA)]

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

David Kantor commented on ATLAS-499:


Changed status back to Open, as I had to leave this aside recently to work on 
higher priority items.  Will resume work on this after addressing these items.

> Automatically update inverse references to prevent repository corruption
> 
>
> Key: ATLAS-499
> URL: https://issues.apache.org/jira/browse/ATLAS-499
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Kantor
>Assignee: David Kantor
>
> For references that are defined in the type system as bi-directional, Atlas 
> does not enforce that clients update both sides of the reference, and relies 
> on well behaved client applications for repository consistency.   This allows 
> the repository to be easily corrupted with unbalanced references.  Atlas 
> should automatically update the inverse reference to avoid this corruption.



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

[jira] [Commented] (ATLAS-1002) Create default user rangertagsync in atlas file authentication for Ranger tag sync module.

[ATLAS QA (JIRA)]

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

ATLAS QA commented on ATLAS-1002:
-

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment
  http://issues.apache.org/jira/secure/attachment/12817182/ATLAS-1002.patch
  against master revision 2ad344f.

{color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

{color:red}-1 tests included{color}.  The patch doesn't appear to include 
any new or modified tests.
Please justify why no new tests are needed for this 
patch.
Also please list what manual steps were performed to 
verify this patch.

{color:green}+1 javac{color}.  The applied patch does not increase the 
total number of javac compiler warnings.

{color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

+1 checkstyle.  The patch generated 0 code style errors.

{color:red}-1 findbugs{color}.  The patch appears to introduce 381 new 
Findbugs (version 2.0.3) warnings.

{color:green}+1 release audit{color}.  The applied patch does not increase 
the total number of release audit warnings.

{color:red}-1 core tests{color}.  The patch failed these unit tests in :
   
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
  org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
  
org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
  org.apache.atlas.discovery.DataSetLineageServiceTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.repository.graph.GraphBackedRepositoryHardDeleteTest
./repository/target/surefire-reports/junitreports/TEST-org.apache.atlas.discovery.DataSetLineageServiceTest

Test results: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//testReport/
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsrepository.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningstitan.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningswebapp.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningscatalog.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningstypesystem.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsclient.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsauthorization.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsplugin-classloader.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsnotification.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningscommon.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningshive-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsfalcon-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningshdfs-model.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningsstorm-bridge.html
Findbugs warnings: 
https://builds.apache.org/job/PreCommit-ATLAS-Build/392//artifact/patchprocess/newPatchFindbugsWarningssqoop-bridge.html
Console output: https://builds.apache.org/job/PreCommit-ATLAS-Build/392//console

This message is automatically generated.

> Create default user rangertagsync in atlas file authentication for Ranger tag 
> sync module.
> --
>
> Key: ATLAS-1002
> URL: https://issues.apache.org/jira/browse/ATLAS-1002
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Minor
> Attachments: ATLAS-1002.patch
>
>
> Create default user 

[jira] [Updated] (ATLAS-1002) Create default user rangertagsync in atlas file authentication for Ranger tag sync module.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues updated ATLAS-1002:
---
Attachment: ATLAS-1002.patch

> Create default user rangertagsync in atlas file authentication for Ranger tag 
> sync module.
> --
>
> Key: ATLAS-1002
> URL: https://issues.apache.org/jira/browse/ATLAS-1002
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Minor
> Attachments: ATLAS-1002.patch
>
>
> Create default user *rangertagsync* in atlas file authentication for Ranger 
> tag sync module.



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

Review Request 49896: ATLAS-1002 - Create default user rangertagsync in atlas file authentication for Ranger tag sync module

[Nixon Rodrigues]

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

Review request for atlas, keval bhatt, Madhan Neethiraj, Mehul Parikh, Shwetha 
GS, Suma Shivaprasad, and Hemanth Yamijala.


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


Repository: atlas


Description
---

Create default user rangertagsync in atlas file authentication for Ranger tag 
sync module.


Diffs
-

  distro/src/conf/policy-store.txt e4e77fc 
  distro/src/conf/users-credentials.properties 1758be2 

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


Testing
---

Tested Atlas UI login with (rangertagsync:rangertagsync), UI loaded with only 
tags.

Tested the types api with curl following commands
curl -kv -u rangertagsync:rangertagsync http://localhost:21000/api/atlas/types
curl -kv -u rangertagsync:rangertagsync 
http://localhost:21000/api/atlas/types?type=CLASS
curl -kv -u rangertagsync:rangertagsync 
http://localhost:21000/api/atlas/types/Metric


Thanks,

Nixon Rodrigues

[jira] [Assigned] (ATLAS-1002) Create default user rangertagsync in atlas file authentication for Ranger tag sync module.

[Nixon Rodrigues (JIRA)]

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

Nixon Rodrigues reassigned ATLAS-1002:
--

Assignee: Nixon Rodrigues

> Create default user rangertagsync in atlas file authentication for Ranger tag 
> sync module.
> --
>
> Key: ATLAS-1002
> URL: https://issues.apache.org/jira/browse/ATLAS-1002
> Project: Atlas
>  Issue Type: Improvement
>Reporter: Nixon Rodrigues
>Assignee: Nixon Rodrigues
>Priority: Minor
>
> Create default user *rangertagsync* in atlas file authentication for Ranger 
> tag sync module.



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

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

[Apache Jenkins Server]

See 

Changes:

[sshivalingamurthy] ATLAS-936 Update atlas website for 0.7 release (shwethags)

--
[...truncated 3060 lines...]
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ 
atlas-repository ---
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
atlas-repository ---
[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-repository ---
[WARNING] Zinc server is not available at port 3030 - reverting to normal 
incremental compile
[INFO] Using incremental compilation
[INFO] Compiling 9 Scala sources and 49 Java sources to 

[WARNING] 
:134:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("adding entities={}", entities);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] 
:297:
 warning: non-varargs call of varargs method with inexact argument type for 
last parameter;
[WARNING] LOG.debug("updating entity {}", entitiesUpdated);
[WARNING] ^
[WARNING]   cast to Object for a varargs call
[WARNING]   cast to Object[] for a non-varargs call and to suppress this warning
[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[WARNING] 2 warnings
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 49 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
atlas-repository ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

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

[WARNING] Note: Some input files use unchecked or unsafe operations.
[WARNING] Note: Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-repository ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 27 source files to 

[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-repository 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.
[INFO] Surefire report directory: 

[INFO] Using configured provider org.apache.maven.surefire.testng.TestNGProvider
[WARNING] file.encoding cannot be set as system property, use 
-Dfile.encoding=... instead

[jira] [Created] (ATLAS-1001) UI: paginate search results

[Shwetha G S (JIRA)]

Shwetha G S created ATLAS-1001:
--

 Summary: UI: paginate search results
 Key: ATLAS-1001
 URL: https://issues.apache.org/jira/browse/ATLAS-1001
 Project: Atlas
  Issue Type: Bug
Reporter: Shwetha G S
Priority: Critical
 Fix For: 0.8-incubating


ATLAS-347 will support pagination of search results in APIs. UI should also 
support pagination



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

[jira] [Updated] (ATLAS-957) Atlas is not capturing topologies that have $ in the data payload

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-957:
--
Priority: Critical  (was: Major)

> Atlas is not capturing topologies that have $ in the data payload
> -
>
> Key: ATLAS-957
> URL: https://issues.apache.org/jira/browse/ATLAS-957
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Shwetha G S
>Priority: Critical
>
> We found a topology that created a specific payload in Kafka ATLAS_HOOK 
> topic, that Atlas failed to process with an exception. The payload was:
> {code}
> {
>   "version": {
> "version": "1.0.0"
>   },
>   "message": {
> "entities": [{
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "-12002007734454",
> "version": 0,
> "typeName": "storm_topology",
> "state": "ACTIVE"
>   },
>   "typeName": "storm_topology",
>   "values": {
> "name": "WordCountid007f0100_date381916",
> "startTime": 1466404755258,
> "outputs": [],
> "id": "WordCountid007f0100_date381916-5-1466404754",
> "inputs": [],
> "qualifiedName": "WordCountid007f0100_date381916",
> "nodes": [{
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "-12002013206349",
> "version": 0,
> "typeName": "storm_bolt",
> "state": "ACTIVE"
>   },
>   "typeName": "storm_bolt",
>   "values": {
> "name": "split",
> "outputs": ["count"],
> "driverClass": "storm.starter.WordCountTopology$SplitSentence",
> "conf": {
>   "SplitSentence._pendingWrites.takeLock.sync.state": "0",
>   "SplitSentence._running": "true",
>   "SplitSentence.workerTimeoutMills": "0",
>   "SplitSentence.sendHeartbeatFlag.value": "0",
>   "SplitSentence.lastHeartbeatTimestamp.value": "0",
>   "SplitSentence._pendingWrites.notEmpty.this$0.state": "0"
> },
> "inputs": ["spout"]
>   },
>   "traitNames": ["DataProcessor"],
>   "traits": {
> "DataProcessor": {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName": "DataProcessor",
>   "values": {}
> }
>   }
> }, {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "-12002012737263",
> "version": 0,
> "typeName": "storm_spout",
> "state": "ACTIVE"
>   },
>   "typeName": "storm_spout",
>   "values": {
> "outputs": ["split"],
> "name": "spout",
> "driverClass": "storm.starter.spout.RandomSentenceSpout",
> "conf": {}
>   },
>   "traitNames": ["DataProducer"],
>   "traits": {
> "DataProducer": {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName": "DataProducer",
>   "values": {}
> }
>   }
> }, {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>   "id": {
> "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
> "id": "-12002021428964",
> "version": 0,
> "typeName": "storm_bolt",
> "state": "ACTIVE"
>   },
>   "typeName": "storm_bolt",
>   "values": {
> "name": "count",
> "driverClass": "org.apache.storm.topology.BasicBoltExecutor",
> "conf": {},
> "inputs": ["split"]
>   },
>   "traitNames": ["DataProcessor"],
>   "traits": {
> "DataProcessor": {
>   "jsonClass": 
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Struct",
>   "typeName": "DataProcessor",
>   "values": {}
> }
>   }
> }],
> "owner": "storm",
> "clusterName": "cl1"
>   },
>   "traitNames": [],
>   "traits": {}
> }],
> "type": "ENTITY_CREATE",
> "user": "storm"
>   }
> }
> {code}
> The exception was
> {code}

[jira] [Updated] (ATLAS-567) create upgrade.sh that can be referenced in the documentation

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-567:
--
Priority: Major  (was: Critical)

> create upgrade.sh that can be referenced in the documentation
> -
>
> Key: ATLAS-567
> URL: https://issues.apache.org/jira/browse/ATLAS-567
> Project: Atlas
>  Issue Type: Task
>Affects Versions: 0.7-incubating
>Reporter: Erik Bergenholtz
>Assignee: Erik Bergenholtz
> Attachments: ATLAS-567.patch
>
>
> In order to prepare for future upgrades, it would be nice to have an 
> "upgrade" file that can be invoked that will (in the future) take care of any 
> upgrade steps.
> A first cut of the file will yield an empty file that can be augmented as 
> necessary. This script will also be invoked by external coordinators such as 
> Ambari.



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

[jira] [Commented] (ATLAS-762) Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be hardened

[Shwetha G S (JIRA)]

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

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

[~nixonrodrigues], can you take a look at this?

> Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be 
> hardened
> 
>
> Key: ATLAS-762
> URL: https://issues.apache.org/jira/browse/ATLAS-762
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Nixon Rodrigues
>Priority: Critical
>
> With changes being done to incorporate a new authentication framework in 
> Atlas (ATLAS-661), the assertion in 
> {{NegativeSSLAndKerberosTest.testUnsecuredClient}} was made weaker for 
> Kerberos based environment tests. This bug is to track the change done there 
> and harden the assertion back as is required by the new framework.



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

[jira] [Updated] (ATLAS-762) Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be hardened

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-762:
--
Assignee: Nixon Rodrigues

> Assertion in NegativeSSLAndKerberosTest.testUnsecuredClient needs to be 
> hardened
> 
>
> Key: ATLAS-762
> URL: https://issues.apache.org/jira/browse/ATLAS-762
> Project: Atlas
>  Issue Type: Bug
>Reporter: Hemanth Yamijala
>Assignee: Nixon Rodrigues
>Priority: Critical
>
> With changes being done to incorporate a new authentication framework in 
> Atlas (ATLAS-661), the assertion in 
> {{NegativeSSLAndKerberosTest.testUnsecuredClient}} was made weaker for 
> Kerberos based environment tests. This bug is to track the change done there 
> and harden the assertion back as is required by the new framework.



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

[jira] [Updated] (ATLAS-960) UI: Associating tags/terms is not allowed for deleted entities.

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-960:
--
Summary: UI: Associating tags/terms is not allowed for deleted entities.  
(was: Associating tags/terms is not allowed for deleted entities.)

> UI: Associating tags/terms is not allowed for deleted entities.
> ---
>
> Key: ATLAS-960
> URL: https://issues.apache.org/jira/browse/ATLAS-960
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
>Priority: Critical
> Fix For: 0.7-incubating
>
>
> Associating tag/terms to deleted entities is not allowed through UI, which it 
> should as per ATLAS-670.
> snapshot: https://monosnap.com/file/9QGJh0EwdPnEZyvCi7ohoF6znOu6ES



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

[jira] [Updated] (ATLAS-960) UI: Associating tags/terms is not allowed for deleted entities.

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-960:
--
Priority: Major  (was: Critical)

> UI: Associating tags/terms is not allowed for deleted entities.
> ---
>
> Key: ATLAS-960
> URL: https://issues.apache.org/jira/browse/ATLAS-960
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: 0.7-incubating
>Reporter: Ayub Khan
> Fix For: 0.7-incubating
>
>
> Associating tag/terms to deleted entities is not allowed through UI, which it 
> should as per ATLAS-670.
> snapshot: https://monosnap.com/file/9QGJh0EwdPnEZyvCi7ohoF6znOu6ES



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

[jira] [Resolved] (ATLAS-924) Release 0.7-incubating

[Shwetha G S (JIRA)]

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

Shwetha G S resolved ATLAS-924.
---
Resolution: Fixed

> Release 0.7-incubating
> --
>
> Key: ATLAS-924
> URL: https://issues.apache.org/jira/browse/ATLAS-924
> Project: Atlas
>  Issue Type: Task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
>




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

[jira] [Updated] (ATLAS-936) Update atlas website for 0.7 release

[Shwetha G S (JIRA)]

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

Shwetha G S updated ATLAS-936:
--
Summary: Update atlas website for 0.7 release  (was: Update atlas website)

> Update atlas website for 0.7 release
> 
>
> Key: ATLAS-936
> URL: https://issues.apache.org/jira/browse/ATLAS-936
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-936.patch
>
>




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

[jira] [Assigned] (ATLAS-639) Exception for lineage request

[Vimal Sharma (JIRA)]

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

Vimal Sharma reassigned ATLAS-639:
--

Assignee: Vimal Sharma

> Exception for lineage request
> -
>
> Key: ATLAS-639
> URL: https://issues.apache.org/jira/browse/ATLAS-639
> Project: Atlas
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Ayub Khan
>Assignee: Vimal Sharma
>Priority: Critical
> Fix For: trunk
>
>
> Exception in log for lineage request
> Steps to repro:
>   create table j13 (col4 String);
>   create table j14 (col5 String);
>   insert into table j13 select * from j14;
>   insert into table j14 select * from j13;
> Query for lineage of any of the above two entities..(also keep querying for 
> any other request along with this). Lineage request is timed-out and below 
> error messages are observed in the application log. The below messages are 
> seen continously.(Clean the data dir and manual restart will fix this).
> Environment: Atlas running in embedded mode on local setup.
> {noformat}
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 - 
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit 
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:45,112 DEBUG - [qtp1936542270-298 - 
> fecc3aa7-f4cf-4f6d-89a2-d973c05bc06f:] ~ graph commit 
> (GraphTransactionInterceptor:44)
> 2016-04-06 11:41:48,935 INFO  - [main-SendThread(localhost:9026):] ~ Client 
> session timed out, have not heard from server in 1669ms for sessionid 
> 0x153ea2cd8da002b, closing socket connection and attempting reconnect 
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO  - [SessionTracker:] ~ Expiring session 
> 0x153ea2cd8da002a, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 INFO  - [main-SendThread(localhost:9026):] ~ Client 
> session timed out, have not heard from server in 1917ms for sessionid 
> 0x153ea2cd8da002a, closing socket connection and attempting reconnect 
> (ClientCnxn:1096)
> 2016-04-06 11:41:48,935 INFO  - [SessionTracker:] ~ Expiring session 
> 0x153ea2cd8da002b, timeout of 1000ms exceeded (ZooKeeperServer:347)
> 2016-04-06 11:41:48,935 WARN  - 
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream 
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid 
> 0x153ea2cd8da002b, likely client has closed socket
>   at 
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
>   at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
>   at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,935 INFO  - [ProcessThread(sid:0 cport:-1)::] ~ Processed 
> session termination for sessionid: 0x153ea2cd8da002a 
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO  - [ProcessThread(sid:0 cport:-1)::] ~ Processed 
> session termination for sessionid: 0x153ea2cd8da002b 
> (PrepRequestProcessor:494)
> 2016-04-06 11:41:48,936 INFO  - 
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection 
> for client /127.0.0.1:51657 which had sessionid 0x153ea2cd8da002b 
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:48,936 WARN  - 
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ caught end of stream 
> exception (NIOServerCnxn:357)
> EndOfStreamException: Unable to read additional data from client sessionid 
> 0x153ea2cd8da002a, likely client has closed socket
>   at 
> org.apache.zookeeper.server.NIOServerCnxn.doIO(NIOServerCnxn.java:228)
>   at 
> org.apache.zookeeper.server.NIOServerCnxnFactory.run(NIOServerCnxnFactory.java:208)
>   at java.lang.Thread.run(Thread.java:745)
> 2016-04-06 11:41:48,936 INFO  - 
> [NIOServerCxn.Factory:localhost/127.0.0.1:9026:] ~ Closed socket connection 
> for client /127.0.0.1:51652 which had sessionid 0x153ea2cd8da002a 
> (NIOServerCnxn:1007)
> 2016-04-06 11:41:49,040 INFO  - [main-EventThread:] ~ zookeeper state changed 
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:49,040 INFO  - [main-EventThread:] ~ zookeeper state changed 
> (Disconnected) (ZkClient:711)
> 2016-04-06 11:41:58,894 INFO  - [main-SendThread(localhost:9026):] ~ Opening 
> socket connection to server localhost/127.0.0.1:9026. Will not attempt to 
> authenticate using SASL (unknown error) (ClientCnxn:975)
> 2016-04-06 11:41:58,894 INFO  - 
> [Curator-Framework-0-SendThread(localhost:9026):] ~ Client session timed out, 
> have not heard from server in 11587ms for sessionid 0x153ea2cd8da0025, 
> closing socket connection and attempting reconnect (ClientCnxn:1096)
> 2016-04-06 11:41:58,894 INFO  - [main-SendThread(localhost:9026):] ~ Socket 
> connection established to localhost/127.0.0.1:9026, initiating session 
> (ClientCnxn:852)
> 2016-04-06 11:41:58,894 INFO  - 

[jira] [Commented] (ATLAS-936) Update atlas website

[Vimal Sharma (JIRA)]

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

Vimal Sharma commented on ATLAS-936:


+1

> Update atlas website
> 
>
> Key: ATLAS-936
> URL: https://issues.apache.org/jira/browse/ATLAS-936
> Project: Atlas
>  Issue Type: Sub-task
>Reporter: Shwetha G S
>Assignee: Shwetha G S
> Fix For: 0.7-incubating
>
> Attachments: ATLAS-936.patch
>
>




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