Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Date: Fri, 15 Jun 2012 03:45:43 +0000 (UTC)
From: "Chris A. Mattmann (JIRA)" <jira@apache.org>
To: commits@oodt.apache.org
Message-ID: <1141527986.17674.1339731943142.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1667316202.21363.1336045730106.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (OODT-454) Crawler command line bugs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris A. Mattmann commented on OODT-454:
----------------------------------------

Hey Tom!

bq. I've just realised this issues is still open. Sorry!

No worries!

bq. An annoying question - do I keep the TriggerPostIngestWorkflow or use the UpdateWorkflowStatusToIngest?

I would prefer that (for back compat perspective) we leave it as it was (UpdateWorkflowStatusToIngest).

bq. Is there still time to close this issue before 0.4 release? Issue 1) has fallen away and I need to commit to resolve issue 2) and 3) (see the 3 issues in the Description).

I would just set it for 0.5 unless you think this is critical for a respin. If you think so, just let pramirez know on the dev list and we can DISCUSS a respin. No worries if that's the case!

Thanks man.


> Crawler command line bugs
> -------------------------
>
>                 Key: OODT-454
>                 URL: https://issues.apache.org/jira/browse/OODT-454
>             Project: OODT
>          Issue Type: Bug
>          Components: crawler
>    Affects Versions: 0.4
>            Reporter: Thomas Bennett
>            Assignee: Thomas Bennett
>            Priority: Minor
>              Labels: patch
>             Fix For: 0.4
>
>
> I've think I've flushed out a few crawler command line bugs:
> 1) --actionIds can currently fails when more than 1 actionId is specified
> 2) ActionId Unique fails because the filemgrUrl is not set.
> 3) ActionId TriggerPostIngestWorkflow is not configured correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira