Man it's almost like there isn't an incentive to clearly and simply document open-source projects that are maintained largely by companies that profit from service contracts
This is handy. I find the documentation at the official website to often be severely lacking in many cases, so any additional resources are most welcome.
It blows my mind that they are actively opposed to supplying Javadocs. There is a 3-year issue regarding sharing documentation, with the only response along the lines of "just look at the source". The item was finally closed when other developers created servers to host the javadocs, though many of the method names don't have any documentation besides their method signature (ie method name, input types/names, and output)
There are $1600 2 day developer sessions concerning all things Elasticsearch offered by elastic.co . The cynic in me might assume that they give just enough documentation to let you know something is possible, but not enough for you to easily do so without the training. :)
Had to write a plugin to Elasticsearch recently. Was like a fun little hike into the source code without the documentation. On one hand, it could have been helpful. But on the other, I couldn't have learned a few internals of how ES works.
this is a great resource, wonder how the underlying docs.json is being created. would like to see it being extended to explain the query dsl.