Alex Levenson created SPARK-18728:
-------------------------------------
Summary: 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: Bug
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
