spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (SPARK-6168) Expose some of the collection classes as DeveloperApi
Date Wed, 25 Mar 2015 20:46:52 GMT

     [ https://issues.apache.org/jira/browse/SPARK-6168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sean Owen resolved SPARK-6168.
------------------------------
    Resolution: Won't Fix

It seems like there are several people who do not want to make this change, so I believe it
should be WontFix.

> Expose some of the collection classes as DeveloperApi
> -----------------------------------------------------
>
>                 Key: SPARK-6168
>                 URL: https://issues.apache.org/jira/browse/SPARK-6168
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.4.0
>            Reporter: Mridul Muralidharan
>            Priority: Minor
>
> It would be very useful to mark some of the collection and util classes we have as @DeveloperApi
or even @Experimental.
> For example :
> - org.apache.spark.util.BoundedPriorityQueue
> - org.apache.spark.util.collection.Utils
> - org.apache.spark.util.collection.CompactBuffer
> Usecases for these are for example to do a treeAggregate and/or treeReduce impl for common
api's within RDD which fail due to limitations of aggregate/reduce at scale (ref: SPARK-6165).
> Ofcourse, they are useful for other things too :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org


Mime
View raw message