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

glossary.md's "Operator" entry only covers PD scheduling; execution-plan "operator" is undocumented and possibly ambiguous

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
sql
Área
databases, documentation

Línea de trabajo

Empieza por glossary.md; luego compara la entrada Operator con el uso de operator en partitioned-table.md y en las páginas relacionadas con EXPLAIN. Traza ambos significados y comprueba si la documentación existente los distingue. Se considera terminado cuando haya una referencia cruzada clara en el glosario o una desambiguación para los operadores de planes de ejecución, o una decisión registrada de que el término compartido es intencional.

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

Descripción

What did you do?

While reviewing Japanese translation consistency for the term "operator" (see https://github.com/pingcap/docs/pull/23594), I found that glossary.md defines "Operator" strictly as a PD scheduling concept:

Operator

An operator is a collection of actions that applies to a Region for scheduling purposes. Operators perform scheduling tasks such as "migrate the leader of Region 2 to Store 5" and "migrate replicas of Region 2 to Store 1, 4, 5".

An operator can be computed and generated by a scheduler, or created by an external API.

However, the bare word "operator" is also used elsewhere in the docs for a completely different concept — a node/step in a query execution plan (e.g. TableScan, HashAgg, Exchange, IndexLookUp), for example in partitioned-table.md ("each operator supports direct access to multiple partitions") and throughout the EXPLAIN-related pages. This second sense has no glossary entry of its own and is not distinguished from the PD-scheduling sense anywhere in the docs.

What did you expect to see?

Either:

  • A separate glossary entry (or a disambiguation note on the existing "Operator" entry) for the execution-plan sense of "operator", so readers landing on the glossary from an EXPLAIN-related page aren't given an unrelated PD-scheduling definition, or
  • Confirmation that this overlap is intentional/acceptable, so translation teams (and future doc edits) know to keep treating both senses as the same term rather than trying to disambiguate them.

What did you see instead?

A single "Operator" glossary entry that only documents one of (at least) two distinct technical meanings the word carries elsewhere in the docs, with no cross-reference or disambiguation between them.

Additional context

This surfaced while normalizing the Japanese translation's katakana spelling for "operator" (オペレータ → オペレーター) across both PD-scheduling and execution-plan contexts. Since the English source itself doesn't distinguish the two senses, the Japanese translation currently mirrors that (uses the same term for both) — but it would help future translation/editing work to have an explicit answer on whether that's the intended approach.

Lenguaje dominante
Python
Estrellas
615
Forks
724
Merge medio
2 d 4 h
PR fusionados (30 d)
310

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 pingcap/docs

Todos los issues de pingcap/docs

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.