-
Notifications
You must be signed in to change notification settings - Fork 60
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
Remove manual refresh for S3 integrations #1226
Conversation
Signed-off-by: Simeon Widdis <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #1226 +/- ##
==========================================
- Coverage 44.07% 44.06% -0.01%
==========================================
Files 329 329
Lines 19668 19672 +4
Branches 4735 4685 -50
==========================================
Hits 8669 8669
- Misses 10422 10958 +536
+ Partials 577 45 -532
Flags with carried forward coverage won't be shown. Click here to find out more. |
{table_name}; | ||
{table_name} | ||
WITH ( | ||
auto_refresh = 'true', |
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.
any option to configure refresh?
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.
Not really, can maybe look at adding it in a future release
(cherry picked from commit 80f112a) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
(cherry picked from commit 80f112a) Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Description
Instead of doing the refresh synchronously as part of integration installation, we configure the MV for autorefresh and let it run in the background. This can lead to some start-up time for integrations before showing data, but speeds up the installation process.
Issues Resolved
N/A
Check List
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.