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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 37.03 MB...]
2017-08-26 03:59:38,672 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2630144] (GraphToTypedInstanceMapper:387)
2017-08-26 03:59:38,673 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2630144 type=hive_table 
guid=673580f7-44cd-4bef-b35a-e03ce899ec2f] (GraphHelper:495)
2017-08-26 03:59:38,675 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2630144 type=hive_table 
guid=673580f7-44cd-4bef-b35a-e03ce899ec2f] (GraphHelper:495)
2017-08-26 03:59:38,675 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[aa6a82aa-308a-4e73-88fd-74ed1e25ec4b] 
(GraphBackedMetadataRepository:179)
2017-08-26 03:59:38,676 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[47f2c156-eb94-48cc-a539-e0c6eab27c4d] 
(GraphBackedMetadataRepository:179)
2017-08-26 03:59:38,676 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[29ca0586-2363-4ae2-ac6a-476fe4f097d0] 
(GraphBackedMetadataRepository:179)
2017-08-26 03:59:38,676 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[0d4d4494-e84e-460b-8b6d-d1be2b0f1bb3] 
(GraphBackedMetadataRepository:179)
2017-08-26 03:59:38,676 DEBUG - [NotificationHookConsumer thread-0:] ~ 
Retrieving entities with guids=[982de8c0-bb22-4665-8205-ae68398db66c] 
(GraphBackedMetadataRepository:179)
2017-08-26 03:59:38,827 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":"7185d5c3-bbf8-442b-845c-d2aea2c64eb1","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-26 03:59:38,828 DEBUG - [NotificationHookConsumer thread-0:] ~ Sending 
message for topic ATLAS_ENTITIES: 

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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 32.38 MB...]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] 
[INFO] --- maven-source-plugin:2.4:jar-no-fork (attach-sources) @ hive-bridge 
---
[INFO] Building jar: 

2017-08-26 03:33:10,425 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-26 03:33:10,425 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
[INFO] 
[INFO] --- maven-source-plugin:2.4:test-jar-no-fork (attach-sources) @ 
hive-bridge ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-failsafe-plugin:2.19.1:verify (verify) @ hive-bridge ---
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache Atlas Server Build Tools  SUCCESS [  0.807 s]
[INFO] apache-atlas ... SUCCESS [  4.520 s]
[INFO] Apache Atlas Integration ... SUCCESS [ 25.892 s]
[INFO] Apache Atlas Common  SUCCESS [ 13.329 s]
[INFO] Apache Atlas Typesystem  SUCCESS [ 58.219 s]
[INFO] Apache Atlas Client  SUCCESS [ 15.448 s]
[INFO] Apache Atlas Server API  SUCCESS [  8.629 s]
[INFO] Apache Atlas Notification .. SUCCESS [ 13.914 s]
[INFO] Apache Atlas Graph Database Projects ... SUCCESS [  0.556 s]
[INFO] Apache Atlas Graph Database API  SUCCESS [  6.895 s]
[INFO] Graph Database Common Code . SUCCESS [  7.214 s]
[INFO] Apache Atlas Titan 1.0.0 GraphDB Impl .. SUCCESS [ 27.340 s]
[INFO] Shaded version of Apache hbase client .. SUCCESS [  7.949 s]
[INFO] Apache Atlas Titan 0.5.4 Graph DB Impl . SUCCESS [ 40.398 s]
[INFO] Apache Atlas Graph Database Implementation Dependencies SUCCESS [  0.816 
s]
[INFO] Shaded version of Apache hbase server .. SUCCESS [ 21.570 s]
[INFO] Apache Atlas Repository  SUCCESS [01:40 min]
[INFO] Apache Atlas Authorization . SUCCESS [ 11.095 s]
[INFO] Apache Atlas Business Catalog .. SUCCESS [ 15.414 s]
[INFO] Apache Atlas UI  SUCCESS [ 58.706 s]
[INFO] Apache Atlas Web Application ... SUCCESS [09:44 min]
[INFO] Apache Atlas Documentation . SUCCESS [ 24.085 s]
[INFO] Apache Atlas FileSystem Model .. SUCCESS [  9.012 s]
[INFO] Apache Atlas Plugin Classloader  SUCCESS [ 13.187 s]
[INFO] Apache Atlas Hive Bridge Shim .. SUCCESS [ 19.099 s]
[INFO] Apache Atlas Hive Bridge ... FAILURE [09:04 min]
[INFO] Apache Atlas Falcon Bridge Shim  SKIPPED
[INFO] Apache Atlas Falcon Bridge . SKIPPED
[INFO] Apache Atlas Sqoop Bridge Shim . SKIPPED
[INFO] Apache Atlas Sqoop Bridge .. SKIPPED
[INFO] Apache Atlas Storm Bridge Shim . SKIPPED
[INFO] Apache Atlas Storm Bridge .. SKIPPED
[INFO] Apache Atlas Distribution .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 27:15 min
[INFO] Finished at: 2017-08-26T03:33:10Z
[INFO] Final Memory: 583M/1905M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-failsafe-plugin:2.19.1:verify (verify) on 
project hive-bridge: There are test failures.
[ERROR] 
[ERROR] Please refer to 

Re: [VOTE] Release Apache Atlas 0.8.1 - release candidate 1

2017-08-25 Thread Don Bosco Durai
+1 
- No binary files, except zip files containing json files
- Verified build with -DskipTests=true  (my build env as some issues)

Thanks

Bosco


On 8/25/17, 2:13 PM, "Ramesh Mani"  wrote:

+1 for the rc1 of Apache Atlas 0.8.1 release

Verified the build with the source
https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-
sources.tar.gz


Thanks,
Ramesh

On 8/23/17, 4:48 PM, "Sarath Subramanian"  wrote:

