Hi Patryk,
Thanks for experimenting.
> Escaping parentheses worked for me though:
Yes, with selective escaping of the parentheses but that's not equivalent to
quoting and seems to require no other special characters than the 2
parentheses.
When sending the query/field value through a proper
Hi Thomas,
Apparently, the parser becomes more sensitive to special characters when the
local parameter is in the middle of a query. Possibly because an increased need
for context switching.
Escaping parentheses worked for me though:
curl
'http://localhost:8983/solr/demo/select?rows=5&q=inStoc
Hi,
Thanks for suggesting local parameters. Unfortunately I can't refactor the
codebase to make use of them because these queries are placed in fq statements
that are treated as individual units by the UI. It would require massive
refactoring and higher complexity as a consequence. The graph tra
Hi Thomas,
I can’t reproduce the exact results, but this might be caused by the space
character, which is double-encoded (%2520). Are you still seeing the issue if
you replace it with %20?
Kind regards,
Patryk
On 2024/09/14 08:56:55 Thomas Åkesson wrote:
> Hi,
> We have come across a potent
Hello Thomas.
I think extensive use of local parameters references is easy than fighting
with escaping
q=inStock:true AND {!boost b=manufacturedate_dt v=$nameq}&nameq={!field
f=name}the (concept).xml
or even ...{!field f=name v=$nameval}&nameval=the (concept).xml
also depending on the field type yo
Hi,
We have come across a potentially incorrect lexical error with the following
combination in the query:
- Parentheses in the search term (tried both escaping and quoting)
- Query parser within {}. Actual use-case is using !graph but clearer
reproduction with something simple like !boost.
