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

SPIKE: Discuss ways in which callers can indicated to not to auto-delete statements upon completion + cursor close()

Open
  • Is something wrong?
#79 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
databases

Research direction

No files, tests, or entry points are named. Start by reviewing the current statement cleanup and cursor close behavior, then compare it with the described CCloud Flink behavior. Done means documenting a decided way for callers to prevent automatic deletion, including the expected completed-statement lifecycle.

Written by the indexing model from the issue text.

Description

Aggressively deleting statements when they're completed and the cursor is closed may not be everyone's cup of tea, esp. if they're used to CCloud Flink behavior of the entire trail of completed statements by default.

Dominant language
Python
Stars
6
Forks
1
Avg merge
1d 2h
Merged PRs (30d)
15

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 confluentinc/confluent-sql

All issues in confluentinc/confluent-sql

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.