Begin a QueryJob without waiting for it to finish #5435

Activity

1. tseaver

   added

   type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.

   api: bigqueryIssues related to the BigQuery API.Issues related to the BigQuery API.

   on Jun 4, 2018
2. tseaver commented on Jun 4, 2018

   

   tseaver

   on Jun 4, 2018

   Contributor

   More actions

   PR #4242 renamed the begin method to _begin, making it private: the expected usage pattern is that the caller use job.result() to begin the job, and then use the future it returns.

   @tswast I'll defer to your opinion here.
3. bencaine1 commented on Jun 4, 2018

   

   bencaine1

   on Jun 4, 2018

   Author

   More actions

   I can explain my use case a little more: I'm trying to start a query and print out the query if there's syntax error. The following code does not work:

               try:
                   return query_job.result()
               except GoogleCloudError as e:
                   msg = str(e)
                   # This craziness puts line numbers next to the SQL.
                   lines = query.split('\n')
                   longest = max(len(l) for l in lines)
                   # Print out a 'ruler' above and below the SQL so we can judge columns.
                   ruler = ' ' * 4 + '|'  # Left pad for the line numbers (4 digits plus ':')
                   for _ in range(longest / 10):
                       ruler += ' ' * 4 + '.' + ' ' * 4 + '|'
                   header = '-----Offending Sql Follows-----'
                   padding = ' ' * ((longest - len(header)) / 2)
                   msg += '\n\n{}{}\n\n{}\n{}\n{}'.format(padding, header, ruler, '\n'.join(
                       '{:4}:{}'.format(n + 1, line) for n, line in enumerate(lines)), ruler)
                   raise RuntimeError(msg)
   

   Because the Retry object has a try/except block, so having this method in a try/except will bypass the Retry functionality due to nested try/excepts being weird in python.

   What I want to do is begin the job, then check the job for errors periodically, and print the query and error if there are any errors and continue if the job executed successfully.
4. bencaine1 commented on Jun 4, 2018

   

   bencaine1

   on Jun 4, 2018

   Author

   More actions

   It actually looks like _begin is called when the query_job is created via Client.query(). So you can actually close this ticket. Thanks!

   👍React with 👍1Reacted by Mohit Nalavadi
5. tseaver

   closed this as completedon Jun 4, 2018
6. tseaver

   added

   status: invalid

   on Jun 4, 2018
7. tswast commented on Jun 4, 2018

   

   tswast

   on Jun 4, 2018

   Contributor

   More actions

   @bencaine1 Is correct. Calling Client.query() starts the job. No need to call result() if you don't need to wait for it to finish.
8. JustinBeckwith

   assigned

   tseaver

   on Feb 1, 2021