support connecting to lance files in an S3 bucket
Nobody has claimed this yet.
- #71 by @dentiny — closed without merging
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the code that currently accepts a filesystem path and mounts or opens the Lance table in the web UI. Trace how an S3 URI could enter that path, then identify the existing checks or tests for local paths. Done means the viewer can open a Lance file from S3 as well as from the local filesystem.
Written by the indexing model from the issue text.
Description
Thanks for a great tool. Could you envisage this working against an S3 URI as well as a filesystem path, as currently implemented?
- Dominant language
- Python
- Stars
- 65
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lance-format/lance-data-viewer
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
lance-format/lance-data-viewer#89 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in lance-format/lance-data-viewer
Similar issues
-
Validate non-divisible effective batch sizes in the Unsloth LoRA backendPossibly taken @debesh-biswas claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
`rx.Model` event arguments emit `PydanticDeprecatedSince20` once per payload keyPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
reflex-dev/reflex#7634 · 1 comment ·
Maintainers usually reply within 2 days
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
topoteretes/cognee#6239 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ranaroussi/yfinance#3009 ·
Maintainers usually reply within 1 day
-
Test discovery aborts on GPU builds without cuStateVec: check_cuStateVec expects a failed result but set_config() now raises RuntimeErrorPossibly taken @dmeliksetian claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Qiskit/qiskit-aer#2495 ·
Maintainers usually reply within 1 day