Pesky requirements But yep, you can't just use &wt=json...
In fact it sounds like no matter what you do you have to transform
things somehow...
You could _consider_ (and I'm not recommending, just being sure
you know it exists) writing a custom response writer. See
JSONResponseWriter for a m
Erick:
Thanks for your reply. Simply omitting the null fields is an intriguing
idea, and I will test this out.
Why not use the JSON response writer? Two reasons: our clients dictate a
particular JSON schema that changes on a query-by-query basis. The
schemas can be quite complex. Also, we rol
If I'm reading this right, you're kind of stuck. Solr/DIH don't have any
way to reach out to your mapping file and "do the right thing"
A couple of things come to mind.
Use a Transformer in DIH to simply remove the field from the document
you're indexing. Then the absence of the field in the r
Smart Folks:
I use JDBC to produce simple XML entities such as this one:
AWARDTYPE
0
31
1
awardtypes::31:1
The XML entities are stored in file and loaded by the
FileListEntityProcessor.
In this case, the "movie_id" element has a value of zero because the JDBC
getString("movie_id") m
