[
https://issues.apache.org/jira/browse/OODT-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001524#comment-13001524
]
Brian Foster commented on OODT-150:
-----------------------------------
| Can't you already do this with the MimeType action, that calls a checksummer?
the mime-type is based on the data-file, i need mime-type based on the checksum
file (i sometimes get different checksum files for the same data-type from the
same provider -- so attaching a checksum to a data-type mime-type is not gonna
cut it in my case)
| Maybe we could actually benchmark this before we claim that it will
unequivocally slow it down without having any hard # to say how much or why.
an xml-rpc connect takes just as long as or longer md5 checksum . . . aside
from waiting for resources and all the other complications this would introduce
| Keeping the dependency tree small was one part of it. The main part was that
all of your actions had a bunch of PEATE specific nomenclature in them (e.g.,
the policy to configure them, including environment variable refs, etc.). That
was the main thing I objected to.
changing names and paths takes like a few secs of grep replacements (and the
names of the actions are pretty generic -- PGPChecksum and MD5Checksum . . .
and they expect the checksum to exist in a file which is created by MD5 or PGP
with a given configurable extension)
| Yah, probably some baked in example config with the ExternAction would
probably make a lot of sense. Let's think about doing that and what a patch
would look like.
This would be in another JIRA issue i presume?
> ToggleAction addition to crawler
> --------------------------------
>
> Key: OODT-150
> URL: https://issues.apache.org/jira/browse/OODT-150
> Project: OODT
> Issue Type: New Feature
> Components: crawler
> Affects Versions: 0.2
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.3
>
> Attachments: crawler.OODT-150.2011-03-01.patch.txt
>
>
> Allows for cases where there are one of two (or more) actions which needs to
> run. For example: sometimes the same file types have different checksum files
> associated with it, this allows for either case.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
