[
https://issues.apache.org/jira/browse/YARN-3422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525410#comment-14525410
]
Billie Rinaldi commented on YARN-3422:
--------------------------------------
Let’s say we post entity A with related entity B and primary filter C. This
implies a directional relationship B -> A. The entries stored include the
following:
{noformat}
entity entry: A (with hidden B)
related entity entry: B A
primary filter entry: C A (no B)
{noformat}
The patch submitted adds primary filter entry C B A, which is not correct for
the existing design because C was posted as a primary filter for A, not for B.
What we might want (that the store does not currently do) is for A to be added
under primary filter entries for B (i.e. D B A, where D is a primary filter for
B). One problem with doing this is that we do not know the primary filters for
B when we are posting entity A, and a further problem is that the primary
filters for B could change over time and have to be kept up to date.
> relatedentities always return empty list when primary filter is set
> -------------------------------------------------------------------
>
> Key: YARN-3422
> URL: https://issues.apache.org/jira/browse/YARN-3422
> Project: Hadoop YARN
> Issue Type: Bug
> Components: timelineserver
> Reporter: Chang Li
> Assignee: Chang Li
> Attachments: YARN-3422.1.patch
>
>
> When you curl for ats entities with a primary filter, the relatedentities
> fields always return empty list
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
