NordicHPC / NordicHPC/slurm2sql
Commandline Argument for DuckDB as Output format
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 19
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I needed DuckDB as a database because it is much faster. Simply connecting to the SQLite database through DuckDB didn’t work, it was actually slower than SQLite itself.
At first, I wrote a script to convert the Sqlite to DuckDB, but that was wasting too much memory on the Sqlite Database. So I forked slurm2sql and built a DuckDB integration with the --duckdb command-line argument to output a DuckDB directly. If you’re interested in merging it into the main repo, let me know.
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
The issue mentions a proposed --duckdb command-line argument and an existing fork, but names no files, tests, or entry points. Start by locating the command-line argument handling and output-database code, then compare the fork's integration; done means DuckDB output works through the command-line option without the reported SQLite conversion overhead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, database
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100