On Sun, Oct 30, 2016 at 9:04 AM, Joshua Fox יהושע פוקס <[email protected] > wrote: > > Worst case: We've discussed writing something ourselves multiple times, >> that would scan our Datastore and writes entities out in a more useful way, >> but we haven't prioritized it. >> > > Evan, can you explain why this is not a high priority? Do you see > accidental deletion as unlikely? >
So far we are trusting that the existing datastore backup tool does something useful. :) The reason we've considered doing our own backup thing is to be able to do more selecting restores. For example, per-entity, per-namespace, or per date (we have a bunch of entities that include a timestamp attribute), depending on the reason. We haven't had the right disaster yet to prioritize us doing that work. I agree with you: I think protecting against programmer error is valuable! We are just hoping that we do enough of it already, and haven't been burned enough to cause us to put that ahead of new product work. Sadly, human nature being what it is, its hard to invest resources into a possible future disaster that has not yet happened. Still: this discussion has reminded me that we still have a bit more work to do on our Datastore and BigQuery backup stuff, so thanks! Evan -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/CACRPLjgvaL4smG34MLHHB%2BJF1QAW25vQm6dZuaOYp-CqdGHeJQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
