Hello Madhan, Thank you for your response and attention,
Since you already gave me a way to access entities through uniqueAttributes my problems are already solved and I do not see now a usecase for which I would like to handle the GUID myself. Thank you very much for your good work and this wonderful tool. Best regards, Joan 2018-01-11 2:39 GMT+01:00 Madhan Neethiraj <[email protected]>: > Joan, > > > > >> Is it expected to be available in notification processing or REST APIS > in any near-future releases? > > Can you please file a JIRA with details of the usecases for this > enhancement? It will help prioritize and track the progress. > > > > >> Is there anyway to construct Process entities that refer its inputs and > outputs through some identification that is controlled from the outside, > (it means other than the guid?? the qualifiedName for instance?) > > Yes. Atlas can pick an existing entity based on unique-attribute value > provided for inputs/outputs entities. However, you would have to provide > value for all ‘required-attributes’ though. If this doesn’t address your > needs, please file a JIRA with details of the usecases. > > > > Thanks, > > Madhan > > > > > > *From: *Jo MailingList <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Wednesday, December 27, 2017 at 12:31 AM > *To: *"[email protected]" <[email protected]> > *Subject: *Re: Unassigned GUID > > > > Hello, > > > > Thank you very much for your quick reply. > > > > I have a couple of questions > > > > Is it expected to be available in notification processing or REST APIS in > any near-future releases? > > > > Is there anyway to construct Process entities that refer its inputs and > outputs through some identification that is controlled from the outside, > (it means other than the guid?? the qualifiedName for instance?) > > > > Thank you very much, > > > > Best regards, > > > > Joan > > > > 2017-12-23 1:53 GMT+01:00 Madhan Neethiraj <[email protected]>: > > Joan, > > > > >> I have found that GUID looks like could be assigned from the outside as > a valid UUID, instead of leting Atlas assign one for you > > Atlas recognizes externally provided GUIDs only when performing ‘import’. > In all other scenarios of entity creation (like notification processing, > REST APIs), Atlas doesn’t accept externally given GUIDs. > > > > Regards, > > Madhan > > > > > > *From: *Jo MailingList <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Friday, December 22, 2017 at 6:03 AM > *To: *"[email protected]" <[email protected]> > *Subject: *Fwd: Unassigned GUID > > > > > > Sorry I did by mistake send a partial incomplete mail. > > Hello, > > > > I have been digging a little bit in the code and I have found that GUID > looks like could be assigned from the outside as a valid UUID, instead of > leting Atlas assign one for you by inserting a big negative number in the > "id" field. > > > > But I have tried to create objects with an id provided by me in the id and > I get the following exception. > > > > 2017-12-22 14:55:13,930 WARN - [NotificationHookConsumer thread-0:] ~ > Error handling message (NotificationHookConsumer$HookConsumer:443) > > org.apache.atlas.exception.AtlasBaseException: Referenced entity > aa1da4e0-a2a1-45f3-97b6-77afd9cdf33c is not found > > at org.apache.atlas.repository.store.graph.v1. > IDBasedEntityResolver.resolveEntityReferences( > IDBasedEntityResolver.java:74) > > at org.apache.atlas.repository.store.graph.v1. > AtlasEntityGraphDiscoveryV1.resolveReferences(AtlasEntityGraphDiscoveryV1. > java:173) > > at org.apache.atlas.repository.store.graph.v1. > AtlasEntityGraphDiscoveryV1.discoverEntities(AtlasEntityGraphDiscoveryV1. > java:72) > > at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1. > preCreateOrUpdate(AtlasEntityStoreV1.java:523) > > at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1. > createOrUpdate(AtlasEntityStoreV1.java:174) > > at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1. > createOrUpdate(AtlasEntityStoreV1.java:193) > > at org.apache.atlas.repository.store.graph.v1.AtlasEntityStoreV1$$ > FastClassBySpringCGLIB$$80c00649.invoke(<generated>) > > at org.springframework.cglib.proxy.MethodProxy.invoke( > MethodProxy.java:204). > > > > It would be useful for me to be able to deal myself with the guid so that > I can save calls to the REST API to consult guid to get the guid to create > lineage objects. > > > > Do you know what I am doing wrong? Is it not supported this feature yet? > > > > Thank you very much, > > > Best regards, > > > > Joan > > > > > > > > >
