date:20161226

Re: Hive Hook - what is missing ?

2016-12-26 Thread Hemanth Yamijala

Hi,

A few questions to help debug:

1) Are you using Hive CLI or Beeline? Best results would be to
configure these hooks with HiveServer2 and use Beeline.

2) Could you please check hive logs and look for AtlasHook related messages?

Thanks
Hemanth

On Mon, Dec 26, 2016 at 8:59 PM, Russell Anderson  wrote:
>
>
> Hi dev list,
>
> I have built the Atlas7rc2 - have working the Hive Import, the Dashboard,
> and generally things appear to be working as expected.
>
> However, I have followed the instruction below but cannot seem to get the
> Hive Hook to detect table hive creations to be added to the metadata /
> lineage.
>
> Can anyone suggest how to debug what could be missing regardless of
> following the instructions below ? Any and all help appreciated !!!
>
> Regards,
>
> Russ.
>
> =
>
> Hive Hook
>
>
> Hive supports listeners on hive command execution using hive hooks. This is
> used to add/update/remove entities in Atlas using the model defined in
> org.apache.atlas.hive.model.HiveDataModelGenerator. The hook submits the
> request to a thread pool executor to avoid blocking the command execution.
> The thread submits the entities as message to the notification server and
> atlas server reads these messages and registers the entities. Follow these
> instructions in your hive set-up to add hive hook for Atlas:
>   Set-up atlas hook in hive-site.xml of your hive configuration:
> 
>   hive.exec.post.hooks
>   org.apache.atlas.hive.hook.HiveHook
> 
>
>
> 
>   atlas.cluster.name
>   primary
> 
>
>
>   Add 'export HIVE_AUX_JARS_PATH=/hook/hive' in
>   hive-env.sh of your hive configuration
>   Copy /atlas-application.properties to the hive conf
>   directory.
>
>
> The following properties in /atlas-application.properties
> control the thread pool and notification details:
>   atlas.hook.hive.synchronous - boolean, true to run the hook
>   synchronously. default false. Recommended to be set to false to avoid
>   delays in hive query completion.
>   atlas.hook.hive.numRetries - number of retries for notification
>   failure. default 3
>   atlas.hook.hive.minThreads - core number of threads. default 5
>   atlas.hook.hive.maxThreads - maximum number of threads. default 5
>   atlas.hook.hive.keepAliveTime - keep alive time in msecs. default 10
>   atlas.hook.hive.queueSize - queue size for the threadpool. default
>   1

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

2016-12-26 Thread Apache Jenkins Server

See 

Changes:

[madhan] ATLAS-1415: fix potential NPE issues found by Coverity scan

--
[...truncated 3356 lines...]
Running 
org.apache.atlas.repository.typestore.StoreBackedTypeCacheConfigurationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.632 sec - in 
org.apache.atlas.repository.typestore.StoreBackedTypeCacheConfigurationTest
Running org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.547 sec - in 
org.apache.atlas.repository.typestore.StoreBackedTypeCacheTest
Running org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 13.102 sec - in 
org.apache.atlas.repository.typestore.GraphBackedTypeStoreTest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.176 sec - in 
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryHATest
Running org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 21.58 sec - in 
org.apache.atlas.repository.audit.HBaseBasedAuditRepositoryTest
Running org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.721 sec - in 
org.apache.atlas.repository.audit.InMemoryAuditRepositoryTest
Running org.apache.atlas.repository.BaseTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.25 sec - in 
org.apache.atlas.repository.BaseTest
Running org.apache.atlas.query.ExpressionTest
Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.358 sec - in 
org.apache.atlas.query.ExpressionTest
Running org.apache.atlas.query.LineageQueryTest
Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 19.422 sec - in 
org.apache.atlas.query.LineageQueryTest
Running org.apache.atlas.query.GremlinTest
Tests run: 21, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 26.346 sec - 
in org.apache.atlas.query.GremlinTest
Running org.apache.atlas.query.LexerTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.793 sec - in 
org.apache.atlas.query.LexerTest
Running org.apache.atlas.query.BaseGremlinTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.255 sec - in 
org.apache.atlas.query.BaseGremlinTest
Running org.apache.atlas.query.ParserTest
Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.852 sec - in 
org.apache.atlas.query.ParserTest
Running org.apache.atlas.RepositoryServiceLoadingTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.515 sec - in 
org.apache.atlas.RepositoryServiceLoadingTest
Running org.apache.atlas.lineage.EntityLineageServiceTest
Tests run: 23, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 27.017 sec - 
in org.apache.atlas.lineage.EntityLineageServiceTest
Running org.apache.atlas.TestUtils
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.263 sec - in 
org.apache.atlas.TestUtils
Running org.apache.atlas.discovery.DataSetLineageServiceTest
Tests run: 60, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 56.156 sec - 
in org.apache.atlas.discovery.DataSetLineageServiceTest
Running org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
Tests run: 319, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 168.198 sec - 
in org.apache.atlas.discovery.GraphBackedDiscoveryServiceTest
Running org.apache.atlas.BaseRepositoryTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.263 sec - in 
org.apache.atlas.BaseRepositoryTest

Results :

Failed tests: 
  
DefaultMetadataServiceTest.testSpecialCharacters:225->assertReferenceableEquals:245
 expected:<{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-1043832554883860",
"version":0,
"typeName":"hxtFqt64ii\"${}%",
"state":"ACTIVE"
  },
  "typeName":"hxtFqt64ii\"${}%",
  "values":{
"WnNtEbFEwp\"${}%":[
  "7ZH1NcbrIq\"${}%"
],
"0LwNIHOiN2\"${}%":{
  "KRrSq6zYuY\"${}%":"zpHzJwDwXM\"${}%"
},
"PawSj6UUel\"${}%":"MsuGJ34uFW\"${}%"
  },
  "traitNames":[

  ],
  "traits":{

  },
  "systemAttributes":{
"createdBy":null,
"modifiedBy":null,
"createdTime":null,
"modifiedTime":null
  }
}> but was:<{
  
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
  "id":{
"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
"id":"-1043832554883860",
"version":0,
"typeName":"hxtFqt64ii\"${}%",
"state":"ACTIVE"
  },
  "typeName":"hxtFqt64ii\"${}%",
  "values":{
"0LwNIHOiN2\"${}%":{
  "KRrSq6zYuY\"${}%":"zpHzJwDwXM\"${}%"
},
"WnNtEbFEwp\"${}%":[

Re: Review Request 55031: ATLAS-1415: fix potential NPE issues found by Coverity scan

2016-12-26 Thread Suma Shivaprasad


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


Ship it!




Ship It!

- Suma Shivaprasad


On Dec. 25, 2016, 8:15 a.m., Madhan Neethiraj wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/55031/
> ---
> 
> (Updated Dec. 25, 2016, 8:15 a.m.)
> 
> 
> Review request for atlas.
> 
> 
> Bugs: ATLAS-1415
> https://issues.apache.org/jira/browse/ATLAS-1415
> 
> 
> Repository: atlas
> 
> 
> Description
> ---
> 
> fix potential NPE issues found by Coverity scan
> 
> 
> Diffs
> -
> 
>   
> webapp/src/main/java/org/apache/atlas/web/adapters/AtlasStructFormatConverter.java
>  b469f95 
>   webapp/src/main/java/org/apache/atlas/web/rest/EntitiesREST.java b770143 
> 
> Diff: https://reviews.apache.org/r/55031/diff/
> 
> 
> Testing
> ---
> 
> Verified all unit and IT tests pass
> 
> 
> Thanks,
> 
> Madhan Neethiraj
> 
>

Hive Hook - what is missing ?

2016-12-26 Thread Russell Anderson



Hi dev list,

I have built the Atlas7rc2 - have working the Hive Import, the Dashboard,
and generally things appear to be working as expected.

However, I have followed the instruction below but cannot seem to get the
Hive Hook to detect table hive creations to be added to the metadata /
lineage.

Can anyone suggest how to debug what could be missing regardless of
following the instructions below ? Any and all help appreciated !!!

Regards,

Russ.

=

Hive Hook


Hive supports listeners on hive command execution using hive hooks. This is
used to add/update/remove entities in Atlas using the model defined in
org.apache.atlas.hive.model.HiveDataModelGenerator. The hook submits the
request to a thread pool executor to avoid blocking the command execution.
The thread submits the entities as message to the notification server and
atlas server reads these messages and registers the entities. Follow these
instructions in your hive set-up to add hive hook for Atlas:
  Set-up atlas hook in hive-site.xml of your hive configuration:

  hive.exec.post.hooks
  org.apache.atlas.hive.hook.HiveHook




  atlas.cluster.name
  primary



  Add 'export HIVE_AUX_JARS_PATH=/hook/hive' in
  hive-env.sh of your hive configuration
  Copy /atlas-application.properties to the hive conf
  directory.


The following properties in /atlas-application.properties
control the thread pool and notification details:
  atlas.hook.hive.synchronous - boolean, true to run the hook
  synchronously. default false. Recommended to be set to false to avoid
  delays in hive query completion.
  atlas.hook.hive.numRetries - number of retries for notification
  failure. default 3
  atlas.hook.hive.minThreads - core number of threads. default 5
  atlas.hook.hive.maxThreads - maximum number of threads. default 5
  atlas.hook.hive.keepAliveTime - keep alive time in msecs. default 10
  atlas.hook.hive.queueSize - queue size for the threadpool. default
  1

Re: Creating a new entity

2016-12-26 Thread Ayub Khan Pathan

Great! 

Regards
Ayub Khan

On 12/26/16, 6:29 PM, "Avi Levi"  wrote:

I got it working - thanks !

the reason for the timeout exception was the fact that the kafka
topics used but atlas were missing

thanks

On Mon, Dec 26, 2016 at 1:35 PM, Avi Levi  wrote:
> thanks! I'm over this step and encountered a new problem:
>
> I get a timeout exception against kafka:
> kafka.common.errors.TimeoutException: Failed to update metadata after
> 6 ms.",
>   "stackTrace": "org.apache.atlas.notification.NotificationException:
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException: Failed to update
> metadata after 6 ms
>
> On Mon, Dec 26, 2016 at 12:33 PM, Ayub Khan Pathan
>  wrote:
>> I have just changed the qualifiedname and name values. Please check.
>>  "qualifiedName": "default1@cluster1",
>>  "name": "default1"
>>
>> Thanks
>> Ayub Khan
>>
>> On 12/26/16, 3:51 PM, "Avi Levi"  wrote:
>>
>> Thanks a lot
>>
>> I can't see the difference between the json I've send and the one you
>> have, can you be more specific?
>> also, I try changing the id and keep getting the same response.
>>
>> thanks again
>>
>> On Sun, Dec 25, 2016 at 6:13 PM, Ayub Khan Pathan
>>  wrote:
>> > Hi,
>> >
>> >
>> >
>> > Seems like you are trying to create an existing entity, so Atlas is
>> > returning with no guid, which is expected.
>> >
>> >
>> >
>> > Below is the valid request/response json content for a successful 
creation
>> > of the entity.
>> >
>> > JSON request body sent to ATLAS:
>> >
>> > [{
>> >
>> >   "jsonClass":
>> > 
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>> >
>> >   "id": {
>> >
>> > "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>> >
>> > "id": "-1466683608564093000",
>> >
>> > "version": 0,
>> >
>> > "typeName": "DataSet",
>> >
>> > "state": "ACTIVE"
>> >
>> >   },
>> >
>> >   "typeName": "DataSet",
>> >
>> >   "values": {
>> >
>> > "qualifiedName": "default1@cluster1",
>> >
>> > "name": "default1"
>> >
>> >   },
>> >
>> >   "traitNames": [],
>> >
>> >   "traits": {}
>> >
>> > }]
>> >
>> >
>> >
>> > JSON response from ATLAS:
>> >
>> > {
>> >
>> >   "requestId": "qtp1823101219-1336 - 
70a0a4fb-3677-479a-bb76-ea74b20b8fd7",
>> >
>> >   "entities": {
>> >
>> > "created": [
>> >
>> >   "fa35cf46-7f3a-4f51-b66a-31257991c5c5"
>> >
>> > ]
>> >
>> >   },
>> >
>> >   "definition": {
>> >
>> > "jsonClass":
>> > 
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>> >
>> > "id": {
>> >
>> >   "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>> >
>> >   "id": "fa35cf46-7f3a-4f51-b66a-31257991c5c5",
>> >
>> >   "version": 0,
>> >
>> >   "typeName": "DataSet",
>> >
>> >   "state": "ACTIVE"
>> >
>> > },
>> >
>> > "typeName": "DataSet",
>> >
>> > "values": {
>> >
>> >   "qualifiedName": "default1@cluster1",
>> >
>> >   "owner": null,
>> >
>> >   "description": null,
>> >
>> >   "name": "default1"
>> >
>> > },
>> >
>> > "traitNames": [],
>> >
>> > "traits": {}
>> >
>> >   }
>> >
>> > }
>> >
>> >
>> >
>> > Hope this unblocks you.
>> >
>> >
>> >
>> > Thanks
>> >
>> > Ayub Khan
>> >
>> >
>> >
>> > On 12/25/16, 9:32 PM, "Avi Levi"  wrote:
>> >
>> >
>> >
>> > Hi
>> >
>> >
>> >
>> > I'm trying to create an entity, using the url:
>> >
>> > admin:ad...@sandbox.hortonworks.com:21000/api/atlas/entities
>> >
>> >
>> >
>> > and the following body:
>> >
>> > [{
>> >
>> >   "jsonClass":
>> > 
"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>>

Re: Creating a new entity

2016-12-26 Thread Avi Levi

I got it working - thanks !

the reason for the timeout exception was the fact that the kafka
topics used but atlas were missing

thanks

On Mon, Dec 26, 2016 at 1:35 PM, Avi Levi  wrote:
> thanks! I'm over this step and encountered a new problem:
>
> I get a timeout exception against kafka:
> kafka.common.errors.TimeoutException: Failed to update metadata after
> 6 ms.",
>   "stackTrace": "org.apache.atlas.notification.NotificationException:
> java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TimeoutException: Failed to update
> metadata after 6 ms
>
> On Mon, Dec 26, 2016 at 12:33 PM, Ayub Khan Pathan
>  wrote:
>> I have just changed the qualifiedname and name values. Please check.
>>  "qualifiedName": "default1@cluster1",
>>  "name": "default1"
>>
>> Thanks
>> Ayub Khan
>>
>> On 12/26/16, 3:51 PM, "Avi Levi"  wrote:
>>
>> Thanks a lot
>>
>> I can't see the difference between the json I've send and the one you
>> have, can you be more specific?
>> also, I try changing the id and keep getting the same response.
>>
>> thanks again
>>
>> On Sun, Dec 25, 2016 at 6:13 PM, Ayub Khan Pathan
>>  wrote:
>> > Hi,
>> >
>> >
>> >
>> > Seems like you are trying to create an existing entity, so Atlas is
>> > returning with no guid, which is expected.
>> >
>> >
>> >
>> > Below is the valid request/response json content for a successful 
>> creation
>> > of the entity.
>> >
>> > JSON request body sent to ATLAS:
>> >
>> > [{
>> >
>> >   "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>> >
>> >   "id": {
>> >
>> > "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>> >
>> > "id": "-1466683608564093000",
>> >
>> > "version": 0,
>> >
>> > "typeName": "DataSet",
>> >
>> > "state": "ACTIVE"
>> >
>> >   },
>> >
>> >   "typeName": "DataSet",
>> >
>> >   "values": {
>> >
>> > "qualifiedName": "default1@cluster1",
>> >
>> > "name": "default1"
>> >
>> >   },
>> >
>> >   "traitNames": [],
>> >
>> >   "traits": {}
>> >
>> > }]
>> >
>> >
>> >
>> > JSON response from ATLAS:
>> >
>> > {
>> >
>> >   "requestId": "qtp1823101219-1336 - 
>> 70a0a4fb-3677-479a-bb76-ea74b20b8fd7",
>> >
>> >   "entities": {
>> >
>> > "created": [
>> >
>> >   "fa35cf46-7f3a-4f51-b66a-31257991c5c5"
>> >
>> > ]
>> >
>> >   },
>> >
>> >   "definition": {
>> >
>> > "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>> >
>> > "id": {
>> >
>> >   "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>> >
>> >   "id": "fa35cf46-7f3a-4f51-b66a-31257991c5c5",
>> >
>> >   "version": 0,
>> >
>> >   "typeName": "DataSet",
>> >
>> >   "state": "ACTIVE"
>> >
>> > },
>> >
>> > "typeName": "DataSet",
>> >
>> > "values": {
>> >
>> >   "qualifiedName": "default1@cluster1",
>> >
>> >   "owner": null,
>> >
>> >   "description": null,
>> >
>> >   "name": "default1"
>> >
>> > },
>> >
>> > "traitNames": [],
>> >
>> > "traits": {}
>> >
>> >   }
>> >
>> > }
>> >
>> >
>> >
>> > Hope this unblocks you.
>> >
>> >
>> >
>> > Thanks
>> >
>> > Ayub Khan
>> >
>> >
>> >
>> > On 12/25/16, 9:32 PM, "Avi Levi"  wrote:
>> >
>> >
>> >
>> > Hi
>> >
>> >
>> >
>> > I'm trying to create an entity, using the url:
>> >
>> > admin:ad...@sandbox.hortonworks.com:21000/api/atlas/entities
>> >
>> >
>> >
>> > and the following body:
>> >
>> > [{
>> >
>> >   "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>> >
>> >   "id": {
>> >
>> > "jsonClass":
>> > "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>> >
>> > "id": "-1466683608564093000",
>> >
>> > "version": 0,
>> >
>> > "typeName": "DataSet",
>> >
>> > "state": "ACTIVE"
>> >
>> >   },
>> >
>> >   "typeName": "DataSet",
>> >
>> >   "values": {
>> >
>> > "qualifiedName": "default@cluster1",
>> >
>> > "name": "default"
>> >
>> >   },
>> >
>> >   "traitNames": [],
>> >
>> >   "traits": {}
>> >
>> > }]
>> >
>> >
>> >
>> >
>> >
>> > I get what seems to be a valid response, but without entity ids:

Re: Creating a new entity

2016-12-26 Thread Ayub Khan Pathan

I have just changed the qualifiedname and name values. Please check.
 "qualifiedName": "default1@cluster1",
 "name": "default1"

Thanks
Ayub Khan

On 12/26/16, 3:51 PM, "Avi Levi"  wrote:

Thanks a lot

I can't see the difference between the json I've send and the one you
have, can you be more specific?
also, I try changing the id and keep getting the same response.

thanks again

On Sun, Dec 25, 2016 at 6:13 PM, Ayub Khan Pathan
 wrote:
> Hi,
>
>
>
> Seems like you are trying to create an existing entity, so Atlas is
> returning with no guid, which is expected.
>
>
>
> Below is the valid request/response json content for a successful creation
> of the entity.
>
> JSON request body sent to ATLAS:
>
> [{
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
>   "id": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
> "id": "-1466683608564093000",
>
> "version": 0,
>
> "typeName": "DataSet",
>
> "state": "ACTIVE"
>
>   },
>
>   "typeName": "DataSet",
>
>   "values": {
>
> "qualifiedName": "default1@cluster1",
>
> "name": "default1"
>
>   },
>
>   "traitNames": [],
>
>   "traits": {}
>
> }]
>
>
>
> JSON response from ATLAS:
>
> {
>
>   "requestId": "qtp1823101219-1336 - 
70a0a4fb-3677-479a-bb76-ea74b20b8fd7",
>
>   "entities": {
>
> "created": [
>
>   "fa35cf46-7f3a-4f51-b66a-31257991c5c5"
>
> ]
>
>   },
>
>   "definition": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
> "id": {
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
>   "id": "fa35cf46-7f3a-4f51-b66a-31257991c5c5",
>
>   "version": 0,
>
>   "typeName": "DataSet",
>
>   "state": "ACTIVE"
>
> },
>
> "typeName": "DataSet",
>
> "values": {
>
>   "qualifiedName": "default1@cluster1",
>
>   "owner": null,
>
>   "description": null,
>
>   "name": "default1"
>
> },
>
> "traitNames": [],
>
> "traits": {}
>
>   }
>
> }
>
>
>
> Hope this unblocks you.
>
>
>
> Thanks
>
> Ayub Khan
>
>
>
> On 12/25/16, 9:32 PM, "Avi Levi"  wrote:
>
>
>
> Hi
>
>
>
> I'm trying to create an entity, using the url:
>
> admin:ad...@sandbox.hortonworks.com:21000/api/atlas/entities
>
>
>
> and the following body:
>
> [{
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
>   "id": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
> "id": "-1466683608564093000",
>
> "version": 0,
>
> "typeName": "DataSet",
>
> "state": "ACTIVE"
>
>   },
>
>   "typeName": "DataSet",
>
>   "values": {
>
> "qualifiedName": "default@cluster1",
>
> "name": "default"
>
>   },
>
>   "traitNames": [],
>
>   "traits": {}
>
> }]
>
>
>
>
>
> I get what seems to be a valid response, but without entity ids:
>
>
>
> {
>
>   "requestId": "qtp1613255205-87 -
> 268121f0-fb70-43af-9898-7f05ac0c267d",
>
>   "entities": {}
>
> }
>
>
>
> Atlas's logs writes the following corresponding statements:
>
>
>
> 2016-12-25 12:12:55,860 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ submitting entities
>
>
> 
{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"-1466683608564093000","version":0,"typeName":"DataSet","state":"ACTIVE"},"typeName":"DataSet","values":{"qualifiedName":"default@cluster1","description":"Default
>
> dataset","name":"default"},"traitNames":[],"traits":{}}
>
> (EntityResource:131)
>
>
>
> 2016-12-25 12:12:55,865 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ graph commit
>
> (GraphTransactionInterceptor:46)
>
>
>
> 2016-12-25 12:12:55,866 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ Putting 0 events
>

Re: Creating a new entity

2016-12-26 Thread Avi Levi

Thanks a lot

I can't see the difference between the json I've send and the one you
have, can you be more specific?
also, I try changing the id and keep getting the same response.

thanks again

On Sun, Dec 25, 2016 at 6:13 PM, Ayub Khan Pathan
 wrote:
> Hi,
>
>
>
> Seems like you are trying to create an existing entity, so Atlas is
> returning with no guid, which is expected.
>
>
>
> Below is the valid request/response json content for a successful creation
> of the entity.
>
> JSON request body sent to ATLAS:
>
> [{
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
>   "id": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
> "id": "-1466683608564093000",
>
> "version": 0,
>
> "typeName": "DataSet",
>
> "state": "ACTIVE"
>
>   },
>
>   "typeName": "DataSet",
>
>   "values": {
>
> "qualifiedName": "default1@cluster1",
>
> "name": "default1"
>
>   },
>
>   "traitNames": [],
>
>   "traits": {}
>
> }]
>
>
>
> JSON response from ATLAS:
>
> {
>
>   "requestId": "qtp1823101219-1336 - 70a0a4fb-3677-479a-bb76-ea74b20b8fd7",
>
>   "entities": {
>
> "created": [
>
>   "fa35cf46-7f3a-4f51-b66a-31257991c5c5"
>
> ]
>
>   },
>
>   "definition": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
> "id": {
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
>   "id": "fa35cf46-7f3a-4f51-b66a-31257991c5c5",
>
>   "version": 0,
>
>   "typeName": "DataSet",
>
>   "state": "ACTIVE"
>
> },
>
> "typeName": "DataSet",
>
> "values": {
>
>   "qualifiedName": "default1@cluster1",
>
>   "owner": null,
>
>   "description": null,
>
>   "name": "default1"
>
> },
>
> "traitNames": [],
>
> "traits": {}
>
>   }
>
> }
>
>
>
> Hope this unblocks you.
>
>
>
> Thanks
>
> Ayub Khan
>
>
>
> On 12/25/16, 9:32 PM, "Avi Levi"  wrote:
>
>
>
> Hi
>
>
>
> I'm trying to create an entity, using the url:
>
> admin:ad...@sandbox.hortonworks.com:21000/api/atlas/entities
>
>
>
> and the following body:
>
> [{
>
>   "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Reference",
>
>   "id": {
>
> "jsonClass":
> "org.apache.atlas.typesystem.json.InstanceSerialization$_Id",
>
> "id": "-1466683608564093000",
>
> "version": 0,
>
> "typeName": "DataSet",
>
> "state": "ACTIVE"
>
>   },
>
>   "typeName": "DataSet",
>
>   "values": {
>
> "qualifiedName": "default@cluster1",
>
> "name": "default"
>
>   },
>
>   "traitNames": [],
>
>   "traits": {}
>
> }]
>
>
>
>
>
> I get what seems to be a valid response, but without entity ids:
>
>
>
> {
>
>   "requestId": "qtp1613255205-87 -
> 268121f0-fb70-43af-9898-7f05ac0c267d",
>
>   "entities": {}
>
> }
>
>
>
> Atlas's logs writes the following corresponding statements:
>
>
>
> 2016-12-25 12:12:55,860 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ submitting entities
>
>
> {"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Reference","id":{"jsonClass":"org.apache.atlas.typesystem.json.InstanceSerialization$_Id","id":"-1466683608564093000","version":0,"typeName":"DataSet","state":"ACTIVE"},"typeName":"DataSet","values":{"qualifiedName":"default@cluster1","description":"Default
>
> dataset","name":"default"},"traitNames":[],"traits":{}}
>
> (EntityResource:131)
>
>
>
> 2016-12-25 12:12:55,865 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ graph commit
>
> (GraphTransactionInterceptor:46)
>
>
>
> 2016-12-25 12:12:55,866 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ Putting 0 events
>
> (HBaseBasedAuditRepository:117)
>
>
>
> 2016-12-25 12:12:55,866 INFO  - [qtp1613255205-87 -
>
> 268121f0-fb70-43af-9898-7f05ac0c267d:] ~ Created entities []
>
> (EntityResource:134)
>
>
>
> as you can see, no errors or any clue as to whats wrong.
>
>
>
> can someone point me in the right direction?
>
> thanks a lot
>
> Avi
>
>
>
>

[jira] [Created] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

2016-12-26 Thread Hemanth Yamijala (JIRA)

Hemanth Yamijala created ATLAS-1416:
---

 Summary: UI: It would be nice to sort the properties in the 
details page of an entity by name
 Key: ATLAS-1416
 URL: https://issues.apache.org/jira/browse/ATLAS-1416
 Project: Atlas
  Issue Type: Improvement
Reporter: Hemanth Yamijala


The Atlas UI has a Details page for every entity. In the "Properties" tab of 
this pane, it currently enumerates all properties of the entity. Currently the 
order seems random and hence is not very easy to grok. It would be nice to have 
these sorted by property name to make location of required details easier.



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

Re: Hive Hook - what is missing ?

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

Re: Review Request 55031: ATLAS-1415: fix potential NPE issues found by Coverity scan

Hive Hook - what is missing ?

Re: Creating a new entity

Re: Creating a new entity

Re: Creating a new entity

Re: Creating a new entity

[jira] [Created] (ATLAS-1416) UI: It would be nice to sort the properties in the details page of an entity by name

9 matches

Site Navigation

Mail list logo

Footer information