[ https://issues.apache.org/jira/browse/BEAM-1663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014657#comment-16014657 ]
ASF GitHub Bot commented on BEAM-1663: -------------------------------------- Github user asfgit closed the pull request at: https://github.com/apache/beam/pull/3151 > Generated package names should be deterministic and consistent across runs. > --------------------------------------------------------------------------- > > Key: BEAM-1663 > URL: https://issues.apache.org/jira/browse/BEAM-1663 > Project: Beam > Issue Type: Improvement > Components: runner-core, sdk-java-core > Reporter: Alex Amato > Assignee: Kenneth Knowles > > This makes it difficult for error/stack trace processing systems to identify > that these two errors are the same. > These two errors contain generated package names with random strings in them, > would it be possible to make the generated package names consistent across > each job run? From what I understand the random string is to prevent two > package names from colliding. Perhaps we could have the name be of the > generated packages be based off the functions they are wrapping/referring to? > YZjse2Tt > 1TK4aKgJ > src.test.java.org.apache.beam.examples.cookbook.LoggedException: > LoggedException > at > src.test.java.org.apache.beam.examples.cookbook.CloudErrorReporting$WriteLogs$1.processElement > (CloudErrorReporting.java:94) > at > src.test.java.org.apache.beam.examples.cookbook.CloudErrorReporting$WriteLogs$1$auxiliary$1TK4aKgJ.invokeProcessElement > (Unknown Source) > --- > src.test.java.org.apache.beam.examples.cookbook.LoggedException: > LoggedException > at > src.test.java.org.apache.beam.examples.cookbook.CloudErrorReporting$WriteLogs$1.processElement > (CloudErrorReporting.java:94) > at > src.test.java.org.apache.beam.examples.cookbook.CloudErrorReporting$WriteLogs$1$auxiliary$YZjse2Tt.invokeProcessElement > (Unknown Source) -- This message was sent by Atlassian JIRA (v6.3.15#6346)