Thank you for the example, Ahmet!
Paolo- what you did in choice 'b' does what you want - it escapes the
colon in the URI. But Ahmet's example is a better way because it does
not have the 'double-escaping' problem that us old Unix types are so
familiar with.
On 6/18/10, Chris Hostetter wrote:
>
>
: I am not sure how SolrJ behaves regarding "escaping" special characters
: [1] in a query string.
SolrJ encodes your strings for "transport" -- ie: it handles URL escaping
if it's sending hte query in a GET URL -- but id doesn't do "query parser
escaping" ... mainly because it has no way of kn
> My understanding is that SolrJ users are supposed to escape
> special characters, therefore (b) is the correct way.
> If this is the case, what's the best way to escape a query
> string which
> might contain field names and URIs in their field values?
Easiest thing is to use RawQParserPlugin or
