sdap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Frank Greguska (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SDAP-142) Previously Completed Ingest Jobs Fail
Date Wed, 12 Sep 2018 20:13:00 GMT

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

Frank Greguska commented on SDAP-142:
-------------------------------------

I think the current situation is not ideal. I could see a few options:
 # Print a warning to the log, don't ingest anything, but complete successfully
 # Print a warning to the log but proceed with ingesting data normally
 # Leave it as it is

I think I prefer #1 in combination with an option that will allow an operator to force a job
to re-run ([SDAP-134|https://issues.apache.org/jira/projects/SDAP/issues/SDAP-134]).

[~jjacob], [~eyam], [~nchung] what do you guys think?

> Previously Completed Ingest Jobs Fail
> -------------------------------------
>
>                 Key: SDAP-142
>                 URL: https://issues.apache.org/jira/browse/SDAP-142
>             Project: Apache Science Data Analytics Platform
>          Issue Type: Improvement
>            Reporter: Frank Greguska
>            Priority: Major
>
> Currently, an ingest job that has already run and succeeded will fail with a message:
>  
> JobInstanceAlreadyCompleteException: A job instance already exists and is complete
>  
> Is this the behavior we want?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message