Staging: loop in SQL queries
Description
CAPL - Bug default text according to the team DoR (Definition of Ready)
02 - PROBLEM (WHAT'S THE ISSUE?):
- slack thread where the issue was raised
https://totvslabs.slack.com/archives/C0330CSV2/p1694699956719769
- it was identified a scenario with more than 2k requests to a select, that seems to be originated from the Staging UI
SELECT `s_1`.`mdmCreated`, `s_1`.`mdmLastUpdated`, `s_1`.`mdmId`, `s_1`.`mdmdeleted`, `s_1`.`chapa`, `s_1`.`codcoligada` FROM `stg_totvs_pfunc` `s_1` WHERE (UPPER(`s_1`.`chapa`) LIKE UPPER('%000666%'))
- the hypothesis is that some scenario on this tenant might be causing a loop of select, originated on these urls:
https://totvsclockin.carol.ai/totvsrm/carol-ui/connectors/totvs/pfunc?p=1&ps=25&order=ASC&filters=%5B%7B%22consolidation%22:%22n%22%7D,%7B%22chapa%22:%5B%22contains%22,%5B%22000666%22%5D%5D%7D%5D
- we don’t know if it can be relevant, but both stagings with issues seems to have ETL applied
03 - STEPS TO REPRODUCE (STEP (1...N), VIDEO, SCREENSHOTS, LOGS FOLDER, HEARTBEAT, ETC. – IF IS NOT POSSIBLE TO REPRODUCE EXPLAIN THE REASON):
- not reproducible
05 - EXPECTED BEHAVIOR (LIST THE EXPECTED BEHAVIORS TO CONSIDER THIS BUG AS DONE):
- identify potencial scenarios for a intense loop on the staging UI, and if found, add some delay or debounce mechanism
https://totvsclockin.carol.ai/totvsrm/carol-ui/connectors/totvs/pfunc?p=1&ps=25&order=ASC&filters=%5B%7B%22consolidation%22:%22n%22%7D,%7B%22chapa%22:%5B%22contains%22,%5B%22000666%22%5D%5D%7D%5D
https://totvsclockin.carol.ai/totvsrm/carol-ui/connectors/totvs/pfcompl?p=1&ps=25&order=ASC&filters=%5B%7B%22consolidation%22:%22y%22%7D,%7B%22chapa%22:%5B%22contains%22,%5B%22000666%22%5D%5D%7D%5D