falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1747) Falcon instance status listing is throwing error message.
Date Fri, 15 Jan 2016 07:38:39 GMT

    [ https://issues.apache.org/jira/browse/FALCON-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101378#comment-15101378
] 

Ajay Yadava commented on FALCON-1747:
-------------------------------------

[~peeyushb] Good catch [~peeyushb]! Will it make sense to set start date to cluster start
date if it is before cluster start date? It might be getting handled somewhere later in code
flow/oozie but explicitly checking it here will make the logic more readable/predictable.



> Falcon instance status listing is throwing error message.
> ---------------------------------------------------------
>
>                 Key: FALCON-1747
>                 URL: https://issues.apache.org/jira/browse/FALCON-1747
>             Project: Falcon
>          Issue Type: Bug
>          Components: prism
>            Reporter: Peeyush Bishnoi
>            Assignee: Peeyush Bishnoi
>             Fix For: 0.9
>
>         Attachments: FALCON-1747.patch
>
>
> When trying to do listing of Falcon instance, following error message appears:
> {code:java}
> ERROR: Bad Request;default/Specified End date 2016-01-12T10:20Z is before the entity
was scheduled 221558424-03-21T20:03Z
> {code}
> Process entity validity start date and end date is valid.
> This issue has been reported by one of the user internally at Hortonworks.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message