[
https://issues.apache.org/jira/browse/OODT-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528818#comment-16528818
]
Chris A. Mattmann commented on OODT-985:
----------------------------------------
Thanks [~imesha] we should just use Complex types. This is more correct Java
and saves us of having to do magic on the SerDe end. With respect to workflow
manager and DRAT, this can easily be solved by simply taking the DRAT
dynWorkflow REST interface and bringing into the workflow services project.
Make sense?
> AvroRpcWorkflowManager only accepts a map of strings as metadata
> ----------------------------------------------------------------
>
> Key: OODT-985
> URL: https://issues.apache.org/jira/browse/OODT-985
> Project: OODT
> Issue Type: Bug
> Components: workflow manager
> Affects Versions: 1.2.2
> Reporter: Imesha Sudasingha
> Priority: Blocker
> Fix For: 1.9
>
>
> AvroRpcWorkflowManager only accepts a map of *String*:
> {code:java}
> // Ex: When creating a dynamic workflow
> @Override
> public String executeDynamicWorkflow(List<String> taskIds, Map<String,
> String> metadata) throws AvroRemoteException;
> {code}
> This becomes a problem when the metadata fields have a list of values. In
> XmlRpcWorkflowManager, this was like that and Avro version should behave the
> same to be compatible with other components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
