Bug 542828 - Underscore in 'Details Filter' breaks filtering - no messages are displayed
Summary: Underscore in 'Details Filter' breaks filtering - no messages are displayed
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Events
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Simeon Pinder
QA Contact: Jeff Weiss
URL:
Whiteboard:
Depends On:
Blocks: RHQ-2284 JON231
TreeView+ depends on / blocked
 
Reported: 2009-11-30 21:40 UTC by Jaroslaw Kijanowski
Modified: 2014-11-09 22:50 UTC (History)
3 users (show)

Fixed In Version: 2.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-08-12 16:50:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Jaroslaw Kijanowski 2009-11-30 21:40:25 UTC
Description of problem:
I have enabled event loggin. Now when I filter events I use 'Details Filter'.
When I try to filter strings that contains the "_" character nothing is displayed although there are events which should match.

Version-Release number of selected component (if applicable):
JON-2.3.0.GA

How reproducible:
Every time

Steps to Reproduce:
1. enable event logging
2. force the server to display some log message with the "_" character
3. search for this message using the 'Details Filter' text box
  
Actual results:
No messages show up

Expected results:
Messages with the "_" character should be displayed

Additional info:
-

Comment 1 Charles Crouch 2010-01-22 15:19:38 UTC
This was found using JON against Oracle 10g

Comment 2 Charles Crouch 2010-01-22 16:27:41 UTC
I just tried this on PG and it worked fine. Using _ in the Details filter found...

[org.rhq.enterprise.server.measurement.MeasurementCompressionManagerBean] Begin purging data from table [RHQ_MEASUREMENT_DATA_NUM_1D] before [Thu Jan 22 11:00:…

Comment 3 Simeon Pinder 2010-02-01 14:49:33 UTC
Fixed: 

svn rev 5278

git hash 41074662511d03f3cbced4c631a2433b2583d6e1

Added new utility, better backslash processing and post pending ESCAPE clause.  For master _ and % processing should be working more correctly than it has been in a long time. 


Reproduce instructions for both Postgres and Oracle:

i) install release on [Postgres || Oracle]
ii) import resources into JON and enable Event logging for RHQ JBossAS (remember double edit and double save on Inventory subtab properties )
iii) restart the Jon server
iv) navigate to RHQ JBossAS resource -> Events and search in the 'Details' field for: CLUSTERED  and a few events featuring $_NON_CLUSTERED should be returned
v) search in same field with NON_CLUSTERED and confirm the same number of results as previous search are returned with an "_" in the search string.  
vi) Rinse and repeat with the other database.

Comment 4 Simeon Pinder 2010-02-02 19:24:08 UTC
Charles wants this to be tested with the following database versions to guard against regression:
i) Oracle 10G 
i) Postgres 8.2.* and 8.4.*

Comment 5 Simeon Pinder 2010-02-03 16:57:58 UTC
svn 5280 includes changes for escaping % and \ as well in the Resource and Event search queries.


Additional Reproduce instructions for Resource Search:
i) install release on [Postgres || Oracle]
ii) import resources into JON
iii) rename one of the resources to include _, then search for the string without and with underscore. _ search should isolate resource names correctly now.

Comment 6 Corey Welton 2010-02-11 17:06:50 UTC
Postgresql 8.4 regression was clean.

Comment 7 Jeff Weiss 2010-02-11 20:27:21 UTC
Oracle 10G works too.  Just need Postgres 8.2 now

Comment 8 Corey Welton 2010-02-12 15:17:02 UTC
Postgres 8.2 regression was clean.

QA Verified.

Comment 9 wes hayutin 2010-02-16 16:51:26 UTC
Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs.

keyword:
new = Tracking + FutureFeature + SubBug

Comment 10 wes hayutin 2010-02-16 16:57:46 UTC
making sure we're not missing any bugs in rhq_triage

Comment 12 Corey Welton 2010-08-12 16:50:46 UTC
Mass-closure of verified bugs against JON.


Note You need to log in before you can comment on or make changes to this bug.