[ 
https://issues.apache.org/jira/browse/BEAM-6361?focusedWorklogId=189846&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-189846
 ]

ASF GitHub Bot logged work on BEAM-6361:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jan/19 04:35
            Start Date: 25/Jan/19 04:35
    Worklog Time Spent: 10m 
      Work Description: ryan-williams commented on issue #7408: 
[BEAM-6361][BEAM-6364] fix user-metric-prefix checking in Flink portable 
metrics update
URL: https://github.com/apache/beam/pull/7408#issuecomment-457452816
 
 
   Looks like everything passed the second time around, so this should be good 
to go
   
   edit: Python_PVR_Flink is apparently still running, though github was 
showing me all checks as passed a moment ago
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 189846)
    Time Spent: 3h  (was: 2h 50m)

> Fix user-metric prefix detection for portable Flink metrics
> -----------------------------------------------------------
>
>                 Key: BEAM-6361
>                 URL: https://issues.apache.org/jira/browse/BEAM-6361
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>    Affects Versions: 2.9.0
>            Reporter: Ryan Williams
>            Assignee: Ryan Williams
>            Priority: Minor
>          Time Spent: 3h
>  Remaining Estimate: 0h
>
> [[email protected]] [noticed a 
> bug|https://github.com/apache/beam/pull/7183/files#r243402155] in classifying 
> portable Flink metrics as user-namespaced vs not.
> I think it's only currently affecting how metrics get displayed downstream in 
> Flink, but it should be fixed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to