[ 
https://issues.apache.org/jira/browse/BEAM-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Etienne Chauchot updated BEAM-6030:
-----------------------------------
    Description: 
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.

  was:
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 
PipelineOptionsGraphiteMetrics interfaces to avoid having technology specific 
methods in base classes/interfaces.


> Remove Graphite Metrics Sink specific methods from PipelineOptions
> ------------------------------------------------------------------
>
>                 Key: BEAM-6030
>                 URL: https://issues.apache.org/jira/browse/BEAM-6030
>             Project: Beam
>          Issue Type: Improvement
>          Components: beam-model
>    Affects Versions: 2.8.0
>            Reporter: Federico Mendez
>            Assignee: Etienne Chauchot
>            Priority: Critical
>             Fix For: 2.10.0
>
>
> 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)

Reply via email to