splitgraph / seafowl

Analytical database for data-driven Web applications 🪶
https://seafowl.io
Apache License 2.0
388 stars 9 forks source link

It does not work #495

Open alexey-milovidov opened 5 months ago

alexey-milovidov commented 5 months ago

I'm following the tutorial: https://seafowl.io/docs/getting-started/quickstart

# Install

sudo apt-get update
sudo apt-get install -y docker.io

# Run

sudo docker run --rm -p 8080:8080 \
    -e SEAFOWL__FRONTEND__HTTP__WRITE_ACCESS=any \
    splitgraph/seafowl:nightly

curl -i -H "Content-Type: application/json" localhost:8080/q -d@- <<EOF
{"query": "CREATE EXTERNAL TABLE hits \
STORED AS PARQUET \
LOCATION 'https://clickhouse-public-datasets.s3.eu-central-1.amazonaws.com/hits_compatible/athena/hits.parquet'"}
EOF

curl -i -H "Content-Type: application/json" localhost:8080/q \
  -d '{"query": "CREATE TABLE hits AS SELECT * FROM staging.hits"}'

But for the last query, I'm getting

ubuntu@ip-172-31-38-111:~$ curl -i -H "Content-Type: application/json" localhost:8080/q \
  -d '{"query": "CREATE TABLE hits AS SELECT * FROM staging.hits"}'
curl: (52) Empty reply from server

The server logs are:

ubuntu@ip-172-31-38-111:~$ sudo docker run --rm -p 8080:8080     -e SEAFOWL__FRONTEND__HTTP__WRITE_ACCESS=any     splitgraph/seafowl:nightly
2024-02-02T01:28:56.038951Z  INFO main ThreadId(01) seafowl: Starting Seafowl 0.5.4
2024-02-02T01:28:56.039033Z  INFO main ThreadId(01) seafowl: Loading the configuration from /etc/seafowl/seafowl.toml
2024-02-02T01:28:56.081030Z  INFO main ThreadId(01) seafowl: Starting the HTTP frontend on 0.0.0.0:8080
2024-02-02T01:28:56.081039Z  INFO main ThreadId(01) seafowl: HTTP access settings: read any, write any
2024-02-02T01:29:12.556705Z  INFO tokio-runtime-worker ThreadId(185) seafowl::frontend::http: 172.17.0.1:55748 "POST /q HTTP/1.1" 200 "-" "curl/7.81.0" 453.610689ms    
thread 'tokio-runtime-worker' panicked at src/object_store/cache.rs:241:60:
called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "No such file or directory" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace