Hi Steven
Yes, I definitely think #2 is easier and cleaner for both reader and writer
and that lineage is a separate feature all together. There's no need to
couple materialization state with view lineage.
The other way to look at helping to decide between the two options is
what is the most per
Thank you Rahil for driving this, I left a comment as I am curious for #4 why
do we consider it as POST call instead of get? Otherwise +1
An endpoint fetchScanTasks was added in order for a client to get the
file-scan-tasks associated with a plan-task by providing a plan-task as input.
Thanks,
