Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Expose the set of reserved CQL keywords

Open
#233 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python, rust
Domain
api, databases

Research direction

The payload names no file or test in this repository, so start by finding where the driver's Python-facing metadata API is defined and whether it already exposes any CQL grammar data. Compare with the reference the issue cites, cassandra.metadata.cql_keywords_reserved in the Python driver, to see what shape is expected. Settle first whether the maintainers want a raw set or a maybe_quote(name) helper, because that choice decides the work. Done means the chosen API returns the reserved words and a test checks a known reserved word such as order against it.

Written by the indexing model from the issue text.

Description

coodie (a Pydantic ODM for ScyllaDB) needs to know which CQL words are reserved, so it can quote table/keyspace/index names like order when it builds CQL.

scylla-driver and cassandra-driver expose this as cassandra.metadata.cql_keywords_reserved, kept in step with the server grammar. This driver has no equivalent, so coodie has to keep its own copy, which drifts when ScyllaDB adds a reserved word.

Could the driver expose the reserved-keyword set (or a maybe_quote(name) helper like the Python driver has)?

Context: https://github.com/scylladb/coodie/pull/308#discussion_r4238955177

Dominant language
Rust
Stars
6
Forks
8
Avg merge
5d 18h
Merged PRs (30d)
13

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scylladb/python-rs-driver

All issues in scylladb/python-rs-driver

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.