Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/4029#issuecomment-70295103
If the only backwards incompatibility is via pattern matching on listener
events, can we maybe just make the new field a mutable var that's set outside
of the constructor? This should avoid that incompatibility even if it's a
little messy.
Sent from my phone
> On Jan 16, 2015, at 10:04 AM, andrewor14 <[email protected]> wrote:
>
> The changes here actually LGTM, so I will merge this in master. Thanks
@sarutak!
>
> â
> Reply to this email directly or view it on GitHub.
>
---
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 is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