>Atlas team,
>
>I have created a build for Apache Atlas 0.8.1 - release candidate #1.
>Thanks to everyone who have contributed to this release and tested
>this.
>
>
>Changes since last release-candidate:
>
>   - ATLAS-2038: Minor refactoring to use
>org.apache.commons.codec.binary.Base64.
>   - ATLAS-2073: UI - removing tag or type from drop-down will not
>exclude respective filters
>   - ATLAS-2074: AtlasType.resolveReferences() method made package-private
>   - ATLAS-2078: Type update using v1 API doesn't route to
>createUpdateTypesDef in v2 API
>   - ATLAS-2079: Fix coverity scan issue and IT failures introduced by
>ATLAS-2062
>   - ATLAS-2080: fix - tag filters should not be added in the results
>attributes list
>   - ATLAS-2082: basic-search fails when in-memory filters all results
>from index-query
>
>Git tag for the release:
>
>https://github.com/apache/atlas/tree/release-0.8.1-rc1
>
>
>Sources for the release:
>
>https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-
>sources.tar.gz
>
>Source release verification:
>  PGP Signature :
>https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-
>sources.tar.gz.asc
>  MD5 Checksum :
>https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-
>sources.tar.gz.md5
>
>  SHA512 Checksum :
>https://dist.apache.org/repos/dist/dev/atlas/0.8.1-rc1/apache-atlas-0.8.1-
>sources.tar.gz.sha512
>
>Keys to verify the signature of the release artifacts are available at:
>
>https://dist.apache.org/repos/dist/dev/atlas/KEYS
>
>
>List of improvements and issues addressed in this release:
>
>https://issues.apache.org/jira/browse/ATLAS-2066?jql=project%20%3D%20ATLAS
>%20AND%20status%20%3D%20Resolved%20AND%20resolution%20%3D%20Fixed%20AND%20
>fixVersion%20%3D%200.8.1-incubating%20ORDER%20BY%20key%20DESC
>
>
>Note that this is a source only release and we are voting on the
>source *release-0.8.1-rc1*. Please download, test, and try it out.
>
>Voting will be open for at least *72 hours* (until the required number
>of votes are obtained) till 26th August, 2017 04:45 PM PT.
>
>[ ] +1 approve
>[ ] +0 no opinion
>[ ] -1 disapprove (and reason why)
>
>+1 from my side for the release.
>
>
>Thanks,
>
>Sarath Subramanian






Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

2017-08-25 Thread Richard Ding via Review Board


> On Aug. 25, 2017, 9:55 a.m., Nigel Jones wrote:
> > distro/src/bin/atlas_start.py
> > Lines 134 (patched)
> > 
> >
> > I notice we have a hardcoded max time of 5 minutes. I wonder if there's 
> > any scenarios where we might expect longer, and whether we need to add a 
> > -maxtime nn parameter ?
> > 
> > As this is a script which the user can edit I'm not overly concerned 
> > but thought it worth mentioning

Thanks Nigel. It's hard to determine the timeout value. I've talked to Ambari 
developers about how Ambari handles service startup. Ambari delegates service 
startup functions to the service (as defined in Ambari common services). For 
example, Atlas service has following:
```
 
 scripts/metadata_server.py
 PYTHON
 1200
 
```
Each service also provides a server_check script which Ambari runs periodically 
to check server status. Atlas uses following command:
```
smoke_cmd = format('curl -k -s -o /dev/null -w "%{{http_code}}" 
{metadata_protocol}://{atlas_host}:{metadata_port}/')
```
This is similar to what we proposed.


- Richard


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


On Aug. 16, 2017, 11:15 p.m., Richard Ding wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61561/
> ---
> 
> (Updated Aug. 16, 2017, 11:15 p.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-1218
> https://issues.apache.org/jira/browse/ATLAS-1218
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch implements a wait_for_startup function modeled after 
> wait_for_shutdown function.
> 
> 
> Diffs
> -
> 
>   distro/src/bin/atlas_config.py 1be9ca2b 
>   distro/src/bin/atlas_start.py a6a3455c 
> 
> 
> Diff: https://reviews.apache.org/r/61561/diff/4/
> 
> 
> Testing
> ---
> 
> Here are the output of atlas_start and atlas_stop script:
> ```
> starting atlas on port 21000
> 
> Apache Atlas Server started!!!
> ```
> and
> ```
> stopping atlas
> Apache Atlas Server stopped!!!
> ```
> 
> 
> Thanks,
> 
> Richard Ding
> 
>



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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 36.43 MB...]
2017-08-25 22:01:08,575 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=qualifiedName, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=true, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2560256] (GraphToTypedInstanceMapper:387)
2017-08-25 22:01:08,576 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Referenceable.qualifiedName from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,578 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Referenceable.qualifiedName from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,578 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo name (GraphToTypedInstanceMapper:144)
2017-08-25 22:01:08,578 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=name, dataType={name=string, description=null}, 
multiplicity={lower=1, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2560256] (GraphToTypedInstanceMapper:387)
2017-08-25 22:01:08,580 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,581 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.name from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,582 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo description (GraphToTypedInstanceMapper:144)
2017-08-25 22:01:08,582 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=description, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=false, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2560256] (GraphToTypedInstanceMapper:387)
2017-08-25 22:01:08,583 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,584 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.description from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,585 DEBUG - [NotificationHookConsumer thread-0:] ~ Mapping 
attributeInfo owner (GraphToTypedInstanceMapper:144)
2017-08-25 22:01:08,585 DEBUG - [NotificationHookConsumer thread-0:] ~ Adding 
primitive {name=owner, dataType={name=string, description=null}, 
multiplicity={lower=0, upper=1, isUnique=false}, isComposite=false, 
isUnique=false, isIndexable=true, reverseAttributeName=null} from vertex 
Titan0Vertex [id=2560256] (GraphToTypedInstanceMapper:387)
2017-08-25 22:01:08,586 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,587 DEBUG - [NotificationHookConsumer thread-0:] ~ Reading 
property Asset.owner from vertex[id=2560256 type=hive_db 
guid=42795c64-7792-494c-85f7-307da64b7e1e] (GraphHelper:433)
2017-08-25 22:01:08,594 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":"42795c64-7792-494c-85f7-307da64b7e1e","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-25 22:01:10,111 INFO  - [ShutdownMonitor:] ~ Stopping service 
org.apache.atlas.notification.NotificationHookConsumer (Services:65)
2017-08-25 22:01:10,112 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 
(NotificationHookConsumer:173)
2017-08-25 22:01:10,112 INFO  - [ShutdownMonitor:] ~ ==> HookConsumer 
shutdown() (NotificationHookConsumer$HookConsumer:421)
2017-08-25 22:01:10,112 INFO  - [ShutdownMonitor:] ~ 
[atlas-hook-consumer-thread], Shutting down (Logging$class:68)
2017-08-25 22:01:10,666 DEBUG - [main-SendThread(localhost:19026):] ~ 

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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 489.91 KB...]
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "PUT /api/atlas/entities HTTP/1.1" 
200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "GET 
/api/atlas/entities/0b22f44e-1df8-4028-ba43-793fbb1fc439 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:17 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "GET 
/api/atlas/entities/7c515c4b-087a-48e3-85e6-1202281850fa/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "GET 
/api/atlas/entities?type=hive_table HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:18 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraityTXpCBKXLg HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "POST 
/api/atlas/entities/0377cc20-a0d7-4d1a-a565-9c7675b7a965/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "GET 
/api/atlas/entities/0377cc20-a0d7-4d1a-a565-9c7675b7a965/traitDefinitions/PII_TraityTXpCBKXLg
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "GET 
/api/atlas/entities/0377cc20-a0d7-4d1a-a565-9c7675b7a965/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "GET 
/api/atlas/v2/types/typedef/name/PII_TraitLxdj3gIlIv HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:19 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST 
/api/atlas/entities/edd2a937-e9f6-4451-bcd9-8de5dae201bc/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "GET 
/api/atlas/entities/edd2a937-e9f6-4451-bcd9-8de5dae201bc/audit?count=100 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "GET 
/api/atlas/entities/d9c37287-540b-4764-ab2c-c1a0e1416121 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "DELETE 
/api/atlas/entities/68684687-7269-441e-9896-55636ce93556/traits/blah_trait 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "GET /api/atlas/entities/blah 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "GET 
/api/atlas/v2/types/typedef/name/testWOoLnE2OPr HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:20 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:21 +] "GET 
/api/atlas/entities?type=testWOoLnE2OPr HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:21 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:21 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:21 +] "PUT /api/atlas/types HTTP/1.1" 200 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:22 +] "GET 
/api/atlas/entities/69a5bba6-a996-449d-a45a-3f36f9461b59 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:22 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:21:51:22 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"

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

