[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14183 Merged build finished. Test PASSed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14183 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62277/ Test PASSed. ---

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14183 **[Test build #62277 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62277/consoleFull)** for PR 14183 at commit

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14183 Test PASSed. Refer to this link for build results (access rights to CI server needed): https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62276/ Test PASSed. ---

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14183 Merged build finished. Test PASSed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14183 **[Test build #62276 has finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62276/consoleFull)** for PR 14183 at commit

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14183 **[Test build #62277 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62277/consoleFull)** for PR 14183 at commit

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user tdas commented on the issue: https://github.com/apache/spark/pull/14183 Merging to master and 2.0. Tests dont matter here. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user tdas commented on the issue: https://github.com/apache/spark/pull/14183 LGTM. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user SparkQA commented on the issue: https://github.com/apache/spark/pull/14183 **[Test build #62276 has started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62276/consoleFull)** for PR 14183 at commit

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user tdas commented on the issue: https://github.com/apache/spark/pull/14183 ok to test --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] spark issue #14183: [SPARK-16114] [SQL] updated structured streaming guide

Github user AmplabJenkins commented on the issue: https://github.com/apache/spark/pull/14183 Can one of the admins verify this patch? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this