[
https://issues.apache.org/jira/browse/FALCON-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pragya Mittal updated FALCON-1575:
----------------------------------
Description:
If sla start time is after current time then response says start is after end.
{noformat}
dataqa@lda01:~$ date
Fri Oct 30 07:35:25 GMT 2015
dataqa@lda01:~$ falcon entity -type feed -start 2015-10-30T10:00Z -slaAlert
ERROR: Bad Request;start can not be after end
{noformat}
Instead it should say something like start date can not be in future.
was:
{noformat}
dataqa@lda01:~$ date
Fri Oct 30 07:35:25 GMT 2015
dataqa@lda01:~$ falcon entity -type feed -start 2015-10-30T10:00Z -slaAlert
ERROR: Bad Request;start can not be after end
dataqa@lda01:~$
{noformat}
> Non-intuitive message from SLA API if start date is after currentTime
> ---------------------------------------------------------------------
>
> Key: FALCON-1575
> URL: https://issues.apache.org/jira/browse/FALCON-1575
> Project: Falcon
> Issue Type: Bug
> Components: feed, prism
> Affects Versions: trunk
> Environment: QA
> Reporter: Pragya Mittal
> Labels: newbie
> Fix For: trunk
>
>
> If sla start time is after current time then response says start is after end.
> {noformat}
> dataqa@lda01:~$ date
> Fri Oct 30 07:35:25 GMT 2015
> dataqa@lda01:~$ falcon entity -type feed -start 2015-10-30T10:00Z -slaAlert
> ERROR: Bad Request;start can not be after end
> {noformat}
> Instead it should say something like start date can not be in future.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
