You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (JIRA)" <ji...@apache.org> on 2017/05/25 11:12:04 UTC

[jira] [Commented] (SPARK-20883) Improve StateStore APIs for efficiency

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

Apache Spark commented on SPARK-20883:
--------------------------------------

User 'tdas' has created a pull request for this issue:
https://github.com/apache/spark/pull/18107

> Improve StateStore APIs for efficiency
> --------------------------------------
>
>                 Key: SPARK-20883
>                 URL: https://issues.apache.org/jira/browse/SPARK-20883
>             Project: Spark
>          Issue Type: Improvement
>          Components: Structured Streaming
>    Affects Versions: 2.2.0
>            Reporter: Tathagata Das
>            Assignee: Tathagata Das
>
> Current state store API has a bunch of problems that causes too many transient objects causing memory pressure.
> - StateStore.get() returns Options which forces creation of Some/None objects for every get
> - StateStore.iterator() returns tuples which forces creation of new tuple for each record returned
> - StateStore.updates() requires the implementation to keep track of updates, while this is used minimally (only by Append mode in streaming aggregations). This can be totally removed.



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