2017-08-25 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS:2012: Dockerfile to build and run Atlas

--
[...truncated 497.02 KB...]
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET /api/atlas/entities/blah 
HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET 
/api/atlas/v2/types/typedef/name/PII_Traitpl0kJOhk8q HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST 
/api/atlas/entities/e2ba2f7f-827f-45dd-8a3f-3d2f77f5ca18/traits HTTP/1.1" 201 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET 
/api/atlas/entities/e2ba2f7f-827f-45dd-8a3f-3d2f77f5ca18/traitDefinitions/PII_Traitpl0kJOhk8q
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET 
/api/atlas/entities/e2ba2f7f-827f-45dd-8a3f-3d2f77f5ca18/traitDefinitions 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET 
/api/atlas/entities/6612cf96-9255-4d37-80d1-591010446146/traits HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST 
/api/atlas/entities/ba8f2780-2621-4fe4-8878-4a8344d8ac79 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "GET 
/api/atlas/entities/ba8f2780-2621-4fe4-8878-4a8344d8ac79 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:33 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST 
/api/atlas/entities/qualifiedName?type=hive_table=qualifiedName=tableNQp4vPFIQ7
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "GET 
/api/atlas/entities/9e6dd99d-e443-4f70-99bd-3176f62ec19b HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "GET 
/api/atlas/entities/d3eeb0fd-0279-4452-9355-052e5d82d6cb/audit?count=10 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
400 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "GET 
/api/atlas/v2/types/typedef/name/lKv2XwOm8x HTTP/1.1" 404 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/types HTTP/1.1" 201 
- "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/entities HTTP/1.1" 
201 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "GET 
/api/atlas/entities/b40b3dd9-5d00-4706-b3c4-2ace0d8a09a4 HTTP/1.1" 200 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "GET 
/api/atlas/v2/entity/guid/c3dfbd72-a1b4--8deb-0600735ca3d7 HTTP/1.1" 200 - 
"-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST 
/api/atlas/v2/entity/guid/random/classifications HTTP/1.1" 404 - "-" 
"Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/v2/entity/bulk/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:34 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:35 +] "DELETE 
/api/atlas/v2/entity/bulk/?guid=e257914d-d52c-4bce-9436-7bce4e004478=0ccec334-b452-4790-8579-910c0604ec0e
 HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - [25/Aug/2017:19:44:35 +] "POST /api/atlas/v2/entity/ 
HTTP/1.1" 200 - "-" "Java/1.7.0_80"
127.0.0.1 - - 

Re: Review Request 61913: ATLAS-2012: Build docker image

2017-08-25 Thread Madhan Neethiraj


> On Aug. 25, 2017, 6:18 p.m., Apoorv Naik wrote:
> > dev-support/atlas-docker/Dockerfile
> > Lines 52 (patched)
> > 
> >
> > Just curious as to why we're logging into hbase shell

I had the same question.

I think it will be better to tail Atlas log file with: 'tail -fF 
/root/atlas-bin/logs/application.log'.

Rest of the patch is good. Thanks Nigel.


- Madhan


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


