-
Notifications
You must be signed in to change notification settings - Fork 28.5k
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
[SPARK-4333][SQL] Correctly log number of iterations in RuleExecutor #3180
Conversation
…teration - 1 not iteration.
Can one of the admins verify this patch? |
Looks good. I find the handling of this variable a little funky as it reasons about its next value in the current iteration. |
ok to test |
Can you open a JIRA and change the title to something like:
|
Test build #23176 has started for PR 3180 at commit
|
Test build #23176 has finished for PR 3180 at commit
|
Test FAILed. |
|
@marmbrus ok i will change it. |
File line length can not exceeds 100 characters, so i split it to two lines.
Test build #23189 has started for PR 3180 at commit
|
Test build #23189 has finished for PR 3180 at commit
|
Test PASSed. |
Thanks! Merged to master and 1.2 |
When iterator of RuleExecutor breaks, the num of iterator should be (iteration - 1) not (iteration ).Because log looks like "Fixed point reached for batch ${batch.name} after 3 iterations.", but it did 2 iterations really! Author: DoingDone9 <[email protected]> Closes #3180 from DoingDone9/issue_01 and squashes the following commits: 571e2ed [DoingDone9] Update RuleExecutor.scala 46514b6 [DoingDone9] When iterator of RuleExecutor breaks, the num of iterator should be iteration - 1 not iteration. (cherry picked from commit 0cbdb01) Signed-off-by: Michael Armbrust <[email protected]>
When iterator of RuleExecutor breaks, the num of iterator should be (iteration - 1) not (iteration ).Because log looks like "Fixed point reached for batch ${batch.name} after 3 iterations.", but it did 2 iterations really!