[
https://issues.apache.org/jira/browse/SPARK-10985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14954234#comment-14954234
]
Reynold Xin commented on SPARK-10985:
-------------------------------------
Talked to Andrew offline. Removing the assignment.
[~bowenzhangusa] please comment here if you want to work on this. We usually do
the assignment when we actually merge a ticket, or when we know for sure a
particular contributor is committed to a feature and have the bandwidth to
complete it.
> Avoid passing evicted blocks throughout BlockManager / CacheManager
> -------------------------------------------------------------------
>
> Key: SPARK-10985
> URL: https://issues.apache.org/jira/browse/SPARK-10985
> Project: Spark
> Issue Type: Sub-task
> Components: Block Manager, Spark Core
> Reporter: Andrew Or
> Assignee: Bowen Zhang
> Priority: Minor
>
> This is a minor refactoring task.
> Currently when we attempt to put a block in, we get back an array buffer of
> blocks that are dropped in the process. We do this to propagate these blocks
> back to our TaskContext, which will add them to its TaskMetrics so we can see
> them in the SparkUI storage tab properly.
> Now that we have TaskContext.get, we can just use that to propagate this
> information. This simplifies a lot of the signatures and gets rid of weird
> return types like the following everywhere:
> {code}
> ArrayBuffer[(BlockId, BlockStatus)]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
