[jira] [Commented] (FLINK-2646) Rich functions should provide a method "closeAfterFailure()"
[
https://issues.apache.org/jira/browse/FLINK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742379#comment-14742379
]
chenliang commented on FLINK-2646:
--
1.Can you help me to quickly understand "The runtime is the changed to call
close() as part of the regular execution and closeAfterFailure() in case of an
irregular exit.".
2.Just i checked source code, the ChainedAllReduceDriver(one of runtime Driver)
already have cancelTask() method for irregular exit.
@Override
public void closeTask() throws Exception {
RegularPactTask.closeUserCode(this.reducer);
}
//chenliang613 remark: "RegularPactTask.closeUserCode(this.reducer)" also will
invoke "FunctionUtils.closeFunction(this.reducer)"
@Override
public void cancelTask() {
try {
FunctionUtils.closeFunction(this.reducer);
} catch (Throwable t) {
}
}
> Rich functions should provide a method "closeAfterFailure()"
>
>
> Key: FLINK-2646
> URL: https://issues.apache.org/jira/browse/FLINK-2646
> Project: Flink
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.10
>Reporter: Stephan Ewen
>Assignee: chenliang
> Fix For: 0.10
>
>
> Right now, the {{close()}} method of rich functions is invoked in case of
> proper completion, and in case of canceling in case of error (to allow for
> cleanup).
> In certain cases, the user function needs to know why it is closed, whether
> the task completed in a regular fashion, or was canceled/failed.
> I suggest to add a method {{closeAfterFailure()}} to the {{RichFunction}}. By
> default, this method calls {{close()}}. The runtime is the changed to call
> {{close()}} as part of the regular execution and {{closeAfterFailure()}} in
> case of an irregular exit.
> Because by default all cases call {{close()}} the change would not be API
> breaking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (FLINK-2646) Rich functions should provide a method "closeAfterFailure()"
[
https://issues.apache.org/jira/browse/FLINK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14742379#comment-14742379
]
chenliang edited comment on FLINK-2646 at 9/13/15 7:58 AM:
---
@Stephan Ewen
1.Can you help me to quickly understand "The runtime is the changed to call
close() as part of the regular execution and closeAfterFailure() in case of an
irregular exit.".
2.Just i checked source code, the ChainedAllReduceDriver(one of runtime Driver)
already have cancelTask() method for irregular exit.
@Override
public void closeTask() throws Exception {
RegularPactTask.closeUserCode(this.reducer);
}
//chenliang613 remark: "RegularPactTask.closeUserCode(this.reducer)" also will
invoke "FunctionUtils.closeFunction(this.reducer)"
@Override
public void cancelTask() {
try {
FunctionUtils.closeFunction(this.reducer);
} catch (Throwable t) {
}
}
was (Author: chenliang613):
1.Can you help me to quickly understand "The runtime is the changed to call
close() as part of the regular execution and closeAfterFailure() in case of an
irregular exit.".
2.Just i checked source code, the ChainedAllReduceDriver(one of runtime Driver)
already have cancelTask() method for irregular exit.
@Override
public void closeTask() throws Exception {
RegularPactTask.closeUserCode(this.reducer);
}
//chenliang613 remark: "RegularPactTask.closeUserCode(this.reducer)" also will
invoke "FunctionUtils.closeFunction(this.reducer)"
@Override
public void cancelTask() {
try {
FunctionUtils.closeFunction(this.reducer);
} catch (Throwable t) {
}
}
> Rich functions should provide a method "closeAfterFailure()"
>
>
> Key: FLINK-2646
> URL: https://issues.apache.org/jira/browse/FLINK-2646
> Project: Flink
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.10
>Reporter: Stephan Ewen
>Assignee: chenliang
> Fix For: 0.10
>
>
> Right now, the {{close()}} method of rich functions is invoked in case of
> proper completion, and in case of canceling in case of error (to allow for
> cleanup).
> In certain cases, the user function needs to know why it is closed, whether
> the task completed in a regular fashion, or was canceled/failed.
> I suggest to add a method {{closeAfterFailure()}} to the {{RichFunction}}. By
> default, this method calls {{close()}}. The runtime is the changed to call
> {{close()}} as part of the regular execution and {{closeAfterFailure()}} in
> case of an irregular exit.
> Because by default all cases call {{close()}} the change would not be API
> breaking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLINK-2646) Rich functions should provide a method "closeAfterFailure()"
[
https://issues.apache.org/jira/browse/FLINK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenliang updated FLINK-2646:
-
Description:
Right now, the {{close()}} method of rich functions is invoked in case of
proper completion, and in case of canceling in case of error (to allow for
cleanup).
In certain cases, the user function needs to know why it is closed, whether the
task completed in a regular fashion, or was canceled/failed.
I suggest to add a method {{closeAfterFailure()}} to the {{RichFunction}}. By
default, this method calls {{close()}}. The runtime is the changed to call
{{close()}} as part of the regular execution and {{closeAfterFailure()}} in
case of an irregular exit.
Because by default all cases call {{close()}} the change would not be API
breaking.
was:
Right now, the {{close()}} method of rich functions is invoked in case of
proper completion, and in case of canceling in case of error (to allow for
cleanup).
In certain cases, the user function needs to know why it is closed, whether the
task completed in a regular fashion, or was canceled/failed.
I suggest to add a method {{closeAfterFailure()}} to the {{RuchFunction}}. By
default, this method calls {{close()}}. The runtime is the changed to call
{{close()}} as part of the regular execution and {{closeAfterFailure()}} in
case of an irregular exit.
Because by default all cases call {{close()}} the change would not be API
breaking.
> Rich functions should provide a method "closeAfterFailure()"
>
>
> Key: FLINK-2646
> URL: https://issues.apache.org/jira/browse/FLINK-2646
> Project: Flink
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.10
>Reporter: Stephan Ewen
> Fix For: 0.10
>
>
> Right now, the {{close()}} method of rich functions is invoked in case of
> proper completion, and in case of canceling in case of error (to allow for
> cleanup).
> In certain cases, the user function needs to know why it is closed, whether
> the task completed in a regular fashion, or was canceled/failed.
> I suggest to add a method {{closeAfterFailure()}} to the {{RichFunction}}. By
> default, this method calls {{close()}}. The runtime is the changed to call
> {{close()}} as part of the regular execution and {{closeAfterFailure()}} in
> case of an irregular exit.
> Because by default all cases call {{close()}} the change would not be API
> breaking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FLINK-2646) Rich functions should provide a method "closeAfterFailure()"
[
https://issues.apache.org/jira/browse/FLINK-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenliang reassigned FLINK-2646:
Assignee: chenliang
> Rich functions should provide a method "closeAfterFailure()"
>
>
> Key: FLINK-2646
> URL: https://issues.apache.org/jira/browse/FLINK-2646
> Project: Flink
> Issue Type: Improvement
> Components: Core
>Affects Versions: 0.10
>Reporter: Stephan Ewen
>Assignee: chenliang
> Fix For: 0.10
>
>
> Right now, the {{close()}} method of rich functions is invoked in case of
> proper completion, and in case of canceling in case of error (to allow for
> cleanup).
> In certain cases, the user function needs to know why it is closed, whether
> the task completed in a regular fashion, or was canceled/failed.
> I suggest to add a method {{closeAfterFailure()}} to the {{RichFunction}}. By
> default, this method calls {{close()}}. The runtime is the changed to call
> {{close()}} as part of the regular execution and {{closeAfterFailure()}} in
> case of an irregular exit.
> Because by default all cases call {{close()}} the change would not be API
> breaking.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (FLINK-2493) Simplify names of example program JARs
[
https://issues.apache.org/jira/browse/FLINK-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenliang updated FLINK-2493:
-
Description:
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
was:
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
And combine flink-java-examples and flink-scala-examples project to one
examples project。
Simplify names of example program JARs
--
Key: FLINK-2493
URL: https://issues.apache.org/jira/browse/FLINK-2493
Project: Flink
Issue Type: Improvement
Components: Examples
Affects Versions: 0.10
Reporter: Stephan Ewen
Assignee: chenliang
Priority: Minor
Labels: easyfix, starter
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-2537) Add scala examples.jar to build-target/examples
[ https://issues.apache.org/jira/browse/FLINK-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14702673#comment-14702673 ] chenliang commented on FLINK-2537: -- any comments? i will go ahead to raise a PR for resolving this issue. Add scala examples.jar to build-target/examples --- Key: FLINK-2537 URL: https://issues.apache.org/jira/browse/FLINK-2537 Project: Flink Issue Type: Improvement Components: Examples Affects Versions: 0.10 Reporter: chenliang Assignee: chenliang Priority: Minor Labels: maven Fix For: 0.10 Currently Scala as functional programming language has been acknowledged by more and more developers, some starters may want to modify scala examples' code for further understanding flink mechanism. After changing scala code,they may select this method to check result: 1.go to build-target/bin start server 2.use web UI to upload scala examples' jar 3.this time they would get confusion, why changes would be not updated. Because build-target/examples only copy java examples, suggest adding scala examples also. The new directory would like this : build-target/examples/java build-target/examples/scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700014#comment-14700014 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700012#comment-14700012 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700017#comment-14700017 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Assignee: chenliang “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Assignee: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700023#comment-14700023 ] chenliang commented on FLINK-2367: -- ok, how about adding some note like this: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700013#comment-14700013 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-2537) Add scala examples.jar to build-target/examples
[ https://issues.apache.org/jira/browse/FLINK-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2537: - Labels: maven (was: ) Add scala examples.jar to build-target/examples --- Key: FLINK-2537 URL: https://issues.apache.org/jira/browse/FLINK-2537 Project: Flink Issue Type: Improvement Components: Examples Affects Versions: 0.10 Reporter: chenliang Assignee: chenliang Priority: Minor Labels: maven Fix For: 0.10 Currently Scala as functional programming language has been acknowledged by more and more developers, some starters may want to modify scala examples' code for further understanding flink mechanism. After changing scala code,they may select this method to check result: 1.go to build-target/bin start server 2.use web UI to upload scala examples' jar 3.this time they would get confusion, why changes would be not updated. Because build-target/examples only copy java examples, suggest adding scala examples also. The new directory would like this : build-target/examples/java build-target/examples/scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-2537) Add scala examples.jar to build-target/examples
[ https://issues.apache.org/jira/browse/FLINK-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2537: - Description: Currently Scala as functional programming language has been acknowledged by more and more developers, some starters may want to modify scala examples' code for further understanding flink mechanism. After changing scala code,they may select this method to check result: 1.go to build-target/bin start server 2.use web UI to upload scala examples' jar 3.this time they would get confusion, why changes would be not updated. Because build-target/examples only copy java examples, suggest adding scala examples also. The new directory would like this : build-target/examples/java build-target/examples/scala was: Currently Scala as functional programming language has been acknowledged by more and more developers, some starters may want to modify scala examples's code for further understanding flink mechanism. After changing scala code,they may select this method to check result: 1.go to build-target/bin start server 2.use web UI to upload scala examples' jar 3.this time they would get confusion, why changes would be not updated. Because build-target/examples only copy java examples, suggest adding scala examples also. The new directory would like this : build-target/examples/java build-target/examples/scala Add scala examples.jar to build-target/examples --- Key: FLINK-2537 URL: https://issues.apache.org/jira/browse/FLINK-2537 Project: Flink Issue Type: Improvement Components: Examples Affects Versions: 0.10 Reporter: chenliang Assignee: chenliang Priority: Minor Fix For: 0.10 Currently Scala as functional programming language has been acknowledged by more and more developers, some starters may want to modify scala examples' code for further understanding flink mechanism. After changing scala code,they may select this method to check result: 1.go to build-target/bin start server 2.use web UI to upload scala examples' jar 3.this time they would get confusion, why changes would be not updated. Because build-target/examples only copy java examples, suggest adding scala examples also. The new directory would like this : build-target/examples/java build-target/examples/scala -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700018#comment-14700018 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700016#comment-14700016 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14700015#comment-14700015 ] chenliang commented on FLINK-2367: -- ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: ok, your explanation looks reasonable. how about adding some note: log file deleted during runtime is not supported to be aware, this deletion operation belongs OS behavior, please manually check if the written log file still exists.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-2493) Simplify names of example program JARs
[
https://issues.apache.org/jira/browse/FLINK-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenliang updated FLINK-2493:
-
Description:
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
And combine flink-java-examples and flink-scala-examples project to one
examples project。
was:
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
Simplify names of example program JARs
--
Key: FLINK-2493
URL: https://issues.apache.org/jira/browse/FLINK-2493
Project: Flink
Issue Type: Improvement
Components: Examples
Affects Versions: 0.10
Reporter: Stephan Ewen
Assignee: chenliang
Priority: Minor
Labels: easyfix, starter
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
And combine flink-java-examples and flink-scala-examples project to one
examples project。
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (FLINK-2493) Simplify names of example program JARs
[
https://issues.apache.org/jira/browse/FLINK-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
chenliang reassigned FLINK-2493:
Assignee: chenliang
Simplify names of example program JARs
--
Key: FLINK-2493
URL: https://issues.apache.org/jira/browse/FLINK-2493
Project: Flink
Issue Type: Improvement
Components: Examples
Affects Versions: 0.10
Reporter: Stephan Ewen
Assignee: chenliang
Priority: Minor
Labels: easyfix, starter
I find the names of the example JARs a bit annoying.
Why not name the file {{examples/ConnectedComponents.jar}} rather than
{{examples/flink-java-examples-0.10-SNAPSHOT-ConnectedComponents.jar}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632148#comment-14632148 ] chenliang commented on FLINK-2367: -- one thing can do : When running jobs along with writing log info : this time ,the system could give some error message to remind: the log info can't be wrote effectively, please check your system log file “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Comment: was deleted (was: one thing can do : When running jobs along with writing log info : this time ,the system could give some error message to remind: the log info can't be wrote effectively, please check your system log file.) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632155#comment-14632155 ] chenliang commented on FLINK-2367: -- When running jobs: it would be better if the system could give the reminding info to remind: can't write log info effectively, please check your log file. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14632155#comment-14632155 ] chenliang edited comment on FLINK-2367 at 7/18/15 12:14 AM: When running jobs: it would be better if the system could give the error info to remind: can't write log info effectively, please check your log file. was (Author: chenliang613): When running jobs: it would be better if the system could give the reminding info to remind: can't write log info effectively, please check your log file. “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
[ https://issues.apache.org/jira/browse/FLINK-2367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] chenliang updated FLINK-2367: - Issue Type: Improvement (was: Bug) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete - Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Improvement Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Labels: reliability Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (FLINK-2367) “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete
chenliang created FLINK-2367: Summary: “flink-xx-jobmanager-linux-3lsu.log file can't auto be recovered/detected after mistaking delete Key: FLINK-2367 URL: https://issues.apache.org/jira/browse/FLINK-2367 Project: Flink Issue Type: Bug Components: JobManager Affects Versions: 0.9 Environment: Linux Reporter: chenliang Priority: Minor Fix For: 0.9.0 For checking system whether be adequately reliability, testers usually designedly do some delete operation. Steps: 1.go to flink\build-target\log 2.delete “flink-xx-jobmanager-linux-3lsu.log file 3.Run jobs along with writing log info, meanwhile the system didn't give any error info when the log info can't be wrote correctly. 4.when some jobs be run failed , go to check log file for finding the reason, can't find the log file. Must restart Job Manager to regenerate the log file, then continue to run jobs. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
