The reason is fairly simple actually - we don't want to commit to maintaining the specific APIs exposed. If we expose OpenHashSet, we will have to always keep that in Spark and not change the API.
On Tue, Jan 13, 2015 at 12:39 PM, Tae-Hyuk Ahn <ahn....@gmail.com> wrote: > Thank, Josh and Reynold. Yes, I can incorporate it to my package and > use it. But I am still wondering why you designed such useful > functions as private. > > On Tue, Jan 13, 2015 at 3:33 PM, Reynold Xin <r...@databricks.com> wrote: > > It is not meant to be a public API. If you want to use it, maybe copy the > > code out of the package and put it in your own project. > > > > On Fri, Jan 9, 2015 at 7:19 AM, Tae-Hyuk Ahn <ahn....@gmail.com> wrote: > >> > >> Hi, > >> > >> I would like to use OpenHashSet > >> (org.apache.spark.util.collection.OpenHashSet) in my standalone > program. I > >> can import it without error as: > >> > >> import org.apache.spark.util.collection.OpenHashSet > >> > >> However, when I try to access it, I am getting an error as: > >> > >> object OpenHashSet in package collection cannot be accessed in package > >> org.apache.spark.util.collection > >> > >> I suspect this error is caused by private object. I am wondering how I > can > >> use this object in my standalone program. > >> > >> Thanks, > >> > >> Ted > >> > >> > >> > >> -- > >> View this message in context: > >> > http://apache-spark-user-list.1001560.n3.nabble.com/How-to-access-OpenHashSet-in-my-standalone-program-tp21065.html > >> Sent from the Apache Spark User List mailing list archive at Nabble.com. > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: user-unsubscr...@spark.apache.org > >> For additional commands, e-mail: user-h...@spark.apache.org > >> > > >
