You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2017/02/23 21:43:44 UTC
[jira] [Commented] (SPARK-19717) Expanding Spark ML under Different
Namespace
[ https://issues.apache.org/jira/browse/SPARK-19717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881331#comment-15881331 ]
Sean Owen commented on SPARK-19717:
-----------------------------------
I don't know that this should be a JIRA. What are you specifically asking to open up and why? those sorts of details need to be here.
> Expanding Spark ML under Different Namespace
> --------------------------------------------
>
> Key: SPARK-19717
> URL: https://issues.apache.org/jira/browse/SPARK-19717
> Project: Spark
> Issue Type: Wish
> Components: ML, MLlib
> Affects Versions: 2.1.0
> Reporter: Shouheng Yi
> Priority: Minor
>
> This ticket is corresponding to a previous email thread in the dev list: [Spark Namespace]: Expanding Spark ML under Different Namespace?
> The concern is about making some access modifier of some classes/trait from "private [spark]" to public.
> Right now, the options to solve this issues are:
> 1. write or copy your own implementations
> 2. work under org.apache, but have some comments to address this issue
> Details can be found in the dev list email archive.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org