You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi; swapping out backends to tectonic DB causes strange issues with the reader timing out when it makes larger queries (a few hours of data). I think there is a corner case that isnt tested for this, since retrieve test seems to only retrieve 2 entries, which will avoid this issue. the most troubling thing is that starting an interactive shell with ex_tectonicdb and querying for the same range will actually return a result quickly (much quicker than the default 5 second timeout). Digging even further into whats happening with the erlang observer, I can see that the data associated with the query is being returned in its entirety.
Hi; swapping out backends to tectonic DB causes strange issues with the reader timing out when it makes larger queries (a few hours of data). I think there is a corner case that isnt tested for this, since retrieve test seems to only retrieve 2 entries, which will avoid this issue. the most troubling thing is that starting an interactive shell with ex_tectonicdb and querying for the same range will actually return a result quickly (much quicker than the default 5 second timeout). Digging even further into whats happening with the erlang observer, I can see that the data associated with the query is being returned in its entirety.
could you please release or double check whether the tectonicDB backend implementation? any advice would be helpful
The text was updated successfully, but these errors were encountered: