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 2016/01/08 11:50:39 UTC

[jira] [Commented] (SPARK-4698) Data-locality aware Partitioners

    [ https://issues.apache.org/jira/browse/SPARK-4698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15089048#comment-15089048 ] 

Sean Owen commented on SPARK-4698:
----------------------------------

Looking through old tickets -- These partitioners may necessarily put together data that doesn't exist together already. Is the suggestion to try to maximize the locality? I assume that's NP-complete or something but still possible to get close to with heuristics. I doubt this would be implemented in general but if that's the idea it's fine.

> Data-locality aware Partitioners
> --------------------------------
>
>                 Key: SPARK-4698
>                 URL: https://issues.apache.org/jira/browse/SPARK-4698
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Kevin Mader
>            Priority: Minor
>
> The current hash and range partitioner tools do not seem to respect the existing data-locality. A 'dictionary' driven partitioner that calculated the partitions based on the existing key locations instead of re-calculating them would be ideal.



--
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