You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Dongjoon Hyun (JIRA)" <ji...@apache.org> on 2018/12/22 01:53:00 UTC

[jira] [Updated] (SPARK-26428) Minimize deprecated `ProcessingTime` usage

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

Dongjoon Hyun updated SPARK-26428:
----------------------------------
    Description: Use of `ProcessingTime` class was deprecated in favor of `Trigger.ProcessingTime` in Spark 2.2. And, SPARK-21464 minimized it at 2.2.1. Recently, it grows again in test suites. This issue aims to clean up newly introduced deprecation warnings.  (was: Use of `ProcessingTime` class was deprecated in favor of `Trigger.ProcessingTime` in Spark 2.2. And, SPARK-21464 minimized it at 2.2.1. Recently, it grows a little in test suites. This issue aims to clean up newly introduced deprecation warnings.)

> Minimize deprecated `ProcessingTime` usage
> ------------------------------------------
>
>                 Key: SPARK-26428
>                 URL: https://issues.apache.org/jira/browse/SPARK-26428
>             Project: Spark
>          Issue Type: Improvement
>          Components: Tests
>    Affects Versions: 3.0.0
>            Reporter: Dongjoon Hyun
>            Priority: Minor
>
> Use of `ProcessingTime` class was deprecated in favor of `Trigger.ProcessingTime` in Spark 2.2. And, SPARK-21464 minimized it at 2.2.1. Recently, it grows again in test suites. This issue aims to clean up newly introduced deprecation warnings.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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