Pycarol BQ - Expose big query object after query is executed

Description

DASC - Story default text according to the team DoR (Definition of Ready)

01 - PERSON OF CONTACT (WHO CAN ANSWER QUESTIONS):

@Breno Zipoli Monteiro Papa

02 - STORY AS A <PERSONA>, I [WANT TO] <NEED>, [SO THAT] <GOAL>:

As a pycarol user, when using BQ module, I need to check big query job logs, such as job id, time created, time started, time ended, slot time consumed, cached results and so on. Today is not possible to do it using pycarol because the method query() does not expose the big query client that has this information already, but only returns the results of the query executed.

In this issue (

) we needed evidences on what was taking more time, big query requests or customer’s backend. The client was using pycarol’s BQ module, and to do so, we edited bigquery.py file as attached, exposing the client object so the client could print/log the information we needed to validate what was taking the most time on the execution.

03 - PROBLEM (CURRENT SCENARIO OR PAIN TO BE RESOLVED?):

Only the result and job_id is exposed after using pycarol’s query() method on BQ module.

04 - WHO CAN USE THIS FEATURE (USER ROLES):

Anyone using pycarol’s BQ module.

05 - ACTIVITY DIAGRAM (ACTIVITY DIAGRAM LINK AND IMAGE):
06 - STEPS (ACTIONS TO BE PERFORMED LINKING TO SCREENSHOTS):

File attached with example code used in the support issue.

07 - ALTERNATIVE STEPS:
08 - ASSETS (RELEVANT DOCUMENTATION LINKS, JSON EXAMPLES, ETC):
09 - ACCEPTANCE CRITERIA / EXPECTED BEHAVIOR: