[ 
https://issues.apache.org/jira/browse/FLINK-18236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138945#comment-17138945
 ] 

jackylau commented on FLINK-18236:
----------------------------------

Hi [~rmetzger], Thanks . I found this from the page you attach.

*Pull requests belonging to unassigned Jira tickets or not authored by assignee 
will not be reviewed or merged by the community.*

And i am not searching through the code for a contribution opportunity. I found 
this, becasue i am working on elastcisearch source connector 
[https://cwiki.apache.org/confluence/display/FLINK/FLIP-127:+Support+Elasticsearch+Source+Connector].
 So I read the code carefully and found that.

> flink elasticsearch IT test ElasticsearchSinkTestBase.runElasticsearchSink* 
> verify it not right
> -----------------------------------------------------------------------------------------------
>
>                 Key: FLINK-18236
>                 URL: https://issues.apache.org/jira/browse/FLINK-18236
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / ElasticSearch
>    Affects Versions: 1.10.0
>            Reporter: jackylau
>            Assignee: jackylau
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> we can see there are diffirent tests
> runElasticsearchSinkTest
> runElasticsearchSinkCborTest
> runElasticsearchSinkSmileTest
> runElasticSearchSinkTest
> etc.
> And use SourceSinkDataTestKit.verifyProducedSinkData(client, index) to ensure 
> the correctness of results. But all of them use the same index.
> That is to say, if the second unit test sink doesn't send successfully. they 
> are also equal when use verifyProducedSinkData
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to