ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-497841938
@mneethiraj - any way the ATLAS-3180 pull request does exactly what you say.
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-497838976
I agree absolutely. I don't want to create a complex Rest system to access
however the customer wants. I only think that access by service
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-497831869
@mneethiraj-Regarding the DELETE you are proposing the fact of not
implementing it for the serviceType because moving the work on the client
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-497831594
@mneethiraj - I didn't understand if you propose to add new REST APIs by
type
/enumdef /servicetype/hive for example) but use the /typedefs
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-497301805
@mneethiraj - I looked more closely at the code and we could: 1) limit the
rest api for the four types one for the post, one for the put, one
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496750150
In my opinion you are right because I can't understand why we a cache for
the name, a cache for the guid and now also a cache for the
ZepHakase22 commented on issue #54: ATLAS-3219: New REST APIs for serviceType.
URL: https://github.com/apache/atlas/pull/54#issuecomment-496748406
It was exactly what I did but it works only for
> GET / typedefs? serviceype = {servicetype}
how you can see here in the code.
