[
https://issues.apache.org/jira/browse/FALCON-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131999#comment-14131999
]
Balu Vellanki commented on FALCON-718:
--------------------------------------
This is expected behavior. It should not matter if the START date given is
older than the entity/cluster validity time.
When user makes GET instance api calls and provides a START and END date, the
intention is to get instances that are within this time-window. Falcon checks
if there are any instances between the start and end time. If there are
instances, return them. If not, return empty list.
Expecting the API caller to know the exact start time for entity is not very
user friendly. Hence I think this is invalid.
> For instance/status/process end point checks for start and end time is not
> working
> ----------------------------------------------------------------------------------
>
> Key: FALCON-718
> URL: https://issues.apache.org/jira/browse/FALCON-718
> Project: Falcon
> Issue Type: Bug
> Components: process
> Affects Versions: 0.6
> Reporter: Raghav Kumar Gautam
> Fix For: 0.6
>
> Attachments: entity.txt, request.txt
>
>
> I scheduled a process with a cluster validity start="2010-01-02T01:00Z"
> end="2010-01-02T01:22Z
> Then, I request api/instance/status/process/ endpoint with
> start=2010-01-02T00:00Z and end=2010-01-02T01:30Z, the request goes through.
> We would expect an error in this case.
> I suspect it is related to FALCON-166 and request [~bvellanki] to take a look.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
