fix(ui): fix useGetUserGroupUrns when user urn is empty

[Masterchen09]

This PR fixes an issue with useGetUserGroupUrns when the user urn is empty (or undefined), this can happen when the user context (useUserContext.ts) is used for getting the user urn e.g. in AssetsYouOwn.tsx.

A query with an empty user urn causes an exception in the GMS:

2025-04-29 12:19:25,568 [ForkJoinPool.commonPool-worker-5] ERROR c.l.datahub.graphql.GmsGraphQLEngine:3140 - Failed to load Entities of type: CorpUser, keys: [] Failed to batch load Datasets
2025-04-29 12:19:25,570 [ForkJoinPool.commonPool-worker-2] ERROR c.l.d.g.e.DataHubDataFetcherExceptionHandler:45 - Failed to execute
java.lang.RuntimeException: Failed to retrieve entities of type CorpUser
at com.linkedin.datahub.graphql.GmsGraphQLEngine.lambda$createDataLoader$274(GmsGraphQLEngine.java:3147)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1768)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.exec(CompletableFuture.java:1760)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:373)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1182)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1655)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1622)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:165)
Caused by: java.lang.RuntimeException: Failed to batch load Datasets
at com.linkedin.datahub.graphql.types.corpuser.CorpUserType.batchLoad(CorpUserType.java:108)
at com.linkedin.datahub.graphql.GmsGraphQLEngine.lambda$createDataLoader$274(GmsGraphQLEngine.java:3138)
... 7 common frames omitted
Caused by: java.lang.RuntimeException: Failed to retrieve entity with urn , invalid urn
at com.linkedin.common.urn.UrnUtils.getUrn(UrnUtils.java:35)
at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197)
at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1625)
at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509)
at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499)
at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:921)
at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:682)
at com.linkedin.datahub.graphql.types.corpuser.CorpUserType.batchLoad(CorpUserType.java:85)
... 8 common frames omitted
2025-04-29 12:19:25,571 [ForkJoinPool.commonPool-worker-2] ERROR c.datahub.graphql.GraphQLController:153 - Errors while executing query: query getUserGroupsUrns($urn: String!, $start: Int!, $count: Int!) {
corpUser(urn: $urn) {
relationships(
input: {types: ["IsMemberOfGroup", "IsMemberOfNativeGroup"], direction: OUTGOING, start: $start, count: $count}
) {
start
count
total
relationships {
entity {
urn
type
__typename
}
__typename
}
__typename
}
__typename
}
}
, result: {errors=[{message=An unknown error occurred., locations=[{line=2, column=3}], path=[corpUser], extensions={code=500, type=SERVER_ERROR, classification=DataFetchingException}}], data={corpUser=null}, extensions={tracing={version=1, startTime=2025-04-29T12:19:25.566567870Z, endTime=2025-04-29T12:19:25.571188411Z, duration=4629035, parsing={startOffset=548860, duration=418741}, validation={startOffset=976695, duration=391058}, execution={resolvers=[{path=[corpUser], parentType=Query, returnType=CorpUser, fieldName=corpUser, startOffset=1744620, duration=2193243}]}}}}, errors: [DataHubGraphQLError{path=[corpUser], code=SERVER_ERROR, locations=[SourceLocation{line=2, column=3}]}]
2025-04-29 12:19:25,571 [ForkJoinPool.commonPool-worker-2] INFO c.datahub.graphql.GraphQLController:166 - Executed operation getUserGroupsUrns in 4 ms

I have solved it by also accepting undefined user urns, but skipping the query when this is the case.

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[esteban]

Hello @Masterchen09. Thanks for submitting your PR!