[ 
https://issues.apache.org/jira/browse/BEAM-10402?focusedWorklogId=534519&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-534519
 ]

ASF GitHub Bot logged work on BEAM-10402:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Jan/21 20:28
            Start Date: 11/Jan/21 20:28
    Worklog Time Spent: 10m 
      Work Description: je-ik commented on a change in pull request #13719:
URL: https://github.com/apache/beam/pull/13719#discussion_r555317940



##########
File path: 
sdks/java/core/src/main/java/org/apache/beam/sdk/transforms/windowing/Trigger.java
##########
@@ -87,7 +88,7 @@ protected Trigger() {
   }
 
   public List<Trigger> subTriggers() {
-    return subTriggers;
+    return MoreObjects.firstNonNull(subTriggers, Collections.emptyList());

Review comment:
       I agree that it is questionable why the field should ever be null. On 
the other hand, the code seems to distinguish cases when the field is null and 
when the list is empty. This might be fixed later with other nullness related 
fixes.




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 534519)
    Time Spent: 14.5h  (was: 14h 20m)

> [Umbrella] Eliminate nullability errors from Beam Java
> ------------------------------------------------------
>
>                 Key: BEAM-10402
>                 URL: https://issues.apache.org/jira/browse/BEAM-10402
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Priority: P1
>              Labels: Clarified, starter
>          Time Spent: 14.5h
>  Remaining Estimate: 0h
>
> I enabled the checker framework and the core SDK exceeds 100 nullability 
> errors immediately. We should make this number zero, since nullability errors 
> are solved problem in computer science and they do periodically impact Beam.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to