spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jacek Laskowski <ja...@japila.pl>
Subject Re: Implicit from ProcessingTime to scala.concurrent.duration.Duration?
Date Mon, 18 Apr 2016 17:46:11 GMT
When you say "in the future", do you have any specific timeframe in
mind? You got me curious :)

Pozdrawiam,
Jacek Laskowski
----
https://medium.com/@jaceklaskowski/
Mastering Apache Spark http://bit.ly/mastering-apache-spark
Follow me at https://twitter.com/jaceklaskowski


On Mon, Apr 18, 2016 at 7:44 PM, Reynold Xin <rxin@databricks.com> wrote:
> The problem with this is that we might introduce event time based trigger in
> the future, and then it would be more confusing...
>
>
> On Monday, April 18, 2016, Jacek Laskowski <jacek@japila.pl> wrote:
>>
>> Hi,
>>
>> While working with structured streaming (aka SparkSQL Streams :)) I
>> thought about adding
>>
>> implicit def toProcessingTime(duration: Duration) =
>> ProcessingTime(duration)
>>
>> What do you think?
>>
>> I think it'd improve the API:
>>
>> .trigger(ProcessingTime(10 seconds))
>>
>> vs
>>
>> .trigger(10 seconds)
>>
>> (since it's not a release feature I didn't mean to file an issue in
>> JIRA - please guide if needed).
>>
>> Pozdrawiam,
>> Jacek Laskowski
>> ----
>> https://medium.com/@jaceklaskowski/
>> Mastering Apache Spark http://bit.ly/mastering-apache-spark
>> Follow me at https://twitter.com/jaceklaskowski
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
>> For additional commands, e-mail: dev-help@spark.apache.org
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org


Mime
View raw message