#268 reported that the types field add in data-loading/setup-and-load-solr.sh had malformed JSON — a missing comma between stored:true and multiValued:true — which Solr was silently 400-ing, so the field was never getting the intended definition.
main has since rewritten that script (#278, "Speed up and simplify Solr data loading"), so the bug may already be gone, may have been carried over, or may no longer apply if the schema now comes from the checked-in configset rather than runtime field adds.
Worth a quick check against current main: confirm whether the types field ends up with the intended stored/multiValued settings in a freshly loaded core, and fix if not. Silent 400s on schema setup are easy to miss.
#268 reported that the
typesfield add indata-loading/setup-and-load-solr.shhad malformed JSON — a missing comma betweenstored:trueandmultiValued:true— which Solr was silently 400-ing, so the field was never getting the intended definition.mainhas since rewritten that script (#278, "Speed up and simplify Solr data loading"), so the bug may already be gone, may have been carried over, or may no longer apply if the schema now comes from the checked-in configset rather than runtime field adds.Worth a quick check against current
main: confirm whether thetypesfield ends up with the intendedstored/multiValuedsettings in a freshly loaded core, and fix if not. Silent 400s on schema setup are easy to miss.