You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "David Milicevic (Jira)" <ji...@apache.org> on 2025/11/21 13:51:00 UTC

[jira] [Commented] (SPARK-48457) [M0] Testing and operational readiness

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

David Milicevic commented on SPARK-48457:
-----------------------------------------

I'm marking this item as done (cleanup before Spark 4.1 release).

We did this, but it was [~milan.dankovic] who did it. He will be back from vacation next Monday, so he will update with more details, test plans, and other related docs.

> [M0] Testing and operational readiness
> --------------------------------------
>
>                 Key: SPARK-48457
>                 URL: https://issues.apache.org/jira/browse/SPARK-48457
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Spark Core
>    Affects Versions: 4.0.0
>            Reporter: David Milicevic
>            Priority: Major
>
> We are basically doing this as we are developing the feature. This work item should serve as a checkpoint by the end of M0 to figure out if we have covered everything.
>  
> Testing is very clearly defined by itself.
> For the operational readiness part, we are still to figure out what exactly we can do in the case of SQL scripting. It's a really straightforward feature and public documentation should serve well enough for most of the issues we might encounter. But, we should probably think about:
>  * Some KPI indicators.
>  * Telemetry.
>  * Something else?



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