[jira] [Created] (FLINK-35653) "fraud detection" example missed "env.execute" explanation

[Luke Chen (Jira)]

Luke Chen created FLINK-35653:
-

 Summary: "fraud detection" example missed "env.execute" explanation
 Key: FLINK-35653
 URL: https://issues.apache.org/jira/browse/FLINK-35653
 Project: Flink
  Issue Type: Bug
  Components: Documentation
Reporter: Luke Chen


In "try flink" page, there is a [fraud detection with the dataStream 
API|https://nightlies.apache.org/flink/flink-docs-master/docs/try-flink/datastream/]
 example to demo how to build a stateful streaming application with Flink’s 
DataStream API. In this page, we explained the code line by line, but missed 
the last line:
{code:java}
env.execute("Fraud Detection");{code}
 

I confirmed this was existed before 
[v1.12|https://github.com/apache/flink/blob/release-1.12/docs/try-flink/datastream_api.md?plain=1#L365],
 but when we migrated Flink docs from Jekyll to Hugo in this 
[PR|https://github.com/apache/flink/pull/14903], we missed that section. This 
miss will let first flink users miss the important line to execute the flink 
job.

 

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-36677) Instruct users to change log level dynamically in operator

[Luke Chen (Jira)]

Luke Chen created FLINK-36677:
-

 Summary: Instruct users to change log level dynamically in operator
 Key: FLINK-36677
 URL: https://issues.apache.org/jira/browse/FLINK-36677
 Project: Flink
  Issue Type: Improvement
Reporter: Luke Chen


In the 
[doc|https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/operations/metrics-logging/#logging],
 we didn't explicitly instruct users how to change log level dynamically for 
operator/job manager/task manager. This is important for troubleshooting.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)