scylladb / scylladb/python-rs-driver
Named execution profile
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 7
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 9
Description
Old Python Driver accepts a map (key: str, value: ExecutionProfile) with execution profiles.
User can then set profile on a statement using either a name from this map, or ExecutionProfile object (doesn't have to be present in the map).
Default execution profile is taken from a 'EXEC_PROFILE_DEFAULT' key in this map - I'm not a big fan of this. I do however think that the map approach is nice to use - no need to pass profile objects around.
We should consider doing something similar.
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
No source file, test, or entry point is named. Begin by locating the current execution-profile and statement APIs in the Rust driver and compare them with the old Python Driver's named-profile behavior; done should be a settled design and scope for storing, selecting, and defaulting profiles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100