I guess I see where _source is coming from, matching the result of the search.
Only as I formulate the set of options for the search, I'm following the elasticsearch documentation on the search options, thus the impedance mismatch.
So I suppose it's a matter of taste, but if it was consistently named the ES documentation (or better documented in the search docstring), then it would have saved a failed program run.
What do you think about the practice of providing documentation and keyword declarations for all Elastisch supported SearchRequest options
(in clojurewerkz.elastisch.native.conversion/->search-request) in the
clojurewerkz.elastisch.native.document/search function docstring, so that they're available when people are coding search calls?
[If only clojure had an option to enforce keyword parameters vs. actual arguments at compile time that would benefit hoisting keywords even further, but generic map destructuring
doesn't provide that].
Just curious. You can tell I have documentation intensive leanings. I'm just wondering whether trivial pull requests along those
lines might welcome.