On Aug. 25, 2017, 1:14 p.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61913/
> ---
> 
> (Updated Aug. 25, 2017, 1:14 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
> Richard Ding.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2012: Build docker image
> 
> Note: Unit tests are currently not run within the docker image build process. 
> As per the JIRA it would be nice to include these but currently the tests 
> fail in many ways. This is an independent issue to the docker image work, and 
> so I propose opening a new JIRA to re-enable UT once build is stable, but 
> meanwhile we can get the docker support in
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/Dockerfile PRE-CREATION 
>   dev-support/atlas-docker/README.md PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61913/diff/1/
> 
> 
> Testing
> ---
> 
> * check image can be rebuilt repeatedly
> * checker Atlas image starts up correctly
> * Run some unit tests in built image (note: see mailing list for discussion 
> about current IT test failures in builds)
> * Verified Atlas Web UI is accessible
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>



Re: Review Request 61913: ATLAS-2012: Build docker image

2017-08-25 Thread Madhan Neethiraj

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


Ship it!




Ship It!

- Madhan Neethiraj


On Aug. 25, 2017, 1:14 p.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61913/
> ---
> 
> (Updated Aug. 25, 2017, 1:14 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
> Richard Ding.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2012: Build docker image
> 
> Note: Unit tests are currently not run within the docker image build process. 
> As per the JIRA it would be nice to include these but currently the tests 
> fail in many ways. This is an independent issue to the docker image work, and 
> so I propose opening a new JIRA to re-enable UT once build is stable, but 
> meanwhile we can get the docker support in
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/Dockerfile PRE-CREATION 
>   dev-support/atlas-docker/README.md PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61913/diff/1/
> 
> 
> Testing
> ---
> 
> * check image can be rebuilt repeatedly
> * checker Atlas image starts up correctly
> * Run some unit tests in built image (note: see mailing list for discussion 
> about current IT test failures in builds)
> * Verified Atlas Web UI is accessible
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>



[jira] [Updated] (ATLAS-2083) Refactor AtlasDefStore classes to reduce code duplication

2017-08-25 Thread Richard Ding (JIRA)

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

Richard Ding updated ATLAS-2083:

Attachment: ATLAS-2083_1.patch

Rebased the patch on the latest master branch.

> Refactor AtlasDefStore classes to reduce code duplication
> ---
>
> Key: ATLAS-2083
> URL: https://issues.apache.org/jira/browse/ATLAS-2083
> Project: Atlas
>  Issue Type: Improvement
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2083_1.patch, ATLAS-2083.patch
>
>
> Currently each top-level TypeDef defines its own DefStore interface. These 
> interfaces have the same methods.  I suggest that we use generic interface to 
> reduce the code duplication.
> We can also tighten the type restriction on these interfaces. Replacing 
> Object reference with AtlasVertex reference.



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


Re: Review Request 61871: ATLAS-2083: Refactor AtlasDefStore classes to reduce code duplication

2017-08-25 Thread Richard Ding via Review Board

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

(Updated Aug. 25, 2017, 6:44 p.m.)


Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
Sarath Subramanian.


Changes
---

Uploaded a new patch rebased on the latest master branch.


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


Repository: atlas


Description
---

1. Use generic interface to reduce code duplication
2. Move the common code in the implementation classes to the base class
3. Tighten the types required in the interface methods 
4. Move two test classes to the correct package


Diffs (updated)
-

  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasClassificationDefStore.java
 92a59f39 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasDefStore.java
 PRE-CREATION 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEntityDefStore.java
 08391ba5 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasEnumDefStore.java
 d0f98e2f 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasRelationshipDefStore.java
 df67958b 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasStructDefStore.java
 ebd2b706 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/AtlasTypeDefGraphStore.java
 f5e16182 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasAbstractDefStoreV1.java
 baf23092 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasClassificationDefStoreV1.java
 89445048 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEntityDefStoreV1.java
 d6cb2fd4 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasEnumDefStoreV1.java
 39c4dd93 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasRelationshipDefStoreV1.java
 bdde58bc 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasStructDefStoreV1.java
 62729e79 
  
repository/src/main/java/org/apache/atlas/repository/store/graph/v1/AtlasTypeDefGraphStoreV1.java
 ab738495 
  repository/src/test/java/org/apache/atlas/TestModules.java 4bc14872 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/AtlasEntityDefStoreV1Test.java
 5f011362 
  
repository/src/test/java/org/apache/atlas/repository/store/graph/AtlasRelationshipDefStoreV1Test.java
 00d49779 


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

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


Testing
---

All unit tests passed.


Thanks,

Richard Ding



Re: Review Request 61913: ATLAS-2012: Build docker image

2017-08-25 Thread Apoorv Naik

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




dev-support/atlas-docker/Dockerfile
Lines 52 (patched)


Just curious as to why we're logging into hbase shell


- Apoorv Naik


On Aug. 25, 2017, 1:14 p.m., Nigel Jones wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61913/
> ---
> 
> (Updated Aug. 25, 2017, 1:14 p.m.)
> 
> 
> Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
> Richard Ding.
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> ATLAS-2012: Build docker image
> 
> Note: Unit tests are currently not run within the docker image build process. 
> As per the JIRA it would be nice to include these but currently the tests 
> fail in many ways. This is an independent issue to the docker image work, and 
> so I propose opening a new JIRA to re-enable UT once build is stable, but 
> meanwhile we can get the docker support in
> 
> 
> Diffs
> -
> 
>   dev-support/atlas-docker/Dockerfile PRE-CREATION 
>   dev-support/atlas-docker/README.md PRE-CREATION 
> 
> 
> Diff: https://reviews.apache.org/r/61913/diff/1/
> 
> 
> Testing
> ---
> 
> * check image can be rebuilt repeatedly
> * checker Atlas image starts up correctly
> * Run some unit tests in built image (note: see mailing list for discussion 
> about current IT test failures in builds)
> * Verified Atlas Web UI is accessible
> 
> 
> Thanks,
> 
> Nigel Jones
> 
>



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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 33.17 MB...]
2017-08-25 18:10:08,379 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":"6a0430e6-13d4-4b30-bf69-fee3b784da48","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-25 18:10:08,380 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":"966f2116-65c2-4546-868b-baae79fb5dd8","version":0,"typeName":"hive_table","state":"ACTIVE"},"typeName":"hive_table","values":{"tableType":"EXTERNAL_TABLE","name":"tablej0juf4womu","createTime":"2017-08-25T18:08:19.000Z","temporary":false,"db":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"6a0430e6-13d4-4b30-bf69-fee3b784da48","version":0,"typeName":"hive_db","state":"ACTIVE"},"retention":0,"qualifiedName":"default.tablej0juf4womu@primary","columns":[{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"01283146-0fef-4557-b030-323990642921","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"id","qualifiedName":"default.tablej0juf4womu.id@primary","position":0,"owner":"jenkins","type":"int","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"966f2116-65c2-4546-868b-baae79fb5dd8","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-25T18:10:04.344Z","modifiedTime":"2017-08-25T18:10:06.754Z"}},{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"42402d5c-7791-4add-afcd-535703df7fc7","version":0,"typeName":"hive_column","state":"ACTIVE"},"typeName":"hive_column","values":{"name":"name","qualifiedName":"default.tablej0juf4womu.name@primary","position":1,"owner":"jenkins","type":"string","table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"966f2116-65c2-4546-868b-baae79fb5dd8","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-25T18:10:04.344Z","modifiedTime":"2017-08-25T18:10:06.754Z"}}],"comment":"table
 
comment","lastAccessTime":"2017-08-25T18:08:19.000Z","owner":"jenkins","sd":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"01eeff44-0a40-42b5-9545-1cbbbf0dbab8","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.tablej0juf4womu@primary_storage","outputFormat":"org.apache.hadoop.hive.ql.io.HiveIgnoreKeyTextOutputFormat","compressed":false,"numBuckets":-1,"inputFormat":"org.apache.hadoop.mapred.TextInputFormat","storedAsSubDirectories":false,"table":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"966f2116-65c2-4546-868b-baae79fb5dd8","version":0,"typeName":"hive_table","state":"ACTIVE"}},"traitNames":[],"traits":{},"systemAttributes":{"createdBy":"jenkins","modifiedBy":"jenkins","createdTime":"2017-08-25T18:10:04.344Z","modifiedTime":"2017-08-25T18:10:06.754Z"}},"parameters":{"comment":"table
 

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

2017-08-25 Thread Apache Jenkins Server
See 


