Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

A disabled stream of a deleted table stays describable on the service

Abierto
  • ¿Algo no está bien?
#518 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
cassandra, mongodb, postgresql, rust, sqlite
Área
backend-api-design, databases

Línea de trabajo

Start by reviewing the stream handling for DescribeStream, ListStreams, GetShardIterator, and GetRecords, then compare how SQLite, PostgreSQL, MongoDB, and Cassandra delete table shard rows. Check PostgreSQL's cleanup_orphaned_stream_shards and the documented 24 hour retention behavior. Done means deleted-table streams remain resolvable through that retention period and are removed by cleanup afterward, with TableName and KeySchema available after the table row is gone.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug

Summary

On the service a stream whose table has been deleted stays describable and listed. Measured 2026-10-24: a table's stream disabled, then the table deleted and gone from DescribeTable; 10 s and 20 s later DescribeStream on the old ARN answers 200 with StreamStatus DISABLED and its four shards, and ListStreams TableName=<deleted table> lists the one stream. The service documents a 24 hour retention for stream data. On ExtendDB every backend removes the shard rows with the table (SQLite and PostgreSQL by cascade, MongoDB and Cassandra in the delete path), so the ARN stops resolving at DeleteTable; the same is true for an enabled stream of a deleted table.

Fix shape

Keep a deleted table's shard and record rows until the retention sweep removes them (PostgreSQL already has cleanup_orphaned_stream_shards, which removes a deleted table's shards once no records remain; the other three drop them with the table), and let DescribeStream, ListStreams, GetShardIterator and GetRecords resolve a stream whose table row is gone through the stream's own table id and the account's shard rows. The stream's TableName and KeySchema would have to be kept with the shards or in a small stream row, since the table row is gone. A design question, not a one-line change; filed so the divergence is recorded.

Found while reviewing #515.

Lenguaje dominante
Rust
Estrellas
517
Forks
60
Merge medio
2 d 23 h
PR fusionados (30 d)
25

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ExtendDB/extenddb

Todos los issues de ExtendDB/extenddb

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.