[
https://issues.apache.org/jira/browse/FALCON-493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047424#comment-14047424
]
Shwetha G S commented on FALCON-493:
------------------------------------
I think the right thing to do is not consider end as even process validity
start and end follows the same logic. We can check with users on how they use
it to figure out if it really needs to be fixed
> instance at "end" parameter in instance request not getting honoured
> ---------------------------------------------------------------------
>
> Key: FALCON-493
> URL: https://issues.apache.org/jira/browse/FALCON-493
> Project: Falcon
> Issue Type: Bug
> Components: common
> Affects Versions: 0.6
> Environment: QA
> Reporter: Samarth Gupta
> Assignee: Suhas Vasu
> Fix For: 0.4
>
>
> instance API's take 2 params , start and end. Till now feature was , all
> instances at both start and end time and between were returned in response
> and were acted on. but now it seems the instance at the "end" time is not
> being considered. Regression test is failing because of it, some of them :
> ProcessInstanceResumeTest.testProcessInstanceResume_lastInstance
> ProcessInstanceResumeTest.testProcessInstanceResume_resumeMany
> ProcessInstanceResumeTest.testProcessInstanceResume_withinRange
--
This message was sent by Atlassian JIRA
(v6.2#6252)
