[
https://issues.apache.org/jira/browse/SPARK-18728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15726986#comment-15726986
]
Alex Levenson commented on SPARK-18728:
---------------------------------------
I think my comment above lists some concrete benefits. Algebird is a very light
dependency, and if you see anything wrong with it's (small) set of transitive
dependencies I think we'd be open to figuring out how to fix those sorts of
issues.
> Consider using Algebird's Aggregator instead of
> org.apache.spark.sql.expressions.Aggregator
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-18728
> URL: https://issues.apache.org/jira/browse/SPARK-18728
> Project: Spark
> Issue Type: Improvement
> Reporter: Alex Levenson
> Priority: Minor
>
> Mansur (https://twitter.com/mansur_ashraf) pointed out this comment in
> spark's Aggregator here:
> "Based loosely on Aggregator from Algebird:
> https://github.com/twitter/algebird";
> https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/expressions/Aggregator.scala#L46
> Which got a few of us wondering, given that this API is still experimental,
> would you consider using algebird's Aggregator API directly instead?
> The algebird API is not coupled with any implementation details, and
> shouldn't have any extra dependencies.
> Are there any blockers to doing that?
> Thanks!
> Alex
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
