You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2021/08/01 01:42:00 UTC
[jira] [Resolved] (SPARK-36319) Have Observation return Map instead
of Row
[ https://issues.apache.org/jira/browse/SPARK-36319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyukjin Kwon resolved SPARK-36319.
----------------------------------
Fix Version/s: 3.3.0
Resolution: Fixed
Issue resolved by pull request 33545
[https://github.com/apache/spark/pull/33545]
> Have Observation return Map instead of Row
> ------------------------------------------
>
> Key: SPARK-36319
> URL: https://issues.apache.org/jira/browse/SPARK-36319
> Project: Spark
> Issue Type: Improvement
> Components: Java API, PySpark, SQL
> Affects Versions: 3.3.0
> Reporter: Enrico Minack
> Assignee: Enrico Minack
> Priority: Major
> Fix For: 3.3.0
>
>
> As [~gurwls223] pointed out, the {{Observation}} API (Scala, Java, PySpark) could return a {{Map}} / {{Dict}}. It currently returns {{Row}} simply because the metrics are (internal to {{Observation}}) retrieved from the listener as rows. Since that is hidden from the user by the {{Observation}} API, there is no need to return {{Row}}.
> If there is some value in the original {{Row}}, both could be provided via {{getAsRow}} and {{getAsMap}}.
> The {{Observation}} API has been added to Spark in unreleased 3.3.0, so it should not be a blocker to remove the {{Row}} return type in 3.3.0 again.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org