[
https://issues.apache.org/jira/browse/SOLR-17263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17846037#comment-17846037
]
James Dyer commented on SOLR-17263:
-----------------------------------
[~andywebb1975] I think you'd be safe following the pattern with SOLR-17261 and
add your commit three places: *main*, *branch_9x* and *branch_9_6*. The
CHANGES.txt entry would go under 9_7_0 in the two branches, and under 9_6_1 in
*branch_9_6*. Those of you who commit more than I do may have better advice
than this!
> HttpJdkSolrClient doesn't encode curly braces etc
> -------------------------------------------------
>
> Key: SOLR-17263
> URL: https://issues.apache.org/jira/browse/SOLR-17263
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrJ
> Affects Versions: 9.6.0
> Reporter: Andy Webb
> Priority: Major
> Fix For: 9.6.1
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Ref
> https://issues.apache.org/jira/browse/SOLR-599?focusedCommentId=17842429#comment-17842429
> - {{HttpJdkSolrClient}} should use {{{}SolrParams{}}}' {{toQueryString()}}
> method when constructing URLs to that all URL-unsafe characters are encoded.
> It's implicitly using the {{toString()}} method currently which is intended
> for logging etc purposes.
> Attempting to use alternate query parsers in requests as shown below will
> currently fail as the curly braces aren't encoded.
> {noformat}
> myquery.set("fq", "{!terms f=myfield}value1,value2"); {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
