Mailing-List: contact commits-help@oodt.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@oodt.apache.org
Date: Fri, 15 Jun 2012 20:39:43 +0000 (UTC)
From: "Brian Foster (JIRA)" <jira@apache.org>
To: commits@oodt.apache.org
Message-ID: <869377711.20052.1339792783597.JavaMail.jiratomcat@issues-vm>
In-Reply-To: 
 <1667316202.21363.1336045730106.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Comment Edited] (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=13295911#comment-13295911 ] 

Brian Foster edited comment on OODT-454 at 6/15/12 8:38 PM:
------------------------------------------------------------

let do this... there are 2 sets of config anyway... in the old backwards compatible config let leave it named UpdateWorkflowStatusToIngest... and in the new, which all your current scripts aren't gonna work with anyway (--operation look-n-feel), we will name it TriggerPostIngestWorkflow
                
      was (Author: bfoster):
    let do this... there are 2 sets of config anyway... in the old backwards compatible config let leave it named UpdateWorkflowStatusToIngest... and in the new, which all your current scripts aren't gonna work with anyway (--operator look-n-feel), we will name it TriggerPostIngestWorkflow
                  
> 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.5
>
>
> 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