datafusion-contrib / datafusion-contrib/liquid-cache
Create JOB benchmark
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 452
- Forks
- 51
- Avg merge
- 3h 10m
- Merged PRs (30d)
- 12
Description
JOB (join order benchmark) is a good benchmark with real data.
We don't care about join order here, but we want the real data with filters.
The end goal for this issue is two parts:
- Find a way to automatically set up the data necessary for job, in parquet format.
- Generate queries based on the queries in job.
More specifically,
- download imdb dataset, convert it into parquet format. this should be done using a simple script.
- To generate queries:
Given a query from job:
SELECT MIN(t.title) AS movie_title
FROM company_name AS cn,
keyword AS k,
movie_companies AS mc,
movie_keyword AS mk,
title AS t
WHERE cn.country_code ='[sm]'
AND k.keyword ='character-name-in-title'
AND cn.id = mc.company_id
AND mc.movie_id = t.id
AND t.id = mk.movie_id
AND mk.keyword_id = k.id
AND mc.movie_id = mk.movie_id;
We'd like to remove all unrelated queries nodes and make it into simple:
SELECT cn.country_code, k.keyword
FROM company_name AS cn,
keyword AS k,
WHERE cn.country_code ='[sm]'
AND k.keyword ='character-name-in-title';
Finally, we'd like to run the query and data in the ci.
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 with the linked IMDb dataset and the JOB SQL queries; identify the repository's existing approach for scripts, Parquet data, and CI. Done means an automated setup produces the required Parquet data, generates simplified filter queries from JOB, and runs the resulting queries and data in CI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- data-engineering, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100