To respond to your last question Yonik, the "fl" in the query params
behaves the same as the "fl" in the JSON params block, so no bug there.
There is a difference though, between those and the top level "fields"
param, as Jack pointed out it appends to the defaults instead of overriding
them like
Yonik? The doc is weak in this area. In fact, I see a comment on it from
Cassandra directed to you to verify the JSON to parameter mapping. It would
be nice to have a clear statement of the semantics for JSON "fields"
parameter and how it may or may not interact with the Solr fl parameter.
--
Multiple "fl" parameters are additive, so it would make sense that
"fields" is also (for fl and field in the same request). If that's
true for "fl" as a default and "fl" as a query param, then it seems
like that should be true for the other variants.
If "fl" as a query param and "fl" in a JSON
In a normal query multiple fl parameters are additive, but they
collectively override whatever fl parameter(s) may have been specified in
"defaults", right? I mean, that's why Solr has "appends" in addition to
"defaults", right"?
Ah, but I see in the JSON Request API doc that it says
