Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14168
@sameeragarwal that's a good defensive measure.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this featu
Github user sameeragarwal commented on the issue:
https://github.com/apache/spark/pull/14168
@ericl as an alternative, did you consider simply defining `boolean
${ev.isNull} = false;` for even the non-nullable branches in `nullSafeCodegen`
(e.g., here:
https://github.com/apache/spark
Github user rxin commented on the issue:
https://github.com/apache/spark/pull/14168
Thanks - merging in master/2.0.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and w
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14168
Merged build finished. Test PASSed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14168
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62202/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14168
**[Test build #62202 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62202/consoleFull)**
for PR 14168 at commit
[`4524d97`](https://github.com/apache/spark/commit/
Github user ericl commented on the issue:
https://github.com/apache/spark/pull/14168
Sure
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
