While creating some unit tests for my Lucene queries, I noticed some strange punctuation behavior, in particular around parentheses.
What are some of the best ways to work with search fields that contain significant punctuation?
If you have not configured the query parser, Lucene should behave according to the syntax of the parsing of the query by query . Are you getting something else? Do you want punctuation to have special meaning or just remove punctuation from searches? Another common suspect here is Analyzer , which determines how your field is indexed and how the query is broken into parts for search. Can you post specific examples of bad behavior?
These are not only brackets, other point fragments, such as colon, hyphen, etc. will cause problems. Here is a way to deal with them.
Source: https://habr.com/ru/post/1757274/More articles:Как пропустить представление/расположение в контроллере zf - ajaxClient and server - c ++https://translate.googleusercontent.com/translate_c?depth=1&pto=aue&rurl=translate.google.com&sl=ru&sp=nmt4&tl=en&u=https://fooobar.com/questions/1757271/python-function-fails-to-return-unless-the-last-statement-is-slow&usg=ALkJrhjF0Y17YniIxSjc9q_3YIF7i9rXVQMoving a boolean with a simple view in Django? - djangoViews or Organic groups for this use case - phpHow can I test various environments (eg developmentSounds silly, but ... I need help setting a variable in PHP - variablesMonitor.TryEnter Tips - multithreadingHow are items stored in containers in .Net? - c ++I have the line "abc = 14.22 xyz = 33, tdc = 48" in the file. How can I split it into strings and their corresponding values in C ++? - c ++All Articles