[FALCON-166] Instance status start and end dates are rigid and inconvenient

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3
• Fix Version/s: 0.6
• Component/s: webapp
• Assignee: Balu Vellanki
• Reporter: Venkatesh Seetharam
• Created: 04/Nov/13 23:10
• Updated: 12/Sep/14 15:05
• Resolved: 28/Aug/14 00:16

Description

There are 2 annoying issues that was brought up by srimanth.gunturi while working on FALCON-164. The use case is to get the status for a given entity for the past 1 or 2 or 3 or 7 days.

1. Instance status with out an end date fetches for a very small window
Instance status take end date as optional but assumes one second from the start date which is too small a window.

    private Date getEndDate(Date start, String endStr) throws FalconException {
        Date end;
        if (StringUtils.isEmpty(endStr)) {
            end = new Date(start.getTime() + 1000); // next sec
        } else {
            end = EntityUtil.parseDateUTC(endStr);
        }
        return end;
    }

May be assuming the current time might be appropriate instead.

2. The start date has to be on or after the start of the entity.
If the user has created the entity 2 days back but specified the start date for looking at the instances in the past 7 days, it should fetch what is valid rather than complain that the start date is before the entity's start.

This is quite unwieldy to work with in a dashboard use case. I'm not sure what the performance impact is for this API to be changed.

Thoughts?

Issue Links

• blocks: FALCON-469 Enhance REST API to drive interactive user dashboard
• is related to: FALCON-715 "end" parameter should be greater than last instance's startTime