PutSolrContentStream SolrLocation property: parameter vs. attribute I moved a working flow that is populating Solr indexes from one process group to another. In the original, the SolrLocation property of the PutSolrContentStream processor is populated using two parameters:#{solr_url}/#{solr_index_name_a}It's done this way because a QueryRecord processor is used to split the record set into two groups, and one path uses the "a" index, and the other, the "b" index. However, in the new flow, I have to append a year value (i.e., "2023") to the name of the index depending on earlier processing. To accomplish this, I am holding the name of the index in an attribute instead of a parameter. At the appropriate time in the flow, I use an UpdateAttribute processor to append the correct year to the index name. Then further down, I have the PutSolrContentStream processor, and I populate the SolrLocation property like this:#{solr_url}/${solr_index_name_a}This fails with an "HTTP ERROR 404 NOT FOUND". It took a lot of trial an error, but I have discovered if I h
