[ 
https://issues.apache.org/jira/browse/YUNIKORN-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Bacsko updated YUNIKORN-1939:
-----------------------------------
    Description: 
Based on an internal discussion, we need to add an extra convenience features 
to the REST interface.

We'd like to retrieve the recent "n" events: the implementation of this is not 
difficult. We calculate the startID based on how many events we want. Right now 
this cannot be done reliably because right after we determined the startID, new 
events can arrive, so the last "n" is no longer the last "n".

  was:
Based on an internal discussion, we need to add extra convenience features to 
the REST interface.

1. Filtering: one might be interested in application-only events.  We don't 
know when the first event belonging to an app was submitted and if the job runs 
for hours or days, it's difficult to efficiently retrieve only those which we 
want. We can rely on the ID but the client has to store it. It's way better if 
we can specify the event type and possibly more details like appID or queue 
name (ObjectID).

2. Recent "n" events, the implementation of this is not difficult. We calculate 
the startID based on how many events we want. Right now this cannot be done 
reliably because right after we determined the startID, new events can arrive, 
so the last "n" is no longer the last "n".


> Add retrieving recent events to the REST interface
> --------------------------------------------------
>
>                 Key: YUNIKORN-1939
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-1939
>             Project: Apache YuniKorn
>          Issue Type: Sub-task
>          Components: core - scheduler
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>
> Based on an internal discussion, we need to add an extra convenience features 
> to the REST interface.
> We'd like to retrieve the recent "n" events: the implementation of this is 
> not difficult. We calculate the startID based on how many events we want. 
> Right now this cannot be done reliably because right after we determined the 
> startID, new events can arrive, so the last "n" is no longer the last "n".



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to