[
https://issues.apache.org/jira/browse/SPARK-28592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16938028#comment-16938028
]
Imran Rashid commented on SPARK-28592:
--------------------------------------
[~holden] no, I think this is intentionally *not* a blocker. The idea is that
we can merge changes from the new api, even if the entire thing doesn't make it
into 3.0. We specifically do not want to block 3.0 on getting the entire thing
in (it would be great if we made it in, but don't think it should hold up the
release).
> Mark new Shuffle apis as @Experimental (instead of @Private)
> ------------------------------------------------------------
>
> Key: SPARK-28592
> URL: https://issues.apache.org/jira/browse/SPARK-28592
> Project: Spark
> Issue Type: Sub-task
> Components: Shuffle, Spark Core
> Affects Versions: 3.0.0
> Reporter: Imran Rashid
> Priority: Major
>
> The new Shuffle api is initially marked as {{@Private}}, just to discourage
> anyone from trying to make use of it before all the pieces are in place (in
> particular if spark 3.0 is released before everything is merged). But once
> its all merged we can change to {{@Experimental}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
