New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/oss/update to v2 endpoints #4128
Feature/oss/update to v2 endpoints #4128
Conversation
…to feature/OSS/updateToV2Endpoints
Constants.ASPECT_LATEST_VERSION, | ||
context.getAuthentication()); | ||
return keyAspect != null; | ||
Urn userUrn = Urn.createFromString(userUrnStr); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So I think previously if there was no key aspect, this would getAspectOrNull would return null... But I believe that batchGetV2 artificially injects a key aspect into the result set to maintain our previous behavior. In this particular case it won't be a huge deal but it might be in other cases... Gabe added an "exists" API in GMS that we should migrate this to instead...
Don't may not need to address in this PR, but definitely want to call it out
_datasetHydrator.hydrateFromEntityResponse(document, entityResponse); | ||
break; | ||
default: | ||
log.error("Unable to find valid hydrator for entity type: {} urn: {}", entityResponse.getEntityName(), urn); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Amazing PR, thank you @RyanHolstien !
Updates all internal usages of old Snapshot endpoints to V2 endpoints for Java classes