MHMDhub / enterprise-log-search-and-archive

Automatically exported from code.google.com/p/enterprise-log-search-and-archive
0 stars 0 forks source link

AND/OR, +/- issues with Saved Searches. #90

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run and save a search query with + in it. 
2. Edit Saved Searches, just add a blank space to Value and save it again . 
3. Use macro or "Add to Current Search", the + sign is gone.

What is the expected output? What do you see instead?
Example-1: A search query like: "+7777 +failed" finds the expected failed 
keepalived_healthcheck on port 7777.
Example-2: A search query like "7777 AND failed" finds the same thing.

Using macro, Example-1 works while Example-2 changes case on AND and gets the 
result from "7777 and failed".

Editing Saved Searches, to change port from +7777 to +8888, the + sign gets 
lost. Returns the result for "8888 failed" instead of the expected "+8888 
+failed".

Expected behavior would be for the +sign to be kept after edit and that CASE 
from search query to be kept when saved.

What version of the product are you using? On what operating system?
Elsa revision 596 on Debian 6.0.6. 
Client Chrome 23.0.1271.101 on Mac OS X 10.7.5

Please provide any additional information below.
A work around is to not edit Saved Searches.
Delete, make new query, save as same name.

And to avoid the case issue, use + sign instead of AND.

Original issue reported on code.google.com by lars.kro...@axstores.se on 10 Jan 2013 at 11:07

GoogleCodeExporter commented 8 years ago
Silly mistake with URI encoding of values in the AJAX, it's fixed now as of 
revision 601.  Sorry, and thanks for filing the bug report!

Original comment by mchol...@gmail.com on 10 Jan 2013 at 3:39

GoogleCodeExporter commented 8 years ago
Great work! 
The + sign in Saved Searched issue is gone.
Tested and verified on revision 603, Debian 6.0.6.

Original comment by lars.kro...@axstores.se on 11 Jan 2013 at 8:28