[
https://issues.apache.org/jira/browse/OODT-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12969234#action_12969234
]
Brian Foster commented on OODT-72:
----------------------------------
- your counter example creates a xml-rpc client connection within an xml-rpc
client connection . . . out of a 100 concurrent threads allowed to a filemgr
server you are now making each ingest utilize 2 of those threads
- you metextractor is faulty: Product p = Product.blankProduct(); . . . what if
your Versioner uses product.getProductId()? . . . you FileLocation metadata
field is not going to be accurate
"Sigh, again not true. Not in all cases."
- yes . . . either on the client or the server . . . it will be dynamically
loaded . . . otherwise the product will never get versioned
"Not sure how?"
- on the server side in the ingestProduct method, modify it so that it clones
the Metadata object before calling the Versioner
> Unable to set Metadata based off Product Versioning during Product ingestion
> ----------------------------------------------------------------------------
>
> Key: OODT-72
> URL: https://issues.apache.org/jira/browse/OODT-72
> Project: OODT
> Issue Type: Improvement
> Components: file manager
> Affects Versions: 0.1-incubating
> Environment: none
> Reporter: Brian Foster
> Assignee: Brian Foster
> Priority: Minor
> Fix For: 0.2
>
>
> Ingest order:
> - add product to catalog
> - metextractors run
> - add metadata to catalog
> - versioner runs (on client or on server)
> - add references to catalog
> This prevents Metadata elements such as FileLocation from being set based off
> Product References since metadata is added to catalog pre-versioning
> - A known work-around is to run the versioner twice (once in a MetExtractor
> and again when the Versioner is run in the ingest process) . . . however this
> is very much a work-around and setting elements such as FileLocation is a
> very common functionality.
> I purpose that Versioning take place before MetExtractors run.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
