Jerry Cwiklik created UIMA-5540:
-----------------------------------
Summary: UIMA-AS: Aggregate type priorities are not merged
properly
Key: UIMA-5540
URL: https://issues.apache.org/jira/browse/UIMA-5540
Project: UIMA
Issue Type: Bug
Components: Async Scaleout
Reporter: Jerry Cwiklik
Assignee: Jerry Cwiklik
Fix For: 2.10.0AS
The UIMA-AS aggregate merges type priorities from all delegates. When all
delegates report back, the aggregate does *not* merge its type priorities. The
consequence is that the aggregate's type priorities are clobbered due to this:
aggregateMetadata.setTypePriorities(getCasManagerWrapper().getMetadata().getTypePriorities());
In the above, the CasManager contains type priorities from all delegates only.
When UIMA-AS client receives Meta from an aggregate service, the type
priorities are missing if an aggregate was the only one that defined it. If
type priorities are moved from aggregate to a delegate all is well since the
merge successfully added them to the aggregate meta.
The fix is to merge an aggregate type priorities with the delegate type
priorities before calling
aggregateMetadata.setTypePriorities(...);
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
