You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oodt.apache.org by "Chris A. Mattmann (JIRA)" <ji...@apache.org> on 2014/08/03 20:22:12 UTC
[jira] [Commented] (OODT-682) Filemgr behaves differently when
clientTransfer is enabled
[ https://issues.apache.org/jira/browse/OODT-682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084071#comment-14084071 ]
Chris A. Mattmann commented on OODT-682:
----------------------------------------
[~bfoster] did you commit this and if so, in what revision?
> Filemgr behaves differently when clientTransfer is enabled
> ----------------------------------------------------------
>
> Key: OODT-682
> URL: https://issues.apache.org/jira/browse/OODT-682
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Affects Versions: 0.7
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.8
>
>
> Because the MetExtractors always run server-side, when client-side versioning happens the MetExtractor generated metadata is not available for the Versioner (this works find when server-side versioning is used).
> - this fix will sync product metadata to client before running versioning when clientTransfer is enabled.
> Probably best long-term fix for this is to move MetExtraction to client-side as well when clientTransfer is enabled... but making that clean and factoring out the code correctly is a bigger task... will put fix mentioned above in for now and later work on maybe this approach as a final fix.
--
This message was sent by Atlassian JIRA
(v6.2#6252)