--
[...truncated 39.83 MB...]
2017-08-25 18:07:49,472 INFO  - [ShutdownMonitor:] ~ ==> stopConsumerThreads() 
(NotificationHookConsumer:175)
2017-08-25 18:07:49,473 INFO  - [ShutdownMonitor:] ~ ==> HookConsumer 
shutdown() (NotificationHookConsumer$HookConsumer:423)
2017-08-25 18:07:49,473 INFO  - [ShutdownMonitor:] ~ 
[atlas-hook-consumer-thread], Shutting down (Logging$class:68)
2017-08-25 18:07:49,844 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:49,845 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:49,846 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e1a8f3a450001 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-25 18:07:50,080 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:50,081 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:51,393 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:51,393 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:51,394 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e1a8f3a450001 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-25 18:07:51,918 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:51,918 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:52,138 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:52,139 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:52,325 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:52,325 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:52,326 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e1a8f3a450001 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-25 18:07:53,754 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 18:07:53,755 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 18:07:53,756 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e1a8f3a450001 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 

Re: Emtity Resource v1 test failures

2017-08-25 Thread Sarath Subramanian
Nigel,
I agree we all need to spend some time and clean up these tests. Feel free
to open JIRA's for the failing tests.

I see the integration tests consistently failing in hive-bridge module due
to Lock timeout exception - I suspect this is because of some stale open
transaction lingering around which also modified/read the same property,
since Berkley DB is ACID compliant subsequent transactions times out since
the previous transaction is not closed properly. We don't see this in HBase
since its not an ACID compliant.


Thanks,
Sarath Subramanian

On Fri, Aug 25, 2017 at 7:10 AM, Apoorv Naik  wrote:

> I think Sarath already made changes for this one don't know why this
> failed again. Perhaps we need to revisit the integration tests after all.
>
> One jira per test failure should be a great way to split work amongst the
> community.
>
> Sent from Nine
> 
> From: Nigel Jones 
> Sent: Aug 25, 2017 5:06 AM
> To: dev@atlas.apache.org
> Subject: Re: Emtity Resource v1 test failures
>
>
> On 2017-08-25 12:28, "Nigel Jones" wrote:
>
> >  I rebased this morning, but am still getting a failure - albeit a
> different one - this looks like a timeout issue whilst the previous were
> seemingly more functional. Is there a JIRA you are tracking these under?
> Should I create one per failure?
> >
> > I'll retry
> >
> > Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
> 109.969 sec <<< FAILURE! - in TestSuite
> > testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT)  Time
> elapsed: 1.537 sec  <<< FAILURE!
>
> Another build, another random error - timing could be a factor (certainly
> in the earlier test). This however is one of the build failures I had
> yesterday. It's also been seen in the Jenkins build
>
>  FAILURE! - in TestSuite
> runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed:
> 0.344 sec  <<< FAILURE!
> org.apache.atlas.AtlasServiceException: Metadata service API
> org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 failed with status 409
> (Conflict) Response Body 
> ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given
> type Dimension already exists"})
> at org.apache.atlas.examples.QuickStartV2IT.runQuickStart(
> QuickStartV2IT.java:49)
>
>
> Results :
>
> Failed tests:
>   QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API
> org.apache...
>
> Tests run: 134, Failures: 1, Errors: 0, Skipped: 5
>
>
> I feel we do need to between us all try and get these tests running
> cleanly, as it's otherwise very tempting to run skip-tests and risk
> suggesting a change/patch that causes a failure. (I was trying to get a
> solid baseline before trying to start on a new API)
>
> We could even consider a short term change to the build to not stop if any
> known, problematic tests fail - still run, but continue. may help?
>
>


Re: Emtity Resource v1 test failures

2017-08-25 Thread Apoorv Naik
I think Sarath already made changes for this one don't know why this failed 
again. Perhaps we need to revisit the integration tests after all.

One jira per test failure should be a great way to split work amongst the 
community.

Sent from Nine

From: Nigel Jones 
Sent: Aug 25, 2017 5:06 AM
To: dev@atlas.apache.org
Subject: Re: Emtity Resource v1 test failures


On 2017-08-25 12:28, "Nigel Jones" wrote:

>  I rebased this morning, but am still getting a failure - albeit a different 
> one - this looks like a timeout issue whilst the previous were seemingly more 
> functional. Is there a JIRA you are tracking these under? Should I create one 
> per failure?
>
> I'll retry
>
> Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec 
> <<< FAILURE! - in TestSuite
> testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT)  Time 
> elapsed: 1.537 sec  <<< FAILURE!

Another build, another random error - timing could be a factor (certainly in 
the earlier test). This however is one of the build failures I had yesterday. 
It's also been seen in the Jenkins build

 FAILURE! - in TestSuite
runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed: 0.344 
sec  <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 failed with status 409 
(Conflict) Response Body ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given 
type Dimension already exists"})
at 
org.apache.atlas.examples.QuickStartV2IT.runQuickStart(QuickStartV2IT.java:49)


Results :

Failed tests:
  QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API 
org.apache...

Tests run: 134, Failures: 1, Errors: 0, Skipped: 5


I feel we do need to between us all try and get these tests running cleanly, as 
it's otherwise very tempting to run skip-tests and risk suggesting a 
change/patch that causes a failure. (I was trying to get a solid baseline 
before trying to start on a new API)

We could even consider a short term change to the build to not stop if any 
known, problematic tests fail - still run, but continue. may help?



Re: Review Request 61736: ATLAS-2049 Document common standards for OMAS interfaces

2017-08-25 Thread Nigel Jones

Hi all,
 We now have a number of OMAS APIs being designed and developed. There have 
been a number of discussions around best practices/standards, and the document 
below is an initial attempt to get these written down.

I'm sure this will be an evolving list, but it would be really useful to get 
the discussion flowing, so if anyone can spend the time to take a look it would 
be most appreciated.

This started as a list of notes for a discussion so it's far from complete and 
perhaps not detailed enough but we can start somewhere :-)

Note that it's created as a patch against the twiki docs, but we can also 
discuss where this documentation SHOULD go 

Thanks!
Nigel.


On 2017-08-18 15:55, Nigel Jones  wrote: 

> https://reviews.apache.org/r/61736/

> ATLAS-2049 Document common standards for OMAS interfaces
> 
> As we start to build OMAS interfaces it seems having some common standards 
> would be a good idea. I wanted to get this discussion going so opted to 
> document this in twiki format & submit via review board. The intent isn't 
> this first pass is correct, but that we come to a consensus ...



[jira] [Created] (ATLAS-2086) Docker - reenable unit tests in build once IT stable

2017-08-25 Thread Nigel Jones (JIRA)
Nigel Jones created ATLAS-2086:
--

 Summary: Docker - reenable unit tests in build once IT stable
 Key: ATLAS-2086
 URL: https://issues.apache.org/jira/browse/ATLAS-2086
 Project: Atlas
  Issue Type: Bug
Reporter: Nigel Jones


A build of a docker image for atlas was created under ATLAS-2012.
An initial comment from David was that it would be better to build with tests 
enabled. I agree - this makes sense in case there's something different about 
the docker (ubuntu) environment from the host, and would be good to spot even 
though the build takes longer
However with Jenkins build failing regularly, and with some other intermittent 
tests failing as per a recent mailing list discussion I am instead leaving 2012 
without UT, and raising this issue to re-introduce it when things are stable. 
That way we get the docker support in, but also don't forget to read testing as 
soon as we can.



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


Review Request 61913: ATLAS-2012: Build docker image

2017-08-25 Thread Nigel Jones

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

Review request for atlas, Apoorv Naik, David Radley, Madhan Neethiraj, and 
Richard Ding.


Repository: atlas


Description
---

ATLAS-2012: Build docker image

Note: Unit tests are currently not run within the docker image build process. 
As per the JIRA it would be nice to include these but currently the tests fail 
in many ways. This is an independent issue to the docker image work, and so I 
propose opening a new JIRA to re-enable UT once build is stable, but meanwhile 
we can get the docker support in


Diffs
-

  dev-support/atlas-docker/Dockerfile PRE-CREATION 
  dev-support/atlas-docker/README.md PRE-CREATION 


Diff: https://reviews.apache.org/r/61913/diff/1/


Testing
---

* check image can be rebuilt repeatedly
* checker Atlas image starts up correctly
* Run some unit tests in built image (note: see mailing list for discussion 
about current IT test failures in builds)
* Verified Atlas Web UI is accessible


Thanks,

Nigel Jones



[jira] [Updated] (ATLAS-2012) Docker - image & hub - for Atlas

2017-08-25 Thread Nigel Jones (JIRA)

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

Nigel Jones updated ATLAS-2012:
---
Attachment: ATLAS-2012-Build-docker-image.patch

> Docker - image & hub - for Atlas
> 
>
> Key: ATLAS-2012
> URL: https://issues.apache.org/jira/browse/ATLAS-2012
> Project: Atlas
>  Issue Type: New Feature
>Reporter: Nigel Jones
>Assignee: Nigel Jones
> Attachments: ATLAS-2012-Build-docker-image.patch, 
> atlas_docker1.patch, atlas_docker_2.patch, atlas_docker.patch
>
>
> Docker is increasingly become a standard way of easily running components in 
> a flexible manner, whether for development, production, or test
> I feel there are a few things we can do with docker that will aid Atlas's 
> appeal
> 1. We could provide a simple example of how to create a docker image from the 
> Atlas build. This could be published on the wiki & it would make it easier 
> for developers to use Atlas within a docker environment - mostly by 
> addressing how to configure & start up
> 2. We could automatically generate a docker image as part of the build 
> process. This builds on #1 by automating the creation of the image & making 
> it "just part of the build"
> 3. We could publish the docker image from #2, for releases, to dockerhub, 
> making it near trivial for any developer to easily pull down and experiment 
> with Atlas. Full source of course would be provided/documented so that a user 
> could customize as needed for their environment plus of course improve what 
> is provided with the core project
> 4. We could work with other teams especially ranger, to allow similar efforts 
> in other teams to easily work together & be orchestrated 



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


Re: Emtity Resource v1 test failures

2017-08-25 Thread Nigel Jones

On 2017-08-25 12:28, "Nigel Jones" wrote: 

>  I rebased this morning, but am still getting a failure - albeit a different 
> one - this looks like a timeout issue whilst the previous were seemingly more 
> functional. Is there a JIRA you are tracking these under? Should I create one 
> per failure?
> 
> I'll retry
> 
> Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec 
> <<< FAILURE! - in TestSuite
> testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT)  Time 
> elapsed: 1.537 sec  <<< FAILURE!

Another build, another random error - timing could be a factor (certainly in 
the earlier test). This however is one of the build failures I had yesterday. 
It's also been seen in the Jenkins build

 FAILURE! - in TestSuite
runQuickStart(org.apache.atlas.examples.QuickStartV2IT)  Time elapsed: 0.344 
sec  <<< FAILURE!
org.apache.atlas.AtlasServiceException: Metadata service API 
org.apache.atlas.AtlasBaseClient$APIInfo@1a990d3 failed with status 409 
(Conflict) Response Body ({"errorCode":"ATLAS-409-00-001","errorMessage":"Given 
type Dimension already exists"})
at 
org.apache.atlas.examples.QuickStartV2IT.runQuickStart(QuickStartV2IT.java:49)


Results :

Failed tests: 
  QuickStartV2IT.runQuickStart:49 » AtlasService Metadata service API 
org.apache...

Tests run: 134, Failures: 1, Errors: 0, Skipped: 5


I feel we do need to between us all try and get these tests running cleanly, as 
it's otherwise very tempting to run skip-tests and risk suggesting a 
change/patch that causes a failure. (I was trying to get a solid baseline 
before trying to start on a new API)

We could even consider a short term change to the build to not stop if any 
known, problematic tests fail - still run, but continue. may help?


Re: Emtity Resource v1 test failures

2017-08-25 Thread Nigel Jones


On 2017-08-24 18:45, Sarath Subramanian  wrote: 
> Hi Nigel,
> 
> Few Integration Test fixes have gone into master in the last couple of
> days, could you rebase master and try the tests again.

Hi Sarath,
 I rebased this morning, but am still getting a failure - albeit a different 
one - this looks like a timeout issue whilst the previous were seemingly more 
functional. Is there a JIRA you are tracking these under? Should I create one 
per failure?

I'll retry

Tests run: 133, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 109.969 sec 
<<< FAILURE! - in TestSuite
testLineageIsMaintained(org.apache.atlas.examples.QuickStartIT)  Time elapsed: 
1.537 sec  <<< FAILURE!
java.lang.AssertionError: 
at 
org.apache.atlas.examples.QuickStartIT.testLineageIsMaintained(QuickStartIT.java:130)


Results :

Failed tests: 
  QuickStartIT.testLineageIsMaintained:130



Re: About the way traits are stored in TitanDB

2017-08-25 Thread David Radley
Hi Benjamin,
The way Atlas is architected is that there is one graph for types and a 
separate graph for the instances. I see a lot of benefits with this 
design. Having edges between the types allows us to navigate and check 
types consistency with gremlin queries. It means we can implement search 
using  gremlin queries looking at the instance graph. I think for Atlas 
this allows us to manage the metadata types and instances with some degree 
of insolation in the graph store. I think the way the type system is 
designed at the graph level is great strength of Atlas. 

 We are also thinking that this will allow us, in the future, to have 
namespaces - for example one for test and one for development and one for 
production; each of which will have separate instance graph but all using 
the same type graph. 

Of course there are many way to store data in graphs. Mixing types and 
instances together in one big property graph is the approach RDF takes.
   all the best, David. 




From:   BONNET Benjamin 
To: "dev@atlas.apache.org" 
Date:   25/08/2017 11:03
Subject:About the way traits are stored in TitanDB



Hi all,

Working on Atlas repository in Titan, I am surprised by the way traits are 
stored : traits type are Vertices, which seems ok, but traits instances 
are Vertices too.
So, when you attach a trait to an entity, Atlas will create a new Vertex 
(containing the attributes that are set) and draw an Edge between the 
entity instance Vertex and that trait instance Vertex. There is no edge 
between the trait instance Vertex and the trait type Vertex : there is 
just a __typeName attribute in the trait instance that contains the traits 
type (please, tell me if I missed something...).

Actually, I would rather have expected to have the trait instance stored 
as an Edge between the entity instance Vertex and the trait type Vertex. 
That edge would contain the attributes values.
The advantages of modeling traits instances as Edges are :

-  The link between a trait and its type is enforced by the 
database itself and does not rely on a __typeName attribute.

-  Less Vertices in the database, without growing Edges number.

-  The data stored in Titan will look more like a graph : today, 
my data consists of lots of Vertices that are isolated (all types) and 
there are few edges. So I think we cannot really take advantage of the DB 
graph-orientation.

What do you think about that ?

Regards,

Benjamin






Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU


About the way traits are stored in TitanDB

2017-08-25 Thread BONNET Benjamin
Hi all,

Working on Atlas repository in Titan, I am surprised by the way traits are 
stored : traits type are Vertices, which seems ok, but traits instances are 
Vertices too.
So, when you attach a trait to an entity, Atlas will create a new Vertex 
(containing the attributes that are set) and draw an Edge between the entity 
instance Vertex and that trait instance Vertex. There is no edge between the 
trait instance Vertex and the trait type Vertex : there is just a __typeName 
attribute in the trait instance that contains the traits type (please, tell me 
if I missed something...).

Actually, I would rather have expected to have the trait instance stored as an 
Edge between the entity instance Vertex and the trait type Vertex. That edge 
would contain the attributes values.
The advantages of modeling traits instances as Edges are :

-  The link between a trait and its type is enforced by the database 
itself and does not rely on a __typeName attribute.

-  Less Vertices in the database, without growing Edges number.

-  The data stored in Titan will look more like a graph : today, my 
data consists of lots of Vertices that are isolated (all types) and there are 
few edges. So I think we cannot really take advantage of the DB 
graph-orientation.

What do you think about that ?

Regards,

Benjamin





Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

2017-08-25 Thread Nigel Jones


> On Aug. 11, 2017, 12:11 p.m., David Radley wrote:
> > distro/src/bin/atlas_config.py
> > Lines 71 (patched)
> > 
> >
> > I am uncomfortable duplicating the default port values here. I suggest 
> > moving this logic to the java class that already has the default port values
> 
> Richard Ding wrote:
> The default ports are hard-coded in Java class:
> ```
> appPort = StringUtils.isEmpty(enableTLSFlag) || 
> enableTLSFlag.equals("true") ?
> configuration.getInt(ATLAS_SERVER_HTTPS_PORT, 21443) :
> configuration.getInt(ATLAS_SERVER_HTTP_PORT, 21000);
> ```
> It's also difficult to access Java class from python code.
> 
> David Radley wrote:
> hi Richard , unless you move the polling logic into Java code (in a 
> separate thread) - so you have more control over it. I assume the process 
> starts right away, but the delay is in web server code prior to it opening 
> the port. all the best, David.
> 
> Richard Ding wrote:
> You are right. The polling logic is in the startup python script which 
> has no access to Java classes. 
> 
> The process is started by the python script (atlas_start.py) and the 
> script has no way to know when the server initialization is complete. So 
> inside the startup script the best we can do is to ping the port. After 
> changing the code to use socket module, the code is simplified and it appears 
> to work well even with SSL port.

(I know this issue is closed). I think the loose coupling, python script, and 
making a dummy socket connection make sense (as that is basically what the end 
user on a browser would do). But in terms of spreading defaults across multiple 
places (I'm thinking docs, scripts, java source), we could do a pre-processing 
step which would insert and/or update ports in docs, scripts, java etc - not 
sure it's worth the effort though. (so won't reopen)


- Nigel


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


On Aug. 17, 2017, 12:15 a.m., Richard Ding wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61561/
> ---
> 
> (Updated Aug. 17, 2017, 12:15 a.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-1218
> https://issues.apache.org/jira/browse/ATLAS-1218
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch implements a wait_for_startup function modeled after 
> wait_for_shutdown function.
> 
> 
> Diffs
> -
> 
>   distro/src/bin/atlas_config.py 1be9ca2b 
>   distro/src/bin/atlas_start.py a6a3455c 
> 
> 
> Diff: https://reviews.apache.org/r/61561/diff/4/
> 
> 
> Testing
> ---
> 
> Here are the output of atlas_start and atlas_stop script:
> ```
> starting atlas on port 21000
> 
> Apache Atlas Server started!!!
> ```
> and
> ```
> stopping atlas
> Apache Atlas Server stopped!!!
> ```
> 
> 
> Thanks,
> 
> Richard Ding
> 
>



Re: Review Request 61561: ATLAS-1218: Atlas says it is started but does not accept REST requests

2017-08-25 Thread Nigel Jones

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




distro/src/bin/atlas_start.py
Lines 134 (patched)


I notice we have a hardcoded max time of 5 minutes. I wonder if there's any 
scenarios where we might expect longer, and whether we need to add a -maxtime 
nn parameter ?

As this is a script which the user can edit I'm not overly concerned but 
thought it worth mentioning


- Nigel Jones


On Aug. 17, 2017, 12:15 a.m., Richard Ding wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61561/
> ---
> 
> (Updated Aug. 17, 2017, 12:15 a.m.)
> 
> 
> Review request for atlas, David Radley, Madhan Neethiraj, and Sarath 
> Subramanian.
> 
> 
> Bugs: ATLAS-1218
> https://issues.apache.org/jira/browse/ATLAS-1218
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> This patch implements a wait_for_startup function modeled after 
> wait_for_shutdown function.
> 
> 
> Diffs
> -
> 
>   distro/src/bin/atlas_config.py 1be9ca2b 
>   distro/src/bin/atlas_start.py a6a3455c 
> 
> 
> Diff: https://reviews.apache.org/r/61561/diff/4/
> 
> 
> Testing
> ---
> 
> Here are the output of atlas_start and atlas_stop script:
> ```
> starting atlas on port 21000
> 
> Apache Atlas Server started!!!
> ```
> and
> ```
> stopping atlas
> Apache Atlas Server stopped!!!
> ```
> 
> 
> Thanks,
> 
> Richard Ding
> 
>



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

2017-08-25 Thread Apache Jenkins Server
See 


Changes:

[madhan] ATLAS-2076: update type-search to support filter by RELATIONSHIP type

[madhan] ATLAS-2060: Fix logger class name typos

--
[...truncated 35.67 MB...]
at 
org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
2017-08-25 08:57:01,159 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:01,160 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:01,700 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:01,701 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:01,701 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e189681810002 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-25 08:57:01,824 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:01,824 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:02,782 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:02,783 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:02,783 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e189681810002 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-25 08:57:03,905 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:03,905 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:03,958 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:03,959 DEBUG - [main-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:03,960 WARN  - [main-SendThread(localhost:19026):] ~ Session 
0x15e189681810002 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-25 08:57:04,181 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:04,181 DEBUG - 
[Curator-Framework-0-SendThread(localhost:19026):] ~ <== 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client): {} 
(InMemoryJAASConfiguration:238)
2017-08-25 08:57:04,225 DEBUG - [main-SendThread(localhost:19026):] ~ ==> 
InMemoryJAASConfiguration.getAppConfigurationEntry(Client) 
(InMemoryJAASConfiguration:208)
2017-08-25 08:57:04,226 DEBUG - [main-SendThread(localhost:19026):] ~ <== 

[jira] [Resolved] (ATLAS-2060) Fix logger class name typos

2017-08-25 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj resolved ATLAS-2060.
-
Resolution: Fixed

Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/86863339.

Thanks [~sding].

> Fix logger class name typos
> ---
>
> Key: ATLAS-2060
> URL: https://issues.apache.org/jira/browse/ATLAS-2060
> Project: Atlas
>  Issue Type: Bug
>  Components: atlas-intg
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
>Priority: Trivial
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2060.patch
>
>
> There are two classes in intg module that have incorrect logger class names.



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


[jira] [Resolved] (ATLAS-2076) Add RELATIONSHIP type to search filters

2017-08-25 Thread Madhan Neethiraj (JIRA)

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

Madhan Neethiraj resolved ATLAS-2076.
-
Resolution: Fixed

Committed to master: 
http://git-wip-us.apache.org/repos/asf/atlas/commit/a6c0793f

Thanks [~sding].

> Add RELATIONSHIP type to search filters
> ---
>
> Key: ATLAS-2076
> URL: https://issues.apache.org/jira/browse/ATLAS-2076
> Project: Atlas
>  Issue Type: Bug
>  Components:  atlas-core
>Affects Versions: 0.8-incubating
>Reporter: Richard Ding
>Assignee: Richard Ding
>Priority: Minor
> Fix For: 0.9-incubating
>
> Attachments: ATLAS-2076_1.patch, ATLAS-2076.patch
>
>
> The command
> {code}
> curl -X GET -u admin:admin 
> http://localhost:21000/api/atlas/v2/types/typedefs/headers?type=relationship
> {code}
> returns empty result. 



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


Re: Review Request 61665: ATLAS-2047: Exception Thrown by Kafka Consumer Ends up Filling Logs Due to Incorrect Handling

2017-08-25 Thread Madhan Neethiraj

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




webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
Lines 274 (patched)


I think it will be useful to abstract this functionality in a class of its 
own.

class AdaptiveWaiter {
  public AdaptiveWaiter(long minWaitTime, long maxWaitTime, long 
waitIncrement) {
resetInterval = maxWaitTime * 2;
  }

  public wait(String message) {
long now   = System.currentTimeMillis();
long timeSinceLastWait = now - lastWaitAt;

if (timeSinceLastWait > resetInterval) { // it has been a long time 
since the last call
  waitTime = minWaitTime;
} else {
  waitTime = timeSinceLastWait + waitIncrement;

  if (waitTime > maxWaitTime) {
waitTime = maxWaitTime;
  }
}

lastWaitAt = now;

LOG.debug(...);

sleep(waitTime);
  }


- Madhan Neethiraj


On Aug. 17, 2017, 5:04 a.m., Ashutosh Mestry wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/61665/
> ---
> 
> (Updated Aug. 17, 2017, 5:04 a.m.)
> 
> 
> Review request for atlas, Madhan Neethiraj and Nixon Rodrigues.
> 
> 
> Bugs: ATLAS-2047
> https://issues.apache.org/jira/browse/ATLAS-2047
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> Please refer to 
> [ATLAS-2047](https://issues.apache.org/jira/browse/ATLAS-2047) for background 
> and analysis.
> 
> **Background**
> 
> The _IllegalStateException_ is thrown by _KafkaConsumer.aquire_. This method 
> is called at the beginning of almost every method in this class. The method 
> checks if the consumer is closed, if it is then it throws 
> IllegalStateException.
> 
> Scenario may come about in this way:
> - Shutdown has been initiated. Close on consumer is called.
> - However, the consumer thread is just about to enter another poll cycle.
> - Thus acquire sees that consumer is closed and throws the exception (2nd 
> bullet above).
> 
> Please take a look at this scala code. This is _ShutdownableThread_. The 
> thread does the job of handling all exceptions. Upon exception, it manages 
> the _shutdownLatch_ (from yesterday’s bug fix) and gets out of the 
> _isRunning_ loop.
> ```scala
>   override def run(): Unit = {
> info("Starting ")
> try{
>   while(isRunning.get()){
> doWork()
>   }
> } catch{
>   case e: Throwable =>
> if(isRunning.get())
>   error("Error due to ", e)
> }
> shutdownLatch.countDown()
> info("Stopped ")
>   }
> ```
> 
> **Implementation**
> 
> Special treatment is given to _IllegalStateException_ by implementing pause & 
> retry logic:
> - Modified _LOG_ to _debug_. That way logs are not filled during retry.
> - _HookConsumer_ is more resilient. It handles exceptions resulting from 
> _Kafka_ and entity APIs.
> 
> 
> Diffs
> -
> 
>   
> webapp/src/main/java/org/apache/atlas/notification/NotificationHookConsumer.java
>  ef64c3b 
>   
> webapp/src/test/java/org/apache/atlas/notification/NotificationHookConsumerTest.java
>  a6f58e8 
> 
> 
> Diff: https://reviews.apache.org/r/61665/diff/2/
> 
> 
> Testing
> ---
> 
> **Unit tests**
> Updated unit tests to reproduce the scenarios and verify the fix.
> 
> **Functional tests**
> Verified regular notification scenarios.
> 
> 
> Thanks,
> 
> Ashutosh Mestry
> 
>