[
https://issues.apache.org/jira/browse/APEXMALHAR-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897077#comment-15897077
]
ASF GitHub Bot commented on APEXMALHAR-2429:
--------------------------------------------
GitHub user Hitesh-Scorpio opened a pull request:
https://github.com/apache/apex-malhar/pull/572
APEXMALHAR-2429 Ambiguity in passing key parameter to Join accumulation
@chinmaykolhatkar please review.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Hitesh-Scorpio/apex-malhar
APEXMALHAR-2429_Ambiguity
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/apex-malhar/pull/572.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #572
----
commit 4e33c0c9661c1cafd219c9dfce20ee42bf57af6f
Author: Hitesh-Scorpio <forhitesh...@gmail.com>
Date: 2017-03-06T10:40:45Z
APEXMALHAR-2429 Ambiguity in passing key parameter to Join accumulation
----
> Ambiguity in passing "key" parameter to Join accumulation
> ---------------------------------------------------------
>
> Key: APEXMALHAR-2429
> URL: https://issues.apache.org/jira/browse/APEXMALHAR-2429
> Project: Apache Apex Malhar
> Issue Type: Improvement
> Reporter: Hitesh Kapoor
> Assignee: Hitesh Kapoor
>
> Currently we are passing a single String array as parameter and assuming that
> first entry is key from first stream and second entry from second stream and
> so and so forth. There is a scope to improve this.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
