Expose a named variant of `join_core` (mirroring `arrange_named`) for operator-level profiling
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- observability
Research direction
Start with operators/join.rs:81 and compare its join_core implementation with arrange_named and arrange_core(name). Add the named join entry point while preserving join_core's default "Join" label, then verify that joins report distinct names in OperatesEvent and that existing behavior remains unchanged.
Written by the indexing model from the issue text.
Description
Hi all, I noticed that arrangements can be given custom operator names via arrange_named / arrange_core(name), which is really helpful for identifying them in logging and profiling streams.
Joins don’t seem to have an equivalent right now: join_core hardcodes the operator name as "Join" (operators/join.rs:81), so every join shows up with the same name in OperatesEvent, making it hard to distinguish them in dataflows with many joins.
Would you be open to adding a named variant, e.g. join_core_named(other, name, logic), with join_core delegating to it using "Join"? It seems like a small backward-compatible change that mirrors arrange_named, and it would make profiling/debugging much easier.
- Dominant language
- Rust
- Stars
- 3k
- Forks
- 211
- Avg merge
- 10h 42m
- Merged PRs (30d)
- 34
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TimelyDataflow/differential-dataflow
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
TimelyDataflow/differential-dataflow#181 · 1 comment ·
-
build-failure
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
TimelyDataflow/differential-dataflow#742 · 15 comments · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 38/100
TimelyDataflow/differential-dataflow#716 · 1 comment · 1 reaction ·
All issues in TimelyDataflow/differential-dataflow
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#610 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
gitbutlerapp/gitbutler#15998 · 1 comment ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100