Specifying a schema (http/https) as part of a host definition will override the default port

[n0othing]

Tested on: logstash-filter-elasticsearch (3.6.0)

Defining a connection schema will override the default port (9200) for a given host.

Scenario: Elasticsearch node bound to loopback/localhost:

• hosts => ["localhost:9200"] - works
• hosts => ["localhost"] - works
• hosts => ["http://localhost"] - doesn't work

[yaauie]

I've filed a bug on the Elasticsearch Ruby Client (https://github.com/elastic/elasticsearch-ruby/issues/625), since their use of URI#parse is what is introducing the faulty defaults.

Since this project is pinned to 5.x I'm going to look into

• (a) what would it cost to fix upstream and upgrade us to absorb the fix VS
• (b) is this something that I can fix locally in a way that doesn't introduce more edge-cases