Github user JoshRosen commented on the pull request:

    https://github.com/apache/spark/pull/9038#issuecomment-147611336
  
    I'm fairly concerned about the implications of having mutable state inside 
of ImperativeAggregates which isn't reset when switching to sort / could be 
shared across stages of a pipeline, so I'm slightly worried about the idea of 
reverting back to 8695e3f and merging this PR as of then: it seems like the 
same underlying problems could exist there, too.


---
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]

Reply via email to