Add max_es_version to more clearly indicate that Kibana 4.1.x should not be used with ES 2.x

[tbragin]

When you point Kibana 4.1.2 to ES 2.0, user sees an unknown error:

_{"name":"Kibana","hostname":"tatianium","pid":10957,"level":50,"err":{"message":"unknown error","name":"Error","stack":"Error: unknown error\n at respond (/Users/tanya/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:237:15)\n at checkRespForFailure (/Users/tanya/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/transport.js:203:7)\n at HttpConnector. (/Users/tanya/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/src/lib/connectors/http.js:156:7)\n at IncomingMessage.bound (/Users/tanya/kibana-4.1.2-darwin-x64/src/node_modules/elasticsearch/node_modules/lodash-node/modern/internals/baseBind.js:56:17)\n at IncomingMessage.emit (events.js:117:20)\n at _stream_readable.js:944:16\n at process.tickCallback (node.js:442:13)"},"msg":"","time":"2015-10-13T04:36:45.294Z","v":0}

We already have a min_es_version constant, so this enhancement is to add a max_es_version to handle cases like this.

[djvidov]

Hello,
I have almost the same error.
I have use it on W7 with ES 2.0 + kibana v4.1.2 (yesterday) or kibana v4.1.3 (today).

The full error is:
{
"name": "Kibana",
"hostname": "DV01LPT709",
"pid": 11004,
"level": 50,
"err": {
"message": "unknown error",
"name": "Error",
"stack": "Error: unknown error\n at respond (C
:\Users\mu32hv\Downloads\kibana-4.1.3-windows\src\node_modules\elasticsea
rch\src\lib\transport.js:237:15)\n at checkRespForFailure (C:\Users\mu32
hv\Downloads\kibana-4.1.3-windows\src\node_modules\elasticsearch\src\lib
\transport.js:203:7)\n at HttpConnector. (C:\Users\mu32hv\Downl
oads\kibana-4.1.3-windows\src\node_modules\elasticsearch\src\lib\connecto
rs\http.js:156:7)\n at IncomingMessage.bound (C:\Users\mu32hv\Downloads
kibana-4.1.3-windows\src\node_modules\elasticsearch\node_modules\lodash-nod
e\modern\internals\baseBind.js:56:17)\n at IncomingMessage.emit (events.js
:117:20)\n at _stream_readable.js:944:16\n at process._tickCallback (node.
js:442:13)"
},
"msg": "",
"time": "2015-11-17T09:15:44.800Z",
"v": 0
}{
"name": "Kibana",
"hostname": "DV01LPT709",
"pid": 11004,
"level": 60,
"err": {
"message": "unknown error",
"name": "Error",
"stack": "Error: unknown error\n at respond (C
:\Users\mu32hv\Downloads\kibana-4.1.3-windows\src\node_modules\elasticsea
rch\src\lib\transport.js:237:15)\n at checkRespForFailure (C:\Users\mu32
hv\Downloads\kibana-4.1.3-windows\src\node_modules\elasticsearch\src\lib
\transport.js:203:7)\n at HttpConnector. (C:\Users\mu32hv\Downl
oads\kibana-4.1.3-windows\src\node_modules\elasticsearch\src\lib\connecto
rs\http.js:156:7)\n at IncomingMessage.bound (C:\Users\mu32hv\Downloads
kibana-4.1.3-windows\src\node_modules\elasticsearch\node_modules\lodash-nod
e\modern\internals\baseBind.js:56:17)\n at IncomingMessage.emit (events.js
:117:20)\n at _stream_readable.js:944:16\n at process._tickCallback (node.
js:442:13)"
},
"msg": "",
"time": "2015-11-17T09:15:44.800Z",
"v": 0
}

[tbragin]

@djvidov Kibana 4.1.x is not supported with ES 2.0, which is why we opened this issue to make the error message more explicit. Please feel free to use Kibana 4.2 with ES 2.0.

[djvidov]

yes you're right, Thank you!

[w33ble]

Closed via #5576