[
https://issues.apache.org/jira/browse/BEAM-6030?focusedWorklogId=180741&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-180741
]
ASF GitHub Bot logged work on BEAM-6030:
----------------------------------------
Author: ASF GitHub Bot
Created on: 03/Jan/19 15:19
Start Date: 03/Jan/19 15:19
Worklog Time Spent: 10m
Work Description: echauchot commented on issue #7400: [BEAM-6030] Split
metrics related options out of PipelineOptions
URL: https://github.com/apache/beam/pull/7400#issuecomment-451173906
Yes, all metrics are labeled Experimental but it is true that metrics
options themselves are not labeled. Nevertheless, metrics options have not
changed they have only been moved to MetricsOptions. As MetricsOptions extends
PipelineOptions and as they are CLI parameters, all these options will be
visible all together to the user. So how can it be a breaking change ? Do I
miss something ?
----------------------------------------------------------------
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: 180741)
Time Spent: 0.5h (was: 20m)
> Remove Metrics Sinks specific methods from PipelineOptions
> ----------------------------------------------------------
>
> Key: BEAM-6030
> URL: https://issues.apache.org/jira/browse/BEAM-6030
> Project: Beam
> Issue Type: Improvement
> Components: sdk-java-core
> Affects Versions: 2.8.0
> Reporter: Federico Mendez
> Assignee: Etienne Chauchot
> Priority: Critical
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> https://issues.apache.org/jira/browse/BEAM-4553 introduced methods in the
> base PipelineOptions interfaces that are specific to Graphite
> get/setMetricsGraphiteHost and get/setMetricsGraphitePort.
> I'd suggest to those elements should be moved to a
> PipelineOptionsGraphiteMetricsSink interfaces to avoid having technology
> specific methods in base classes/interfaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
