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

Weijie Guo updated FLINK-33493:
-------------------------------
    Fix Version/s: elasticsearch-3.1.0

> Elasticsearch connector ElasticsearchWriterITCase test failed
> -------------------------------------------------------------
>
>                 Key: FLINK-33493
>                 URL: https://issues.apache.org/jira/browse/FLINK-33493
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / ElasticSearch
>            Reporter: Yuxin Tan
>            Assignee: Yuxin Tan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: elasticsearch-3.1.0
>
>
> When I ran tests, the test failed. The failed reason is
> {code:java}
> Error:  
> /home/runner/work/flink-connector-elasticsearch/flink-connector-elasticsearch/flink-connector-elasticsearch-base/src/test/java/org/apache/flink/connector/elasticsearch/sink/ElasticsearchWriterITCase.java:[197,46]
>  cannot find symbol
>   symbol:   method 
> mock(org.apache.flink.metrics.MetricGroup,org.apache.flink.metrics.groups.OperatorIOMetricGroup)
>   location: class 
> org.apache.flink.runtime.metrics.groups.InternalSinkWriterMetricGroup
> Error:  
> /home/runner/work/flink-connector-elasticsearch/flink-connector-elasticsearch/flink-connector-elasticsearch-base/src/test/java/org/apache/flink/connector/elasticsearch/sink/ElasticsearchWriterITCase.java:[273,46]
>  cannot find symbol
>   symbol:   method mock(org.apache.flink.metrics.MetricGroup)
> {code}
> https://github.com/apache/flink-connector-elasticsearch/actions/runs/6809899863/job/18517273714?pr=77#step:13:134.
> ElasticsearchWriterITCase called Flink "InternalSinkWriterMetricGroup#mock", 
> and it is renamed in https://github.com/apache/flink/pull/23541 
> ([FLINK-33295|https://issues.apache.org/jira/browse/FLINK-33295] in Flink 
> 1.19). So the test failed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to