If you search for an issue with a string like ${abc} you have an error: 'Could not parse the query text.' From my prospective it is a valid string, because I am searching for issues where ${abc} variable is dealt with. Probably, the curly brackets should be escaped.
Description
If you search for an issue with a string like ${abc} you have an error: 'Could not parse the query text.' From my prospective it is a valid string, because I am searching for issues where ${abc} variable is dealt with. Probably, the curly brackets should be escaped.
The issue is not so much that the query is not escaped, but the fact that the search engine that we use underneath (Lucene) strips out all the punctuation and special characters. It does it to help searching for regular terms, however if exact matching is required, it does not work.
It is now possible to escape to enter "\${<a string>}" and the query wil be parsed. However it will match all issues that contain "string" and ignore special characters.
Allowing exact matching is not a small task, but we are hoping to address it one day. Do you mind if I turn this issue into an improvement request for implementing "exact matching"?
Anton Mazkovoi [Atlassian] added a comment - 03/May/07 02:04 AM Hi Yevgeny,
The issue is not so much that the query is not escaped, but the fact that the search engine that we use underneath (Lucene) strips out all the punctuation and special characters. It does it to help searching for regular terms, however if exact matching is required, it does not work.
It is now possible to escape to enter "\${<a string>}" and the query wil be parsed. However it will match all issues that contain "string" and ignore special characters.
Allowing exact matching is not a small task, but we are hoping to address it one day. Do you mind if I turn this issue into an improvement request for implementing "exact matching"?
Cheers,
Anton
Yevgeny Studenikin added a comment - 03/May/07 09:24 AM Anton,
Thanks for the clarification. You are right, probably this can be considered as a Lucene bug. I don't mind converting this issue to an improvement.
Yevgeny.
New Feature
Open
Major
Add support for exact full text search including punctuation
The issue is not so much that the query is not escaped, but the fact that the search engine that we use underneath (Lucene) strips out all the punctuation and special characters. It does it to help searching for regular terms, however if exact matching is required, it does not work.
It is now possible to escape to enter "\${<a string>}" and the query wil be parsed. However it will match all issues that contain "string" and ignore special characters.
Allowing exact matching is not a small task, but we are hoping to address it one day. Do you mind if I turn this issue into an improvement request for implementing "exact matching"?
Cheers,
Anton