[
https://issues.apache.org/jira/browse/YARN-6027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15859344#comment-15859344
]
Varun Saxena commented on YARN-6027:
------------------------------------
Ok...I had forgotton that we currently do not limit flow runs which means that
in collapse mode, if daterange is not specified, we will have to do a full
table scan anyways. I have a JIRA for limiting flowruns. I will discuss with
some HBase guy and check the scenario with him and handle it in that JIRA, if
required. Basically its a choice between a full table scan of say 100000 rows
vs multiple scans with PageFilter equal to limit in each scan(or 2-3 times the
limit value) and breaking out from the loop as soon as flow run limit is also
reached. By default we can return 0 flow runs for flows endpoint as we already
have a flowruns endpoint as well.
Anyways I am not a 100% sure on this and need to check with a HBase guy. We can
get back to this on the JIRA which is with me.
> Improve /flows API for more flexible filters fromid, collapse, userid
> ---------------------------------------------------------------------
>
> Key: YARN-6027
> URL: https://issues.apache.org/jira/browse/YARN-6027
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Reporter: Rohith Sharma K S
> Assignee: Rohith Sharma K S
> Labels: yarn-5355-merge-blocker
> Attachments: YARN-6027-YARN-5355.0001.patch
>
>
> In YARN-5585 , fromId is supported for retrieving entities. We need similar
> filter for flows/flowRun apps and flow run and flow as well.
> Along with supporting fromId, this JIRA should also discuss following points
> * Should we throw an exception for entities/entity retrieval if duplicates
> found?
> * TimelieEntity :
> ** Should equals method also check for idPrefix?
> ** Does idPrefix is part of identifiers?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
