I've got a script i want to keep low on memory, so I'm looping over a cursor.fetchone() call and processing each row individually.
But after about 30 minutes, it exits with
TrinoUserError(type=USER_ERROR, name=ABANDONED_QUERY, message=... Query results have not been accessed since 2023-10-13T17:10:23.546Z: currentTime 2023-10-13T17:15:23.774Z"
Whats more interesting is the timestamp for "accessed since" is actually when I started the script!
So somewhere along the line, the client is processing this error but waiting to spit it out? Let me know if anyone can tell what's going on here. Very curious behavior
tried:
- I tried looping over the contents of a DB table with the trino python client cursor.fetchone() and was successful for 30 minutes,
- expecting to reach the end of the table and exit the program normally,
- but what actually happened was that I received an error for having not accessed the query within 5 minutes of the start of the program.