You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Jungtaek Lim (Jira)" <ji...@apache.org> on 2025/05/15 06:49:00 UTC
[jira] [Resolved] (SPARK-52127) Squeeze the protocol of MapState KEYS / VALUES / ITERATOR for transformWithState in PySpark
[ https://issues.apache.org/jira/browse/SPARK-52127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jungtaek Lim resolved SPARK-52127.
----------------------------------
Fix Version/s: 4.1.0
Resolution: Fixed
Issue resolved by pull request 50885
[https://github.com/apache/spark/pull/50885]
> Squeeze the protocol of MapState KEYS / VALUES / ITERATOR for transformWithState in PySpark
> -------------------------------------------------------------------------------------------
>
> Key: SPARK-52127
> URL: https://issues.apache.org/jira/browse/SPARK-52127
> Project: Spark
> Issue Type: Improvement
> Components: PySpark, Structured Streaming
> Affects Versions: 4.1.0
> Reporter: Jungtaek Lim
> Assignee: Jungtaek Lim
> Priority: Major
> Fix For: 4.1.0
>
>
> Same as the rationale for SPARK-51891, we see the same opportunity to optimize the map state operation further in transformWithState in PySpark.
> Previously, we see the way of optimization for ListState.get() like following:
> * ListState.get() requires one more request to notice there is no further data to read. We can remove that request.
> ** This needs inlining response data to the proto message.
> This applies the same to MapState.keys()/values()/iterator().
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org