[
https://issues.apache.org/jira/browse/FALCON-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364895#comment-14364895
]
Suhas Vasu commented on FALCON-1071:
------------------------------------
It is updated
{noformat}
Date end = EntityUtil.getNextInstanceTime(start,
EntityUtil.getFrequency(entityObject),
- EntityUtil.getTimeZone(entityObject));
+ EntityUtil.getTimeZone(entityObject), 1);
AbstractWorkflowEngine wfEngine = getWorkflowEngine();
return wfEngine.getInstanceParams(entityObject, start, end,
lifeCycles);
{noformat}
> Feed Listing API default behaviour for start and end not handled properly.
> ---------------------------------------------------------------------------
>
> Key: FALCON-1071
> URL: https://issues.apache.org/jira/browse/FALCON-1071
> Project: Falcon
> Issue Type: Improvement
> Components: feed
> Affects Versions: trunk
> Environment: QA
> Reporter: Karishma Gulati
> Assignee: Suhas Vasu
> Attachments: FALCON-1071-v2.patch, FALCON-1071.patch
>
>
> The default values of start and end, in case they aren't specified are as
> follows:
> {code}
> start <optional param>
> By default, it is set to (end - (10 * entityFrequency)).
> end <optional param>
> Default is set to now.
> {code}
> So, when only start is specified, it still takes the default value of end as
> now. Therefore, if a start time of say 2012 is specified, the output will be
> a massive 3 years worth instance information. If just start is specified, we
> can probably take the default value of end as start + (10*frequency), as is
> for the vice versa case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
