[google-appengine] Practical Functional Distributed Programming, using Python on App Engine
Hi all, I don't know if it's appropriate to post this here, but this might be interesting to a lot of people who are using Python on App Engine. https://medium.com/the-infinite-machine/practical-functional-distributed-programming-using-python-on-app-engine-e19490580508 -- Emlyn https://medium.com/the-infinite-machine - A publication about Google App Engine sutllang.com - My language sUTL https://plus.google.com/u/0/100281903174934656260 - Google+ -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/CAMp1VPACjrjVm7TvxoaZrrVXRh%2B6UGQChicYQwt8Jcc54kqPMg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Run scheduled Dataflow job from AppEngine web application (flask) - ImportError: No module named dataflow_pipeline
The application is deployed successfully and can be scheduled/ launched via cron. it creates the dataflow job successfully and then the job fails. The flow reads data from Bigquery, filters rows and writes to Bigquery. The filter step fails (beam.Filter()) *error details from google error report:* ImportError: No module named dataflow_pipeline at _import_module (/usr/local/lib/python2.7/dist-packages/dill/dill.py:767) at load_reduce (/usr/lib/python2.7/pickle.py:1133) at load (/usr/lib/python2.7/pickle.py:858) at load (/usr/local/lib/python2.7/dist-packages/dill/dill.py:266) at loads (/usr/local/lib/python2.7/dist-packages/dill/dill.py:277) at loads (/usr/local/lib/python2.7/dist-packages/apache_beam/internal/pickler.py:225) at dataflow_worker.operations.DoOperation.start (dataflow_worker/operations.c:9775) (operations.py:289) at dataflow_worker.operations.DoOperation.start (dataflow_worker/operations.c:10574) (operations.py:284) at dataflow_worker.operations.DoOperation.start (dataflow_worker/operations.c:10680) (operations.py:283) at execute (/usr/local/lib/python2.7/dist-packages/dataflow_worker/executor.py:166) at do_work (/usr/local/lib/python2.7/dist-packages/dataflow_worker/batchworker.py:581) when running dataflow manually from client, works fine! any suggestions and comments would be really helpful! -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/b4c8f43d-4b98-48e8-bd8a-5e090af8c717%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Sydney Data Center and migration of app engine application
That article says that Google App Engine is not available in the Sydney region and will come later... On Tuesday, August 29, 2017 at 6:35:15 PM UTC+10, Mark Hetherington wrote: > > Hi, > > With the commissioning of the Sydney data centre, there are no doubt many > Australia based customers wanting to migrate to the new data centre. I > imagine the same was true when other locations opened up worldwide. > > We have existing app engine, cloud sql, cloud storage and data store > assets we would like to migrate. Has anyone undertaken this process? Our > understanding is that we can create a new application in the new zone, and > do a backup and restore. However there are a few hurdles. Some of the > issues we see are: > >- The application name currently in use won't be available for use in >the new zone, thus requiring a rename of the application >- The process of cutting over between zones may require us to update a >number of DNS A records managed by third parties. >- The CNAME to ghs.googlehosted.com must cut over to the new >application at some point, but I'm not sure how this is managed. > Presumably >when verifying the domain into the new application google starts serving a >new result when ghs.googlehosted.com is queried? > > Are there any migration tools available? Does google offer any assistance > in this regard? According to a news article at > https://www.crn.com.au/news/google-cloud-finally-comes-to-sydney-today-465735, > > " > Google Cloud platform managing director APJ Rick Harshman told CRN that > customers wanting to migrate to local availability zones can contact one of > its partners, or Google's customer engineering team to help with the > migration.", but I'm not sure how to get in touch with the "customer > engineering team". > > Cheers, > Mark > > > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/25039333-d6ad-4281-b5a2-a401891d79ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
