Not using data flow is because of heavily for preference and also beam doesn’t support some of the requirements.
1. Managing late data is not supported in the Beam SDK for Python. 2. The Beam SDK for Python does not support triggers. 3. also code maturity and documentation maturity 4. preference So I understand there is no way to wait for response to a flexible api request for more than 1 hour. Ok thanks. — DK > On Feb 14, 2018, at 10:01 PM, 'Katayoon (Cloud Platform Support)' via Google > App Engine <email@example.com> wrote: > > > The document you are referring is for App Engine Standard Environment. > > > Could you provide more details on your use-case? For instance, If you want to > continuously receive and process data, Cloud Dataflow > can be a better option for you. > > > > On Wednesday, February 14, 2018 at 2:49:43 AM UTC-5, Dinçer Kavraal wrote:> > Hi, >> Here it says it is 24 hours, even for the standard environment. Am I >> interpreting this wrong? >> >> >> from >> https://cloud.google.com/appengine/docs/standard/python/an-overview-of-app-engine >> >> >> >> >> >> >>> Deadlines / Manual Scaling: >>> > Requests can run for up to 24 hours. A manually-scaled instance can >>> > choose to handle /_ah/start >>> and execute a program or script for many hours without returning an HTTP >>> response code. Task queue tasks can run up to 24 hours. >> >> >> >> >> I know this is not the best case even optimal case for AppEngine, but I am >> trying to find a way to utilize AppEngine for a small task, managing long >> running tcp connections. I know I can do this on a simple and small instance. >> >> >> Thanks >> >> >> >> On Tuesday, 13 February 2018 23:23:39 UTC+3, Katayoon (Cloud Platform >> Support) wrote:> The response time limit >>> in App Engine is one hour, so it is intended that you receive the error >>> message after one hour. Using manual scaling in the Flexible environment >>> doesn’t affect that. >>> >>> >>> Could you tell us why you need your requests to last for over an hour? It >>> might be that App Engine is not the best suited product for your needs. >>> >>> >>> You should also note that very heavy traffic might result in your server >>> serving a 504 error. I recommend that you scale up the number of your >>> instances >>> based on your traffic estimation or set it as automatic scaling. >>> >>> >>> >>> >>> >>> >>> >> >> > > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Google App Engine" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/google-appengine/A38kTCjvYrc/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > google-appengine+unsubscr...@googlegroups.com > . > To post to this group, send email to firstname.lastname@example.org > . > 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/20538e7e-feb9-4909-8489-52731d8e54d3%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout > . -- 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 email@example.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/F180DFD7-341D-4179-8BBA-EA5024E33CB0%40gmail.com. For more options, visit https://groups.google.com/d/optout.