GitHub user zsxwing opened a pull request:
https://github.com/apache/spark/pull/12155
[SPARK-14382][SQL]QueryProgress should be post after committedOffsets is
updated
## What changes were proposed in this pull request?
Make sure QueryProgress is post after committedOffsets is updated. If
QueryProgress is post before committedOffsets is updated, the listener may see
a wrong sinkStatus (created from committedOffsets).
See
https://amplab.cs.berkeley.edu/jenkins/job/spark-master-test-maven-hadoop-2.2/644/testReport/junit/org.apache.spark.sql.util/ContinuousQueryListenerSuite/single_listener/
for an example of the failure.
## How was this patch tested?
Existing unit tests.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zsxwing/spark SPARK-14382
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/spark/pull/12155.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #12155
----
commit 9717c559d884534eee6ed30539334874a172eea9
Author: Shixiong Zhu <[email protected]>
Date: 2016-04-04T20:58:12Z
QueryProgress should be post after committedOffsets is updated
----
---
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 feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
