duckdb / duckdb/duckdb-httpfs

Allowing relative paths

Open
#14 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
60
Forks
100
Avg merge
1h 50m
Merged PRs (30d)
25

Description

Hi!,
I use duckdb-wasm and it works well when I read a parquet file with a complete URL. But if I want to use relative file paths, it doesn't work. Probably because this extension checks whether the filepath in read_parquet('./data.parquet') starts with "http". Is there a workaround?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing read_parquet('./data.parquet') in duckdb-wasm and compare it with a complete URL. Trace how the extension handles the filepath check for relative paths. Done means relative parquet paths work in duckdb-wasm without breaking complete URLs.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, wasm
Domain
databases, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.