Great to see all this discussion! We've also launched a Trusted Tester for moving Datastore --> BigQuery for analysis using the Datastore admin backup functionality. More info here: https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dHdpeXlmRlZCNWlYSE9BcE5jc2NYOUE6MQ
This basically allows you to move your datastore data to BigQuery in two simple operations: 1) take a backup using datastore admin, saving the data into cloud storage 2) make an API call or run bq.py to load the datastore backup into bigquery Schema is automatically handled for you. Cheers, -Ryan On Monday, October 15, 2012 3:31:47 AM UTC-7, Richard Watson wrote: > > One of the issues of the datastore is a lack of SQL-like aggregates, or > easy ad-hoc queries in general. This adds a lot of cost to reporting, > dashboards, etc. Is BigQuery the default choice for this type of work, > now? For those who have used it, what kinds of things should we watch out > for? What types of result do you cache back in the datastore, or do you > just run all that from BigQuery? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/AY2hMQM3kmIJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
