[
https://issues.apache.org/jira/browse/BEAM-3243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16267652#comment-16267652
]
ASF GitHub Bot commented on BEAM-3243:
--------------------------------------
jkff commented on issue #4172: [BEAM-3243] support multiple anonymous classes
from the same enclosing class in a pipeline
URL: https://github.com/apache/beam/pull/4172#issuecomment-347341595
That would be optimal, and in general I really like the idea of capturing
the stack trace of transform application and using it in all error messages. We
already do this in PAssert, but it can be applied much more widely - e.g.
errors during coder inference, validation errors, some runtime errors etc.
I suspect that implementing that can have some unexpected stumbling blocks,
so I would recommend to start with a simpler improvement - just make the error
message clearly say that the fix is to specify name in apply().
However, if you're willing to drive an effort to use application stack
traces in more places in Beam, starting with a discussion on the mailing list -
that would be a wonderful contribution and I'd be happy to review it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> multiple anonymous DoFn lead to conflicting names
> -------------------------------------------------
>
> Key: BEAM-3243
> URL: https://issues.apache.org/jira/browse/BEAM-3243
> Project: Beam
> Issue Type: Task
> Components: sdk-java-core
> Reporter: Romain Manni-Bucau
> Assignee: Romain Manni-Bucau
> Fix For: 2.3.0
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
