datafusion-contrib / datafusion-contrib/datafusion-distributed
fuzz with SQLancer
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 139
- Forks
- 67
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 35
Description
See https://github.com/datafusion-contrib/datafusion-distributed/pull/222
We can generate SQL queries using SQLancer https://github.com/datafusion-contrib/datafusion-sqlancer and verify the queries run correctly in distributed datafusion (see property-based validators added in https://github.com/datafusion-contrib/datafusion-distributed/pull/231)
There's some work to do
- Add arrow flight server for SQLancer to run on
- Intercept CREATE TABLE and INSERT statements and modify them so we write data to
testdata/sqlancer/data - Intercept SELECT statements and write them to
testdata/sqlancer/queries. Note that queries still need to be executed so SQLancer can use the data to generate more queries (ex. queries on the information scheam table for sure - unclear if it uses normal SELECT queries) - Data + queries = fuzz input. We run this input against distributed datafusion and validate using property based tests
- Intercept CREATE TABLE and INSERT statements and modify them so we write data to
- The instructions for sqlancer say to run it with java. We probably need to compile and save a linux sqlancer binary in this repo or in git lfs.
Note that sqlancer does not support nested queries and window functions at the time of writing.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing PRs 222 and 231, then inspect the SQLancer project and its Java execution instructions. Define the Arrow Flight server flow around CREATE TABLE, INSERT, and SELECT statements, using testdata/sqlancer/data and testdata/sqlancer/queries as the fuzz input. Done means SQLancer input can run against distributed DataFusion and be checked by the property-based validators, with a documented Linux SQLancer binary approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, rust, sql
- Domain
- distributed-systems, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100