Connie,
Perhaps a collection was sent, instead of a single object-id – looking at ‘[‘
and ‘]’ in the following message?
org.apache.atlas.exception.AtlasBaseException: ObjectId is not valid
[{guid=68fb7501-63be-44c5-9e96-823314ee614a, typeName=schema}]
Can you please check?
Thanks,
Madhan
From: <[email protected]> on behalf of Connie Chen <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Tuesday, June 19, 2018 at 3:47 PM
To: "[email protected]" <[email protected]>
Subject: Re: After updating to 1.0.0 AtlasObjectId's no longer work
Here is the stacktrace, I don't see why it can't detect this as an
`AtlasObjectId`
2018-06-19 22:43:40,509 ERROR - [pool-1-thread-4 -
9b1b9c88-a432-47e0-b02d-3b4086cb8986:] ~ graph rollback due to exception
(GraphTransactionInterceptor:154)
org.apache.atlas.exception.AtlasBaseException: ObjectId is not valid
[{guid=68fb7501-63be-44c5-9e96-823314ee614a, typeName=schema}]
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.visitReference(AtlasEntityGraphDiscoveryV2.java:199)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.visitAttribute(AtlasEntityGraphDiscoveryV2.java:234)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.visitEntity(AtlasEntityGraphDiscoveryV2.java:317)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.walkEntityGraph(AtlasEntityGraphDiscoveryV2.java:358)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.discover(AtlasEntityGraphDiscoveryV2.java:142)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityGraphDiscoveryV2.discoverEntities(AtlasEntityGraphDiscoveryV2.java:69)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.preCreateOrUpdate(AtlasEntityStoreV2.java:643)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:579)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2.createOrUpdate(AtlasEntityStoreV2.java:166)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$FastClassBySpringCGLIB$$6861dca9.invoke(<generated>)
at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
at
org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:736)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
at
org.apache.atlas.GraphTransactionInterceptor.invoke(GraphTransactionInterceptor.java:75)
at
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
at
org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:671)
at
org.apache.atlas.repository.store.graph.v2.AtlasEntityStoreV2$$EnhancerBySpringCGLIB$$5ff9641e.createOrUpdate(<generated>)
at org.apache.atlas.web.rest.EntityREST.createOrUpdate(EntityREST.java:272)
at sun.reflect.GeneratedMethodAccessor84.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
com.sun.jersey.spi.container.JavaMethodInvokerFactory$1.invoke(JavaMethodInvokerFactory.java:60)
at
com.sun.jersey.server.impl.model.method.dispatch.AbstractResourceMethodDispatchProvider$TypeOutInvoker._dispatch(AbstractResourceMethodDispatchProvider.java:185)
On Tue, Jun 19, 2018 at 3:18 PM, Connie Chen <[email protected]> wrote:
Hi, after we upgraded from 0.8.1 to 1.0.0, using `AtlasObjectId` in the
`AtlasClientV2` no longer works, it gives this error
{\"errorCode\":\"ATLAS-400-00-021\",\"errorMessage\":\"ObjectId is not valid
[{guid=68fb7501-63be-44c5-9e96-823314ee614a, typeName=schema}]\"}) class
java.lang.IllegalArgumentException"}
Here is a debug line from Atlas
21848 DEBUG org.apache.atlas.AtlasBaseClient - Request :
AtlasEntityWithExtInfo{entity=AtlasEntity{AtlasStruct{typeName='s3',
attributes=[schema:[AtlasObjectId{guid='68fb7501-63be-44c5-9e96-823314ee614a',
typeName='schema', uniqueAttributes={}}], awsRegion:us-east-1 ....}
You can see that I am sending AtlasObjectId as before. I don't understand why
this is suddenly happening, I looked at the examples in QuickStartV2 and for
references it is still constructing `AtlasObjectId` in the same way with the
guid and typeName, so why are my AtlasObjectId's now invalid?
Connie
