[
https://issues.apache.org/jira/browse/APEXCORE-448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15407454#comment-15407454
]
ASF GitHub Bot commented on APEXCORE-448:
-----------------------------------------
Github user tweise commented on the issue:
https://github.com/apache/apex-core/pull/364
This pull request attracts a lot of attention... Not to spoil the party,
but this looks like a rather minor change and there are many other pull
requests that I would consider of much higher importance that could need such
intense focus (deduper, join, windowing etc.). Assuming everyone has a lot of
work to do and the change is correct, I would suggest to merge this PR?
> Make operator name available in OperatorContext
> -----------------------------------------------
>
> Key: APEXCORE-448
> URL: https://issues.apache.org/jira/browse/APEXCORE-448
> Project: Apache Apex Core
> Issue Type: Improvement
> Reporter: Chandni Singh
>
> Need name of the logical operator in the OperatorContext which can be used by
> WindowDataManager to create a unique path per logical operator .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
