Add support for materializeViews as schedule and task type #538
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, the schedule and task APIs only support one type of schedule and task which is extractRefresh. The word is hardcoded in the library. The changes in this PR is to make them more general so that the caller can decide what type of schedule and task is to be used. The changes still make extractRefresh the default type so that it will not cause problems to anyone that is already using the existing APIs.
Examples:
Currently,
server.tasks.get()gets all the extractRefresh tasks from a site. This will still work as is. But now users can callserver.tasks.get(task_type="materializedViews"to get all the materializeViews tasks from a site.Currently,
server.schedules.add_to_schedule(schedule_id, target_workbook)will add a workbook to extractRefresh schedule. Again, this will remain working. But now users can callserver.schedules.add_to_schedule(schedule_id, target_workbook, schedule_type="materializeViews")to add a workbook to a materializeViews schedule.The API version is changed to 3.8 for Tasks.get(...) in that the new
GET /sites/site-id/tasks/materializedViewsAPI will be under version 3.8.