Uh oh!
There was an error while loading. Please reload this page.
[SPARK-13195][Streaming]Fix NoSuchElementException when a state is not set but timeoutThreshold is defined - #11081
[SPARK-13195][Streaming]Fix NoSuchElementException when a state is not set but timeoutThreshold is defined#11081zsxwing wants to merge 1 commit into
Conversation
zsxwing
commented
Feb 4, 2016
cc @tdas |
tdas
commented
Feb 4, 2016
good catch. LGTM. Please merge to both 1.6 and master. |
zsxwing
commented
Feb 4, 2016
retest this please |
SparkQA
commented
Feb 4, 2016
Test build #50762 has finished for PR 11081 at commit
|
YuvalItzchakov
commented
Feb 4, 2016
Thank you guys for the quick fix. Is there a planned hotfix release soon? Or will I have to compile from source in the meanwhile? |
zsxwing
commented
Feb 4, 2016
You need to compile from source for now. If you cannot, a workaround is always updating the state in your codes. This patch will be available in the next release 1.6.1 (should be available soon). |
zsxwing
commented
Feb 4, 2016
Merging to master and 1.6 |
…ot set but timeoutThreshold is defined Check the state Existence before calling get. Author: Shixiong Zhu <shixiong@databricks.com> Closes#11081 from zsxwing/SPARK-13195. (cherry picked from commit 8e2f296) Signed-off-by: Shixiong Zhu <shixiong@databricks.com>
YuvalItzchakov
commented
Feb 4, 2016
Yes, that's how I've worked around it in the meanwhile. Thx @zsxwing |
ymeymann
commented
Feb 10, 2016
Just hit this issue too, thanks @zsxwing@YuvalItzchakov for the quick fix and workaround |
Check the state Existence before calling get.