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

Legacy QueryFilter, ScanFilter and KeyConditions: eight differences from DynamoDB

Abierto
  • ¿Algo no está bien?
#477 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 2 días

@LeeroyHannigan ya está trabajando en esto.

Desde el 24/10/2026.

  • #507 de @LeeroyHannigan — abierto

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, rust
Área
backend, database

Línea de trabajo

Start with the eight listed behavior differences and the related issues #108 and #399; item 5 points to crates/storage/src/util/key.rs. Re-measure each affected message against DynamoDB in us-east-1, then add wire tests under tests/ that run against the service and every backend. Done means all eight cases match the service's behavior, including BatchGetItem capacity output.

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

Descripción

These remain on the legacy condition paths after #399, which brings the operator, value count and type checks of QueryFilter, ScanFilter and KeyConditions to the service's rules and messages. Each one is present on main as well. Measured against Amazon DynamoDB in us-east-1 on 2026-10-23, on an empty table and on a table with items.

  1. Two legacy condition entries that are both invalid: the service names the second entry in map order, ExtendDB names the first.
  2. Query with a QueryFilter on a primary key attribute: the service refuses it (QueryFilter can only contain non-primary key attributes: Primary key attribute: pk), ExtendDB returns 200.
  3. ScanFilter EQ with an N AttributeValue whose value is not a number: the service reports the numeric conversion (The parameter cannot be converted to a numeric value: <value>), ExtendDB returns 200.
  4. ScanFilter BEGINS_WITH with an N AttributeValue whose value is not a number: the service reports the numeric conversion first, ExtendDB reports the operator against type message.
  5. KeyConditions on the sort key with a value whose type is valid for the operator but is not the schema type: the service refuses it with the schema type message, ExtendDB answers HTTP 500 (crates/storage/src/util/key.rs).
  6. KeyConditions EQ or BEGINS_WITH with an empty string: the service refuses it, ExtendDB returns 200.
  7. KeyConditions EQ on an S partition key with an N value: the service refuses it with the schema type message, ExtendDB returns 200.
  8. BatchGetItem with ReturnConsumedCapacity TOTAL where every key is absent: the service returns one entry per table, ExtendDB returns an empty list.

Items 5 to 7 are the most visible to a client: one is a 500, and two accept a request the service refuses. Each needs its message measured again when it is fixed, and a wire test under tests/ that runs against the service and every backend.

Related: #108 (the original list of error differences), #399.

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.