Skip to content

Conversation

@lamberken
Copy link
Member

What is the purpose of the change

fix error http port in elasticsearch scala doc.
http port is 9200, not 9300

Copy link
Contributor

@yanghua yanghua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lamber-ken Thanks for your contribution. LGTM. The Kafka connector test timeout caused the travis failure. You can open a JIRA issue for that and rebuild your PR.

@lamberken
Copy link
Member Author

@yanghua, thanks for reviews. I'll use the git command which you teached before to rebuild pr 😄

@zentol
Copy link
Contributor

zentol commented Dec 26, 2018

@yanghua I've told you this before, don't rerun Travis for documentation changes. This is a completely unnecessary waste of resources.

@zentol
Copy link
Contributor

zentol commented Dec 26, 2018

Please provide a source for 9200 being the correct port.

@lamberken
Copy link
Member Author

@yanghua I've told you this before, don't rerun Travis for documentation changes. This is a completely unnecessary waste of resources.

sorry, I see.

@yanghua
Copy link
Contributor

yanghua commented Dec 26, 2018

@zentol Sorry, I thought that if Travis turns green, it will make it easier for committer to merge PR, otherwise, they will need to confirm why it failed. And I have asked @lamber-ken to report this failed case to JIRA instead of ignoring it. Then next time I will not make this suggestion.

@lamberken
Copy link
Member Author

lamberken commented Dec 26, 2018

Please provide a source for 9200 being the correct port.

hi, @zentol, here is official elasticsearch source doc, from official doc, we can konw default http is 9200, and give us a complete example

@tzulitai
Copy link
Contributor

tzulitai commented Jan 7, 2019

Can confirm, 9200 is the correct port for the REST-based Elasticsearch 6.x connector.
9300 is for the older Elasticsearch transport client used in 5.x versions and below of the connector.

LGTM, will merge this ...

One suggestion: it would have been easier to confirm this if the PR stated that the docs were incorrect only for the 6.x connector.

@asfgit asfgit closed this in 3d5b6b1 Jan 7, 2019
@lamberken
Copy link
Member Author

Can confirm, 9200 is the correct port for the REST-based Elasticsearch 6.x connector.
9300 is for the older Elasticsearch transport client used in 5.x versions and below of the connector.

LGTM, will merge this ...

One suggestion: it would have been easier to confirm this if the PR stated that the docs were incorrect only for the 6.x connector.

Ok

tisonkun pushed a commit to tisonkun/flink that referenced this pull request Jan 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants