[
https://issues.apache.org/jira/browse/YARN-925?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13800890#comment-13800890
]
Mayank Bansal commented on YARN-925:
------------------------------------
[~zjshen] if you look at the filters more closely you will see we have offset
and limit in the filters which will actually gives you iterative functionality
, however client has to call them with the right offset.
The two methods one with the filters and other without filters , as you said
the filters one can be downgraded to without filter one but thats I think
implementation details, however from user prospective, user should be able to
get all the apps without specifying filters if he knows whats he is looking for
and his data size is less.
The second api is like convinient api for the user wheer user doesn't want to
get educated for all the filters. Its like you are running select * from table
without specifying the where clause if you don't need to. Otherwise all the
users need to understand all the filters and how they work.
I agree with you that we should finalize the filter we want to provide.
>From cache prospective I will keep the metadata for the apps but yeah I want o
>keep that discussion in the corresponding JIRA, probably I will update the
>little writeup for that in the JIRA.
The main part for all this is how we are going to store the files in the store
as that will actually reduce lot of load on the store reading.
We need to do somthing like what we do for JHS , keep meta data on the file
name by that you can filter the files directly before reading instead of
reading everything and then filter one by one.
> HistoryStorage Reader Interface for Application History Server
> --------------------------------------------------------------
>
> Key: YARN-925
> URL: https://issues.apache.org/jira/browse/YARN-925
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Mayank Bansal
> Assignee: Mayank Bansal
> Fix For: YARN-321
>
> Attachments: YARN-925-1.patch, YARN-925-2.patch, YARN-925-3.patch,
> YARN-925-4.patch, YARN-925-5.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
