-
Notifications
You must be signed in to change notification settings - Fork 29k
[DO-NOT-MERGE][SPARK-21145][SS] Added StateStoreProviderId with queryRunId to reload StateStoreProviders when query is restarted #18396
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Test build #78484 has finished for PR 18396 at commit
|
|
This looks weird. Many documentation goes mismatched after I just tested before this PR - https://gist.github.com/HyukjinKwon/ca77ffb7848af00c8a67e6e050b716a3 after this PR - https://gist.github.com/HyukjinKwon/481ca9e8aad918f4757eb0c8efb06ee4 To unblock the PR, (just based on my wild guess) I tried and found that a weird workaround was relocating. Let me try to prepare minimal reproduction and open an issue to GenJavaDoc. |
|
Thanks I will try that in my main PR - #18355 |
|
Test build #78491 has finished for PR 18396 at commit
|
|
@HyukjinKwon But why did this change in StreamTests change all the warnings to errors? |
|
For warnings becoming errors, I described this in https://issues.apache.org/jira/browse/SPARK-20840 with my tests and observations. Given my investigation, the root cause is, Javadoc8 produces both warnings and errors into standard error and SBT gets confused of which one is warning. One possible approach (which was done in SBT I believe) is to manually parse the log output (in a similar way I proposed in the JIRA) but it looks there is limitation. There are more information in the JIRA I investigated for a couple of weeks. +The basic rule for SBT with Javadoc is, up to my knowledge, produces both errors and warnings as errors if there is any error and produces warnings if there is no error. For mismatching docs, I don't know the exact reason. My wild guess was it got confused by nested ones so I just tried to put For not throwing errors for missing documentations in |
What changes were proposed in this pull request?
Copy of PR #18355 for testing the unidoc issue.
How was this patch tested?