FE is not showing/loading the BigQuery Records
Description
PRDE - Bug default text according to the team DoR (Definition of Ready)
01 - PERSON OF CONTACT (PERSON THAT CAN ANSWER QUESTIONS ABOUT THE PROBLEM):
02 - PROBLEM (WHAT'S THE ISSUE?):
- FE is not showing/loading the BigQuery Records
- We’ve sent intake records but the staging is always in Running status
For more details with evidences please check the comments below.
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
- - Create a staging table
- Send records by intake
- Wait for the BQ records events tobe loaded
04 - LINKS (ADD A LINK TO THE BUG OR TO THE TENANT): <text>
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE): <text>
Activity
Show:
@MARCOS STUMPF ,
@Pedro Buzzi , @Fernando Nakamura ,
Esta issue acabou de ser vinculada na(s) issue(s) https://totvslabs.atlassian.net/browse/CAPL-5666#icft=CAPL-5666, conforme menções feitas no comentário anterior.
Este card foi utilizado para análise e está sendo finalizado. A implementação será no card: https://totvslabs.atlassian.net/browse/CAPL-5666
Good morning,
Analyzing this, seems to be a product design matter.
When testing (qarol sandbox) we should enable “STATISTICS_COLLECTOR_ENABLE” flag on Jenkins so that the required endpoints will be available to consolidate statistics data and provide to frontend. Without that the behavior we get is a “Running…” status.
Our advice is to maybe change the label to “Waiting…” to avoid misunderstandings, this way it becomes implicit that something should be running but (frontend) is still not getting a response.
Please find below attached images for reference on this issue.
With STATISTICS_COLLECTOR_ENABLE, frontend resolves BigQuery status:
Without STATISTICS_COLLECTOR_ENABLE, frontend keeps pooling:
Regards,
Fernando
@MARCOS STUMPF ,
@Pedro Buzzi ,
@Geny Isam Hamud Herrera ,
This issue was planned to be delivered until 2024-03-25. You can check that by consulting the issue in the Due Date field.
Dates already planned for this issue: 2024-03-25
If External Issue Link field is filled, customer was also informed on JIRA TOTVS.