[jira] [Assigned] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat reassigned ATLAS-2104:
--

Assignee: Keval Bhatt

> Atlas UI Improvements: Tag CRUD operations UI
> -
>
> Key: ATLAS-2104
> URL: https://issues.apache.org/jira/browse/ATLAS-2104
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8.1-incubating
>Reporter: Srikanth Venkat
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: TagDetailsAddedAttr.png
>
>
> 1. Missing labels in Edit tag popup: A Tag could have the same Name and 
> Description attribute values. In this case, when editing a tag, the Edit 
> Description modal does not communicate that only "Description" attribute 
> value is editable and "Name" is not editable. Also since the field does not 
> have any label it is confusing as to what attribute is allowed to be modified 
> on edit. It would be nice to prefix the attribute name to the edit dialogs 
> for updating the value (i.e. show "Name :" and "Description :" as prefixes to 
> the field values being edited so it is very clear which field is being edited.
> 2. Background color of Tag Delete popup confirmation can be improved to be a 
> more neutral and lighter color. 
> 3. On Tag details page, a previously added attribute and the button for 
> adding a new attribute could be made visually different so the call to action 
> for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png)
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat updated ATLAS-2104:
---
Component/s: atlas-webui

> Atlas UI Improvements: Tag CRUD operations UI
> -
>
> Key: ATLAS-2104
> URL: https://issues.apache.org/jira/browse/ATLAS-2104
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8.1-incubating
>Reporter: Srikanth Venkat
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: TagDetailsAddedAttr.png
>
>
> 1. Missing labels in Edit tag popup: A Tag could have the same Name and 
> Description attribute values. In this case, when editing a tag, the Edit 
> Description modal does not communicate that only "Description" attribute 
> value is editable and "Name" is not editable. Also since the field does not 
> have any label it is confusing as to what attribute is allowed to be modified 
> on edit. It would be nice to prefix the attribute name to the edit dialogs 
> for updating the value (i.e. show "Name :" and "Description :" as prefixes to 
> the field values being edited so it is very clear which field is being edited.
> 2. Background color of Tag Delete popup confirmation can be improved to be a 
> more neutral and lighter color. 
> 3. On Tag details page, a previously added attribute and the button for 
> adding a new attribute could be made visually different so the call to action 
> for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png)
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat updated ATLAS-2104:
---
Description: 
1. Missing labels in Edit tag popup: A Tag could have the same Name and 
Description attribute values. In this case, when editing a tag, the Edit 
Description modal does not communicate that only "Description" attribute value 
is editable and "Name" is not editable. Also since the field does not have any 
label it is confusing as to what attribute is allowed to be modified on edit. 
It would be nice to prefix the attribute name to the edit dialogs for updating 
the value (i.e. show "Name :" and "Description :" as prefixes to the field 
values being edited so it is very clear which field is being edited.

2. Background color of Tag Delete popup confirmation can be improved to be a 
more neutral and lighter color. 


3. On Tag details page, a previously added attribute and the button for adding 
a new attribute could be made visually different so the call to action for the 
user is more clearer. See attached mockup (TagDetailsAddedAttr.png)

 

  was:
1. Missing labels in Edit tag popup: A Tag could have the same Name and 
Description attribute values. In this case, when editing a tag, the Edit 
Description modal does not communicate that only "Description" attribute value 
is editable and "Name" is not editable. Also since the field does not have any 
label it is confusing as to what attribute is allowed to be modified on edit. 
It would be nice to prefix the attribute name to the edit dialogs for updating 
the value (i.e. show "Name :" and "Description :" as prefixes to the field 
values being edited so it is very clear which field is being edited.

2. Background color of Tag Delete popup confirmation can be improved to be a 
more neutral and lighter color. 


3. On Tag details page, Ta previously added attribute and the button for adding 
attribute could be made visually different so the call to action for the user 
is clearer. See attached mockup (TagDetailsAddedAttr.png)

 


> Atlas UI Improvements: Tag CRUD operations UI
> -
>
> Key: ATLAS-2104
> URL: https://issues.apache.org/jira/browse/ATLAS-2104
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8.1-incubating
>Reporter: Srikanth Venkat
>Priority: Critical
> Attachments: TagDetailsAddedAttr.png
>
>
> 1. Missing labels in Edit tag popup: A Tag could have the same Name and 
> Description attribute values. In this case, when editing a tag, the Edit 
> Description modal does not communicate that only "Description" attribute 
> value is editable and "Name" is not editable. Also since the field does not 
> have any label it is confusing as to what attribute is allowed to be modified 
> on edit. It would be nice to prefix the attribute name to the edit dialogs 
> for updating the value (i.e. show "Name :" and "Description :" as prefixes to 
> the field values being edited so it is very clear which field is being edited.
> 2. Background color of Tag Delete popup confirmation can be improved to be a 
> more neutral and lighter color. 
> 3. On Tag details page, a previously added attribute and the button for 
> adding a new attribute could be made visually different so the call to action 
> for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png)
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI

[Srikanth Venkat (JIRA)]

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

Srikanth Venkat updated ATLAS-2104:
---
Affects Version/s: 0.8.1-incubating

> Atlas UI Improvements: Tag CRUD operations UI
> -
>
> Key: ATLAS-2104
> URL: https://issues.apache.org/jira/browse/ATLAS-2104
> Project: Atlas
>  Issue Type: Improvement
>  Components: atlas-webui
>Affects Versions: 0.8.1-incubating
>Reporter: Srikanth Venkat
>Assignee: Keval Bhatt
>Priority: Critical
> Attachments: TagDetailsAddedAttr.png
>
>
> 1. Missing labels in Edit tag popup: A Tag could have the same Name and 
> Description attribute values. In this case, when editing a tag, the Edit 
> Description modal does not communicate that only "Description" attribute 
> value is editable and "Name" is not editable. Also since the field does not 
> have any label it is confusing as to what attribute is allowed to be modified 
> on edit. It would be nice to prefix the attribute name to the edit dialogs 
> for updating the value (i.e. show "Name :" and "Description :" as prefixes to 
> the field values being edited so it is very clear which field is being edited.
> 2. Background color of Tag Delete popup confirmation can be improved to be a 
> more neutral and lighter color. 
> 3. On Tag details page, a previously added attribute and the button for 
> adding a new attribute could be made visually different so the call to action 
> for the user is more clearer. See attached mockup (TagDetailsAddedAttr.png)
>  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2104) Atlas UI Improvements: Tag CRUD operations UI

[Srikanth Venkat (JIRA)]

Srikanth Venkat created ATLAS-2104:
--

 Summary: Atlas UI Improvements: Tag CRUD operations UI
 Key: ATLAS-2104
 URL: https://issues.apache.org/jira/browse/ATLAS-2104
 Project: Atlas
  Issue Type: Improvement
Reporter: Srikanth Venkat
Priority: Critical
 Attachments: TagDetailsAddedAttr.png

1. Missing labels in Edit tag popup: A Tag could have the same Name and 
Description attribute values. In this case, when editing a tag, the Edit 
Description modal does not communicate that only "Description" attribute value 
is editable and "Name" is not editable. Also since the field does not have any 
label it is confusing as to what attribute is allowed to be modified on edit. 
It would be nice to prefix the attribute name to the edit dialogs for updating 
the value (i.e. show "Name :" and "Description :" as prefixes to the field 
values being edited so it is very clear which field is being edited.

2. Background color of Tag Delete popup confirmation can be improved to be a 
more neutral and lighter color. 


3. On Tag details page, Ta previously added attribute and the button for adding 
attribute could be made visually different so the call to action for the user 
is clearer. See attached mockup (TagDetailsAddedAttr.png)

 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2103) Atlas UI Improvements: Confirmation modal dialog for entity/tag CRUD operations needs to be improved

[Srikanth Venkat (JIRA)]

Srikanth Venkat created ATLAS-2103:
--

 Summary: Atlas UI Improvements: Confirmation modal dialog for 
entity/tag CRUD operations needs to be improved
 Key: ATLAS-2103
 URL: https://issues.apache.org/jira/browse/ATLAS-2103
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-webui
Affects Versions: 0.8.1-incubating
Reporter: Srikanth Venkat
Assignee: Keval Bhatt
Priority: Critical
 Attachments: ConfDialogBoxIssues.png

The confirmation dialog when CRUD operations are performed on entities or tags 
has text that is wrapped with incorrect line breaks and the background color 
needs to be made lighter to offer a better user experience - see attached 
screenshot.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (ATLAS-2102) Atlas UI Improvements: Search results page

[Srikanth Venkat (JIRA)]

Srikanth Venkat created ATLAS-2102:
--

 Summary: Atlas UI Improvements: Search results page 
 Key: ATLAS-2102
 URL: https://issues.apache.org/jira/browse/ATLAS-2102
 Project: Atlas
  Issue Type: Improvement
  Components: atlas-webui
Affects Versions: 0.8.1-incubating
Reporter: Srikanth Venkat
Assignee: Keval Bhatt
Priority: Critical
 Attachments: SearchResultsInfoHierarchyUpdates.png

1. Information hierarchy for the text on Search results page needs to be 
improved. Please see the attached mockup (SearchResultsInfoHierarchyUpdates.png)

2. Previous and Next button should not be present is the number of search 
results is less than the current page size.

3. Search results table shifts visually if the show historical properties is 
selected (moves right and down by ~20px) needs to have consistent position in 
the layout. 

4. Edit entity action on Search results table should appear on hover and should 
not be shown next to the column next to the resulting set fof entity names in 
as it create unnecessary visual clutter in the table.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

[Ashutosh Mestry]

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

(Updated Sept. 1, 2017, 1:47 a.m.)


Review request for atlas and Apoorv Naik.


Changes
---

Updates include:
- Added license header.


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


Repository: atlas


Description
---

**Details**
- Added _StandardIDPool_ to _Titan0_ Shaded JAR.
- Replace use of _Stopwatch_ with custom logic.


Diffs (updated)
-

  
graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
 PRE-CREATION 


Diff: https://reviews.apache.org/r/62009/diff/2/

Changes: https://reviews.apache.org/r/62009/diff/1-2/


Testing
---


Thanks,

Ashutosh Mestry

Re: Review Request 59821: ATLAS-1805:Provide an Atlas hook to send Hbase Namespace/Table/column family metadata to Atlas

[Ramesh Mani]

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

(Updated Aug. 31, 2017, 10:52 p.m.)


Review request for atlas and Madhan Neethiraj.


Changes
---

Patch after reviews


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


Repository: atlas


Description
---

ATLAS-1805: Provide an Atlas hook to send Hbase Namespace/Table/column family 
metadata to Atlas


Diffs (updated)
-

  addons/hbase-bridge-shim/pom.xml PRE-CREATION 
  
addons/hbase-bridge-shim/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  addons/hbase-bridge/pom.xml PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/bridge/HBaseAtlasHook.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/event/HBaseEvent.java 
PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessor.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/hook/HBaseAtlasCoprocessorBase.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseContext.java
 PRE-CREATION 
  
addons/hbase-bridge/src/main/java/org/apache/atlas/hbase/model/HBaseDataTypes.java
 PRE-CREATION 
  addons/hbase-bridge/src/main/resources/atlas-hbase-import-log4j.xml 
PRE-CREATION 
  
addons/hbase-bridge/src/test/java/org/apache/atlas/hbase/HBaseAtlasHookTest.java
 PRE-CREATION 
  addons/models/0060-hbase_model.json 3e46e06 
  distro/src/main/assemblies/standalone-package.xml 215cb23 
  pom.xml 8b9eee6 


Diff: https://reviews.apache.org/r/59821/diff/3/

Changes: https://reviews.apache.org/r/59821/diff/2-3/


Testing
---

* Review comments fixed with 2 exceptions whcih I have commented on 
* Added an IT test
* Testing done in LOCAL VM


Thanks,

Ramesh Mani

[jira] [Commented] (ATLAS-1690) Introduce top level relationships

[Pierre Padovani (JIRA)]

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

Pierre Padovani commented on ATLAS-1690:


Two questions on this work:

1) Can a RelationshipType inherit from another RelationshipType?

2) If yes for #1, how does that affect tag propagation?

My use case: Given a set of metadata that belongs to a particular customer, 
where we use a classification with an attribute that contains the customer id, 
we would want that classification to propagate to all related entities. If we 
had a relationship type that was generic in nature and specified that the 
classification for the customer propagated, it would be nice to be able to 
specify sub-types that provide additional behaviors. 

> Introduce top level relationships
> -
>
> Key: ATLAS-1690
> URL: https://issues.apache.org/jira/browse/ATLAS-1690
> Project: Atlas
>  Issue Type: Improvement
>Reporter: David Radley
>Assignee: David Radley
>  Labels: VirtualDataConnector
> Attachments: Atlas_RelationDef_Json_Structure_v1.pdf, Atlas 
> Relationships proposal v1.0.pdf, Atlas Relationships proposal v1.10.pdf, 
> Atlas Relationships proposal v1.1.pdf, Atlas Relationships proposal v1.2.pdf, 
> Atlas Relationships proposal v1.3.pdf, Atlas Relationships proposal v1.4.pdf, 
> Atlas Relationships proposal v1.5.pdf, Atlas Relationships proposal v1.6.pdf, 
> Atlas Relationships proposal v1.7.pdf, Atlas Relationships proposal v1.8.pdf, 
> Atlas Relationships proposal v1.9.pdf
>
>
> Introduce top level relationships including support for 
> -many to many relationships
> - relationship names including the name for both ends and the relationship.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Build failed in Jenkins: Atlas-0.8-IntegrationTests #38

[Apache Jenkins Server]

See 


--
[...truncated 32.97 MB...]
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[d99caa2d-bbc9-43db-b67e-ccdc42cb0f79] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[b64ed909-827d-4c75-887b-15cc3b8c7064] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[c18efcb2-1473-43e0-915c-bf8faa000582] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,439 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[ae62af07-0968-448e-bd5a-78b2533da774] 
(GraphBackedMetadataRepository:179)
2017-08-31 18:32:07,509 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c465d3a8-b86c-4356-8458-1a4d258a7247","version":0,"typeName":"hive_db","state":"ACTIVE"},"typeName":"hive_db","values":{"name":"default","location":":"Default
 Hive 
database","ownerType":{"value":"ROLE","ordinal":2},"qualifiedName":"default@primary","owner":"public","clusterName":"primary"},"traitNames":[],"traits":{},"systemAttributes":{}},"operationType":"ENTITY_UPDATE","traits":[]}}
 (KafkaNotification:218)
2017-08-31 18:32:07,509 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 
{"version":{"version":"1.0.0"},"message":{"entity":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"},"typeName":"hive_table","values":{"tableType":"EXTERNAL_TABLE","name":"tablegrrjapqmwu","createTime":"2017-08-31T18:30:26.000Z","temporary":false,"db":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c465d3a8-b86c-4356-8458-1a4d258a7247","version":0,"typeName":"hive_db","state":"ACTIVE"},"retention":0,"qualifiedName":"default.tablegrrjapqmwu@primary","columns":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"d99caa2d-bbc9-43db-b67e-ccdc42cb0f79","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"id","qualifiedName":"default.tablegrrjapqmwu.id@primary","position":0,"owner":"jenkins","type":"int","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T18:32:01.998Z","modifiedTime":"2017-08-31T18:32:06.518Z"}},{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"b64ed909-827d-4c75-887b-15cc3b8c7064","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"name","qualifiedName":"default.tablegrrjapqmwu.name@primary","position":1,"owner":"jenkins","type":"string","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c20ff0f3-a2de-46ca-acd5-a293269ade6a","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-31T18:32:01.998Z","modifiedTime":"2017-08-31T18:32:06.518Z"}}],"comment":"table
 
comment","lastAccessTime":"2017-08-31T18:30:26.000Z","owner":"jenkins","sd":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"c18efcb2-1473-43e0-915c-bf8faa000582","version":0,"typeName":"hive_storagedesc","state":"ACTIVE"},"typeName":"hive_storagedesc","values":{"location":"p:{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Struct","typeName":"hive_serde","values":{"serializationLib":"org.apache.hadoop.hive.serde2.lazy.LazySimpleSerDe","parameters":{"serialization.format":"1"}}},"qualifiedName":"default.tablegrrjapqmwu@primary_storage","outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat","compressed":false,"numBuckets"

Build failed in Jenkins: Atlas-master-UnitTests #51

[Apache Jenkins Server]

See 

--
[...truncated 451.33 KB...]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ 
atlas-webapp ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 50 source files to 

[WARNING] 
:
 Some input files use or override a deprecated API.
[WARNING] 
:
 Recompile with -Xlint:deprecation for details.
[WARNING] 
:
 Some input files use unchecked or unsafe operations.
[WARNING] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-war-plugin:2.6:war (default-war) @ atlas-webapp ---
[INFO] Packaging webapp
[INFO] Assembling webapp [atlas-webapp] in 
[
[INFO] Processing overlay [ id org.apache.atlas:atlas-dashboardv2]
[INFO] Processing war project
[INFO] Copying webapp resources 
[
[INFO] Building jar: 

[INFO] Webapp assembled in [1328 msecs]
[INFO] Building war: 

[INFO] 
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
atlas-webapp ---
[INFO] 
[INFO] --- enunciate-maven-plugin:2.8.0:docs (default) @ atlas-webapp ---
[INFO] [ENUNCIATE] Skipping enunciate per configuration.
[INFO] 
[INFO] --- maven-surefire-plugin:2.18.1:test (default-test) @ atlas-webapp ---
[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

---
 T E S T S
---
Running org.apache.atlas.notification.AdaptiveWaiterTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 5.012 sec - in 
org.apache.atlas.notification.AdaptiveWaiterTest
Running org.apache.atlas.notification.NotificationEntityChangeListenerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.049 sec - in 
org.apache.atlas.notification.NotificationEntityChangeListenerTest
Running org.apache.atlas.notification.NotificationHookConsumerTest
Tests run: 12, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 9.284 sec <<< 
FAILURE! - in org.apache.atlas.notification.NotificationHookConsumerTest
consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(org.apache.atlas.notification.NotificationHookConsumerTest)
  Time elapsed: 2.565 sec  <<< FAILURE!
java.lang.AssertionError: 
at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
at org.testng.AssertJUnit.assertTrue(AssertJUnit.java:24)
at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:41)
at org.testng.AssertJUnit.assertFalse(AssertJUnit.java:49)
at 
org.apache.atlas.notification.NotificationHookConsumerTest.consumersThrowsIllegalStateExceptionPauseRetryLogicIsInterrupted(NotificationHookConsumerTest.java:290)

Running org.apache.atlas.notification.NotificationHookConsumerKafkaTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.337 sec - in 
org.apache.atlas.notification.NotificationHookConsumerKafkaTest
Running org.apache.atlas.web.security.FileAuthenticationTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.087 sec - in 
org.apache.atlas.web.security.FileAuthenticationTest
Running org.apache.atlas.web.security.NegativeSSLAndKerberosTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.972 sec - in 
org.apache.atlas.web.security.NegativeSS

Build failed in Jenkins: Atlas-master-IntegrationTests #55

[Apache Jenkins Server]

See 


--
[...truncated 40.67 MB...]
2017-08-31 18:21:48,190 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:48,272 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:48,272 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:48,273 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e398222ad0002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-31 18:21:49,436 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:49,436 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:49,437 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e398222ad0002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-31 18:21:50,129 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:50,130 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:50,250 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:50,250 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:50,342 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:50,343 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:50,343 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e398222ad0002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-31 18:21:52,170 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:52,171 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-31 18:21:52,172 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e398222ad0002 for server null, unexpected error, closing socket connection 
and attempting reconnect (ClientCnxn$SendThread:1102)
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at 
sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:744)
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-31 18:21:52,310 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-31 18:21:52,310 DEBUG - 
[Curat

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

[Sarath Subramanian]

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


Ship it!




Ship It!

- Sarath Subramanian


On Aug. 30, 2017, 10:02 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 30, 2017, 10:02 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

[Sarath Subramanian]

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




graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
Lines 1 (patched)


Need to add apache license header. getting rat failure.


- Sarath Subramanian


On Aug. 30, 2017, 10:02 p.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 30, 2017, 10:02 p.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

[Apoorv Naik]

> On Aug. 31, 2017, 5:48 p.m., Apoorv Naik wrote:
> > Ship It!

I'll commit once I review/test some scenarios. Code wise the changes look good.


- Apoorv


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


On Aug. 31, 2017, 5:02 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 31, 2017, 5:02 a.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

Re: Review Request 62009: ATLAS-2101: Update Implementation to Eliminate Use of Stopwatch

[Apoorv Naik]

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


Ship it!




Ship It!

- Apoorv Naik


On Aug. 31, 2017, 5:02 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/62009/
> ---
> 
> (Updated Aug. 31, 2017, 5:02 a.m.)
> 
> 
> Review request for atlas and Apoorv Naik.
> 
> 
> Bugs: ATLAS-2101
> https://issues.apache.org/jira/browse/ATLAS-2101
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> **Details**
> - Added _StandardIDPool_ to _Titan0_ Shaded JAR.
> - Replace use of _Stopwatch_ with custom logic.
> 
> 
> Diffs
> -
> 
>   
> graphdb/titan0/src/main/java/com/thinkaurelius/titan/graphdb/database/idassigner/StandardIDPool.java
>  PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/62009/diff/1/
> 
> 
> Testing
> ---
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>

[jira] [Updated] (ATLAS-2092) Failures following concurrent updates

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry updated ATLAS-2092:
---
Attachment: import-nested-txn.patch

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: import-nested-txn.patch, Investigations and findings 
> relating to concurrent updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (ATLAS-2092) Failures following concurrent updates

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry edited comment on ATLAS-2092 at 8/31/17 4:45 PM:
-

[~grahamwallis] I am reading the PDF now. Analysis is comprehensive and I find 
it interesting read. Thanks for putting this together!

One thing we have noticed is that version of _Berkeley DB_ we are using has a 
few problems.  Mostly around transactions commits. Only yesterday we were 
contemplating on effort required to move our tests to use embedded HBASE and 
embedded Solr. We have not reached any conclusion yet. Doing this would help us 
get around some of the intermittent failures we see in test environments. It 
will also make our unit & IT tests run in an environment that is close to 
production.

How easy is it for you to duplicate this problem on HBASE/Solr setup? It would 
be interesting to see the results.

About 'double wrapping of transactions' (Appendix, Observation 2). I had worked 
on trying to resolve it. Please find patch attached.


was (Author: ashutoshm):
[~grahamwallis] I am reading the PDF now. Analysis is comprehensive and I find 
it interesting read. Thanks for putting this together!

One thing we have noticed is that version of _Berkeley DB_ we are using has a 
few problems.  Mostly around transactions commits. Only yesterday we were 
contemplating on effort required to move our tests to use embedded HBASE and 
embedded Solr. We have not reached any conclusion yet. Doing this would help us 
get around some of the intermittent failures we see in test environments. It 
will also make our unit & IT tests run in an environment that is close to 
production.

How easy is it for you to duplicate this problem on HBASE/Solr setup? It would 
be interesting to see the results.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-2092:


[~grahamwallis] I am reading the PDF now. Analysis is comprehensive and I find 
it interesting read. Thanks for putting this together!

One thing we have noticed is that version of _Berkeley DB_ we are using has a 
few problems.  Mostly around transactions commits. Only yesterday we were 
contemplating on effort required to move our tests to use embedded HBASE and 
embedded Solr. We have not reached any conclusion yet. Doing this would help us 
get around some of the intermittent failures we see in test environments. It 
will also make our unit & IT tests run in an environment that is close to 
production.

How easy is it for you to duplicate this problem on HBASE/Solr setup? It would 
be interesting to see the results.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2101) Remove use of Guava Stopwatch from Atlas

[Ashutosh Mestry (JIRA)]

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

Ashutosh Mestry commented on ATLAS-2101:


[~grahamwallis] This had cost me an entire week when I was new to Atlas.

> Remove use of Guava Stopwatch from Atlas
> 
>
> Key: ATLAS-2101
> URL: https://issues.apache.org/jira/browse/ATLAS-2101
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: trunk
>
> Attachments: StandardIDPool.java
>
>
> *Background*
> Using _IntelliJ_ attempt to start Atlas server. Chances are the startup will 
> fail due to error in resolving _com.google.common.base.StopWatch_.
> Similar problem is observed on some build environments.
> *Solution*
> * Add _StandardIDPool.java_ to shaded _Titan0_ JAR. 
> * Replace use of _Stopwatch_ with some alternative implementation.
> See also: [HBASE-14963|https://issues.apache.org/jira/browse/HBASE-14963]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2092:
--

Thanks Nigel, 
I agree that it would be better to avoid undesirable workarounds and yes, we 
could ship a patched version of the graph code - in fact we do that for other 
reasons already. 
However I am now somewhat less hopeful than I was that we can fix this in the 
graph layer alone. I tried to prototype a fix for the problem by testing with a 
locally patched JanusGraph -  I introduced a synchronization block around the 
test and create of the edge label and its schema vertex. Unfortunately it 
didn't work - and I was silly to think that it would - I had expected the 
schema vertex to become immediately visible (e.g. in the schema cache) to the 
other threads. But that wasn't very sensible, because the system is 
transactional. We wouldn't expect the edge label schema vertex or the edge 
itself to be visible until the transaction is committed. So I think the 'fix' 
currently appears more elaborate - it either needs to apply heavy 
synchronization (which I don't think would be desirable), or it needs to split 
the label creation and the edge creation into separate transactions, the former 
of which would be synchronized. The obvious failure condition (of committing 
the create a label but rolling back the creation of the edge) would be benign - 
it would just mean there's an unused edge label schema vertex. This split and 
synch approach would probably be needed anywhere that we create a schema 
vertex, so it could be a little pervasive.

There may be some lower hanging fruit - such as ensuring that we never ask the 
real graph vertex to perform a getEdges with a label; but instead to always 
query via the GraphHelper. This would not avoid the duplication issue, but it 
would mean you get back correct answers to queries. We could (I think) perform 
such a redirect in the implementations of AtlasVertex. I spent a little while 
this afternoon scanning for places where we ask for edges by label and it looks 
like it could be a manageable change. The above only applies to edge labels, so 
I am also looking at the other roles of schema vertices - i.e. for property 
keys and vertex labels.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

[Nigel Jones (JIRA)]

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

Nigel Jones commented on ATLAS-2092:


thanks for the very thorough write-up and walk through.

In terms of resolution a little thinking 'out-loud'

* At the point we switch to janus and drop titan 0.54 we ideally don't want any 
workarounds in that version of the code, but we may need to make sure we 
address any odd things in the graph during a migration step?
* You mention that fixing titan 0.54 is unrealistic. I understand there is no 
longer any support/activity, it's a dead end. However if it is a small, precise 
change that is required, I still wonder if could build a patch that can be 
applied to 0.54, and ship it with atlas. We could also ensure the libraries we 
supply have it included (needs a build), and perhaps detect on startup, and log 
an error if patch isn't in place. Though this is a bit tedious, I still wonder 
if it's safer or more controlled than adding a fair bit of workaround code. may 
be worth thinking about?
* However in the case of any fix (as in previous point) am I right in thinking 
once this has occurred it may continue to cause functional issues since the key 
will always be out of the correct range? In which case we'd still either need 
to be able to detect, and/or self-heal/fix on demand, or have a fix-script 
available for old atlas users? this may make my previous point somewhat mute.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2092:
--

OK - seems to have worked this time - sorry about that.

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (ATLAS-2092) Failures following concurrent updates

[Graham Wallis (JIRA)]

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

Graham Wallis updated ATLAS-2092:
-
Attachment: Investigations and findings relating to concurrent updates in 
Atlas.pdf

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
> Attachments: Investigations and findings relating to concurrent 
> updates in Atlas.pdf
>
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2092) Failures following concurrent updates

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2092:
--

Hi Ashutosh,
That's weird - I am sure I attached the details to this issue immediately after 
the call on Tuesday - but I don't see it - let me try again :-)

> Failures following concurrent updates
> -
>
> Key: ATLAS-2092
> URL: https://issues.apache.org/jira/browse/ATLAS-2092
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Reporter: Graham Wallis
>
> There is a race condition that causes duplication of schema vertices as a 
> result of concurrent graph updates. This in turn leads to failure of queries 
> that specify a type such as an edge label used in an attribute that 
> references another entity. This problem is known to affect Atlas entity refs 
> – which create graph edges that use edge label schema vertices. It is likely 
> that it also affects other types in Atlas.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (ATLAS-2101) Remove use of Guava Stopwatch from Atlas

[Graham Wallis (JIRA)]

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

Graham Wallis commented on ATLAS-2101:
--

Hi Ashutosh,
I have, in the past, seen problems caused by the change in Guava v17 from using 
a public StopWatch constructor to a private constructor called by a factory 
method. Some of the Atlas stack depends on the older style and I think my build 
had picked up the wrong version of Guava, although I don't recall why.
I agree that if we possible we should remove the dependency altogether.

> Remove use of Guava Stopwatch from Atlas
> 
>
> Key: ATLAS-2101
> URL: https://issues.apache.org/jira/browse/ATLAS-2101
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: trunk
>Reporter: Ashutosh Mestry
>Assignee: Ashutosh Mestry
>Priority: Minor
> Fix For: trunk
>
> Attachments: StandardIDPool.java
>
>
> *Background*
> Using _IntelliJ_ attempt to start Atlas server. Chances are the startup will 
> fail due to error in resolving _com.google.common.base.StopWatch_.
> Similar problem is observed on some build environments.
> *Solution*
> * Add _StandardIDPool.java_ to shaded _Titan0_ JAR. 
> * Replace use of _Stopwatch_ with some alternative implementation.
> See also: [HBASE-14963|https://issues.apache.org/jira/browse/HBASE-14963]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)