[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weijie Guo updated FLINK-7957:
--
Labels: 2.0-related auto-deprioritized-minor auto-unassigned (was:
auto-deprioritized-minor auto-unassigned)
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Not a Priority
> Labels: 2.0-related, auto-deprioritized-minor, auto-unassigned
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-7957:
Parent: FLINK-32378
Issue Type: Sub-task (was: Improvement)
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Not a Priority
> Labels: auto-deprioritized-minor, auto-unassigned
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7957:
--
Labels: auto-deprioritized-minor auto-unassigned (was: auto-unassigned
stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Not a Priority
> Labels: auto-deprioritized-minor, auto-unassigned
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7957:
--
Labels: auto-unassigned stale-minor (was: auto-unassigned)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Priority: Minor
> Labels: auto-unassigned, stale-minor
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7957:
--
Labels: auto-unassigned (was: stale-assigned)
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Minor
> Labels: auto-unassigned
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7957:
--
Labels: stale-assigned (was: )
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Minor
> Labels: stale-assigned
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Knauf updated FLINK-7957:
Priority: Minor (was: Trivial)
In https://issues.apache.org/jira/browse/FLINK-22028 the "Trivial" priority
will be dropped. Therefore I changed the priority of this ticket to Minor.
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Minor
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup>)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-7957:
Fix Version/s: (was: 1.5.0)
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
>Priority: Trivial
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (FLINK-7957) Add MetricGroup#getLogicalScope
[
https://issues.apache.org/jira/browse/FLINK-7957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler updated FLINK-7957:
Fix Version/s: (was: 1.4.0)
1.5.0
> Add MetricGroup#getLogicalScope
> ---
>
> Key: FLINK-7957
> URL: https://issues.apache.org/jira/browse/FLINK-7957
> Project: Flink
> Issue Type: Improvement
> Components: Metrics
>Affects Versions: 1.4.0
>Reporter: Chesnay Schepler
>Assignee: Chesnay Schepler
> Fix For: 1.5.0
>
>
> Various reporters make use of a generalized scope string (e.g.
> "taskmanager.job.task."). This string can be generated with
> {{AbstractMetricGroup#getLogicalScope}}, which is however an internal API. As
> a result, the access pattern currently looks like this:
> {code}
> ((FrontMetricGroup)group).getLogicalScope(CHARACTER_FILTER,
> '.')
> {code}
> Given the wide-spread of this kind of scope i propose to move it into the
> MetricGroup interface.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
