-
Notifications
You must be signed in to change notification settings - Fork 33
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
Fix refresh policy back to WAIT_FOR other than writing query result #554
Conversation
Signed-off-by: Tomoyuki Morita <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to confirm: my understanding is we need to make sure refresh policy is set to WAIT_FOR
in Spark job before we deploy this in Flint 0.5, right? Otherwise, the refresh policy of writing to result index becomes NONE
?
That's right. |
…554) Signed-off-by: Tomoyuki Morita <[email protected]> (cherry picked from commit def26cf) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
QQ: why it takes longer after this change? Previously it was around 40-45 mins and now it's around 1 hour?
…554) (#557) (cherry picked from commit def26cf) Signed-off-by: Tomoyuki Morita <[email protected]> Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…554) Signed-off-by: Tomoyuki Morita <[email protected]>
Description
Issues Resolved
List any issues this PR will resolve, e.g. Closes [...].
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.