[ 
https://issues.apache.org/jira/browse/SPARK-61038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated SPARK-61038:
-----------------------------------
    Labels: pull-request-available  (was: )

> Take the triggers of DataStreamWriter.trigger, including realTime, in the 
> Python client as PySpark does
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SPARK-61038
>                 URL: https://issues.apache.org/jira/browse/SPARK-61038
>             Project: Spark
>          Issue Type: Bug
>          Components: Connect
>    Affects Versions: connect-rust-4.3.0
>            Reporter: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: connect-rust-4.3.0
>
>
> In PySpark Connect, {{df.writeStream.trigger(...)}} takes exactly one of 
> {{processingTime}}, {{once}}, {{continuous}}, {{availableNow}} and 
> {{realTime}}, and raises {{ONLY_ALLOW_SINGLE_TRIGGER}} for none or more than 
> one. An interval or duration is a non-empty string, which it strips, else 
> {{VALUE_NOT_NON_EMPTY_STR}}, and {{once}} and {{availableNow}} are {{True}}, 
> else {{VALUE_NOT_ALLOWED}}. {{trigger(realTime="5 seconds")}} sets the 
> real-time trigger of the query, the {{real_time_batch_duration}} of its 
> {{WriteStreamOperationStart}}.
> The Rust-backed Python client raises {{NotImplementedError: the realTime 
> trigger is not yet supported by this client}} for {{realTime}}. It takes the 
> first trigger of several, raises a plain {{ValueError}} for none and for 
> {{once=False}}, and sends an empty or unstripped interval. Take the trigger 
> as PySpark does.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to