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
Traceback (most recent call last):
File "src/questdb/dataframe.pxi", line 2365, in questdb.ingress._dataframe
File "src/questdb/dataframe.pxi", line 2244, in questdb.ingress._dataframe_handle_auto_flush
questdb.ingress.IngressError: Could not flush buffer: Buffer size of 21780 exceeds maximum configured allowed size of 1024 bytes. - See https://py-questdb-client.readthedocs.io/en/v2.0.3/troubleshooting.html#inspecting-and-debugging-errors#flush-failed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/nick/PycharmProjects/questdb-scratch/df_scratch.py", line 17, in <module>
sender.dataframe(df, table_name='test_df', at=ServerTimestamp)
File "src/questdb/ingress.pyx", line 2403, in questdb.ingress.Sender.dataframe
File "src/questdb/dataframe.pxi", line 2396, in questdb.ingress._dataframe
File "src/questdb/dataframe.pxi", line 2375, in questdb.ingress._dataframe
questdb.ingress.IngressError: Bad dataframe row at index 999: All values are nulls. Ensure at least one column is not null.
The text was updated successfully, but these errors were encountered:
I am not sure max_buf_size can be removed (except perhaps set to 0, I don't recall). We default it to 100 MB. It serves a different purpose to auto_flush_bytes.
Though this example was artificial, it is easily triggered with the default config when using a wide dataframe (140 columns, long strings).
repro:
Error:
The text was updated successfully, but these errors were encountered: