[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee updated FLINK-22585:
Fix Version/s: (was: 1.19.0)
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.20.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
lincoln lee updated FLINK-22585:
Fix Version/s: 1.20.0
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.19.0, 1.20.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jing Ge updated FLINK-22585:
Fix Version/s: 1.19.0
(was: 1.18.0)
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.19.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-22585:
-
Fix Version/s: 1.18.0
(was: 1.17.0)
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.18.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xingbo Huang updated FLINK-22585:
-
Fix Version/s: 1.17.0
(was: 1.16.0)
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.17.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yun Gao updated FLINK-22585:
Fix Version/s: 1.16.0
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.15.0, 1.16.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xintong Song updated FLINK-22585:
-
Fix Version/s: (was: 1.14.0)
1.15.0
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.15.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22585:
---
Labels: auto-unassigned pull-request-available stale-assigned (was:
auto-unassigned pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 30 days, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it.
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-assigned
> Fix For: 1.14.0
>
> Time Spent: 4h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-22585:
---
Labels: pull-request-available stale-assigned (was: stale-assigned)
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: pull-request-available, stale-assigned
> Fix For: 1.14.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-22585) Add deprecated message when "-m yarn-cluster" is used
[
https://issues.apache.org/jira/browse/FLINK-22585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-22585:
---
Labels: stale-assigned (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issue is assigned but has not
received an update in 14, so it has been labeled "stale-assigned".
If you are still working on the issue, please remove the label and add a
comment updating the community on your progress. If this issue is waiting on
feedback, please consider this a reminder to the committer/reviewer. Flink is a
very active project, and so we appreciate your patience.
If you are no longer working on the issue, please unassign yourself so someone
else may work on it. If the "warning_label" label is not removed in 7 days, the
issue will be automatically unassigned.
> Add deprecated message when "-m yarn-cluster" is used
> -
>
> Key: FLINK-22585
> URL: https://issues.apache.org/jira/browse/FLINK-22585
> Project: Flink
> Issue Type: Improvement
> Components: Deployment / YARN
>Reporter: Yang Wang
>Assignee: Rainie Li
>Priority: Major
> Labels: stale-assigned
> Fix For: 1.14.0
>
>
> The unified executor interface has been introduced for a long time, which
> could be activated by "\--target
> yarn-per-job/yarn-session/kubernetes-application". It is more descriptive and
> clearer. We should try to deprecate "-m yarn-cluster" and suggest our users
> to use the new CLI commands.
>
> However, AFAIK, many companies are using some CLI commands to integrate with
> their deployers. So we could not remove the "-m yarn-cluster" very soon.
> Maybe we could do it in the release 2.0 since we could do some breaking
> changes.
>
> For now, I suggest to add the {{@Deprecated}} annotation and printing a WARN
> log message when "-m yarn-cluster" is used. It is useful to let the users
> know the long-term goals and migrate asap.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
