You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Around beginning of March, Y8M dataset we used for cloud storage extension notebook was closed.
Created a ticket for dataset provider: aws-samples/data-lake-as-code#28
And ticket for replacing the dataset: #247
But we need long-term solution for such situations.
It is risky to put some data on public dataset, as it could be used for "payment attack" when data is requested and AWS bills grow infinitely.
Around beginning of March, Y8M dataset we used for cloud storage extension notebook was closed.
Created a ticket for dataset provider: aws-samples/data-lake-as-code#28
And ticket for replacing the dataset: #247
But we need long-term solution for such situations.
It is risky to put some data on public dataset, as it could be used for "payment attack" when data is requested and AWS bills grow infinitely.
Possible solutions we discussed with @redcatbear and @tkilias:
Those options require deeper investigation.
The text was updated successfully, but these errors were encountered: