[
https://issues.apache.org/jira/browse/FLINK-34289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17815532#comment-17815532
]
Piotr Nowojski edited comment on FLINK-34289 at 2/8/24 6:33 AM:
----------------------------------------------------------------
!Screenshot 2024-02-08 at 07.22.19.png|width=600!
This part was confusing to me. My thought process was:
# Ok first box says, I should create a *new* ticket.
# But following the arrow, I should *remove* "Instructions". That's slightly
suggested to rename the ticket.
# The truly confusing part. The box on the right, shows an arrow from "X
Instructions: Verify" to "X: Verify". I've interpreted it as a subtask issue
first, supporting "create new ticket" interpretation. But I couldn't create
sub-task. So maybe that arrow is supposed to represent action of renaming thet
ticket?
# I've checked that in FLINK-34285 someone else has already renamed ticket by
removing "Instructions" so that further supported my interpretation that I
should rename it as well.
Rephrasing the instruction to clarify the meaning of {{remove "Instructions"}}
and labeling the arrow between "Instructions" and non "Instructions" tickets,
to state that for example it represents a linked ticket would help me avoid
this mistake.
was (Author: pnowojski):
!Screenshot 2024-02-08 at 07.22.19.png!
This part was confusing to me. My thought process was:
# Ok first box says, I should create a *new* ticket.
# But following the arrow, I should *remove* "Instructions". That's slightly
suggested to rename the ticket.
# The truly confusing part. The box on the right, shows an arrow from "X
Instructions: Verify" to "X: Verify". I've interpreted it as a subtask issue
first, supporting "create new ticket" interpretation. But I couldn't create
sub-task. So maybe that arrow is supposed to represent action of renaming thet
ticket?
# I've checked that in FLINK-34285 someone else has already renamed ticket by
removing "Instructions" so that further supported my interpretation that I
should rename it as well.
Rephrasing the instruction to clarify the meaning of {{remove "Instructions"}}
and labeling the arrow between "Instructions" and non "Instructions" tickets,
to state that for example it represents a linked ticket would help me avoid
this mistake.
> Release Testing Instructions: Verify FLINK-33695 Introduce TraceReporter and
> use it to create checkpointing and recovery traces
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-34289
> URL: https://issues.apache.org/jira/browse/FLINK-34289
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics
> Affects Versions: 1.19.0
> Reporter: lincoln lee
> Assignee: Piotr Nowojski
> Priority: Blocker
> Fix For: 1.19.0
>
> Attachments: Screenshot 2024-02-08 at 07.22.19.png, screenshot-1.png
>
>
> This ticket covers testing three related features: FLINK-33695, FLINK-33735
> and FLINK-33696.
> Instructions:
> # Configure Flink to use
> [Slf4jTraceReporter|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/trace_reporters/#slf4j]
> and with enabled *INFO* level logging (can be to console or to a file,
> doesn't matter).
> # Start a streaming job with enabled checkpointing.
> # Let it run for a couple of checkpoints.
> # Verify presence of a single *JobInitialization* [1] trace logged just after
> job start up.
> # Verify presence of a couple of *Checkpoint* [1] traces logged after each
> successful or failed checkpoint.
> [1]
> https://nightlies.apache.org/flink/flink-docs-master/docs/ops/traces/#checkpointing-and-initialization
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
