Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

ListTagsOfResource on a stream ARN after its table is deleted answers ResourceNotFoundException; DynamoDB serves the stream's tags

未关闭
#607 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 4 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
62/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
postgresql, rust
领域
backend, databases

调研方向

Start by reading validate_resource_arn and the ListTagsOfResource path; the issue says validation reads the table on all four backends and identifies PostgreSQL at the head of #599. Compare the behavior for a deleted table's stream ARN with the retained tag rows and the reported DynamoDB response. Done means the call returns the stream's tags after table deletion while nonexistent-stream behavior remains consistent with #452.

由索引模型根据 Issue 内容生成。

描述

bug

Summary

After a table is deleted, Amazon DynamoDB still answers ListTagsOfResource on the table's stream ARN with 200 and the stream's tags. ExtendDB answers 400 ResourceNotFoundException, because the tag path requires the table to exist.

Measured (us-east-1, 2026-10-26, 3 of 3)

Table with a stream; TagResource on LatestStreamArn with sk and sk2; DeleteTable; after DescribeTable answers ResourceNotFoundException: ListTagsOfResource {ResourceArn: <stream ARN>} answers 200 {Tags: [sk2]} (an UntagResource of sk sent during the delete had been applied).

ExtendDB on PostgreSQL at the head of #599: ResourceNotFoundException Requested resource not found: ResourceArn: <stream ARN> not found. validate_resource_arn reads the table on all four backends.

Notes

The stream-ARN tag rows themselves are kept across the table's delete on every backend (no delete path removes them), which matches the service; only the read refuses. Related: #452 (a stream ARN for a stream that does not exist) and #518 (streams stay describable after the table is gone).

主要语言
Rust
星标
517
派生
60
平均合并
4 天 22 小时
30 天内合并 PR
40

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ExtendDB/extenddb 的其他 Issue

查看 ExtendDB/extenddb 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。