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
I got a wired problem while running chdb insert in local vscode jupyter notebook(not reproducing on Google Colab or raw python)
Insert from INFILE and VALUES got stuck either.
I have added some test code for this in test_insert_vector.py to comfirm raw python interpreter is not affected.
I also comfirm Google Colab is also not affected.
I'll try to fix that after I finished #150 . No help needed, just open this issue in case I forget.
Code to reproduce:
print("start")
fromchdbimportsessionprint("Connecting to database")
chs=session.Session()
print("Creating database")
chs.query("CREATE DATABASE IF NOT EXISTS movie_embeddings ENGINE = Atomic")
print("Creating table")
chs.query("USE movie_embeddings")
chs.query('DROP TABLE IF EXISTS embeddings')
chs.query('DROP TABLE IF EXISTS embeddings_with_title')
print("Creating table with movie titles")
chs.query("""CREATE TABLE embeddings ( movieId UInt32 NOT NULL, embedding Array(Float32) NOT NULL ) ENGINE = MergeTree() ORDER BY movieId""")
print("Inserting movie embeddings into the database")
# Insert from INFILE and VALUES got stuck either# chs.query("INSERT INTO embeddings FROM INFILE 'movie_embeddings.csv' FORMAT CSV")chs.query("INSERT INTO embeddings VALUES (1, [1,2,3,4,5,6,7,8,9,10])")
print(chs.query('SELECT * FROM embeddings LIMIT 5'))
Behavior
Missing output on nobebook
Got stuck on some INSERT sql
Some guess
Clickhouse-local is using stdin as some input data src. But as this is chDB, stdin is not available for that.
Stack Trace
As we can see, read is trying to read data from fd 0, but from result of lsof
I got a wired problem while running chdb insert in local vscode jupyter notebook(not reproducing on Google Colab or raw python)
test_insert_vector.py
to comfirm raw python interpreter is not affected.I'll try to fix that after I finished #150 . No help needed, just open this issue in case I forget.
Code to reproduce:
Behavior
Some guess
Stack Trace
read
is trying to read data from fd 0, but from result oflsof
lsof output:
gdb attach the running jupyter kernel, got this:
The text was updated successfully, but these errors were encountered: