Hello again! It seams that I made a mistake in my evaluation.
The problem seems to be linked when the slash is followed by a series of letters only. It means my query works for: M/AB2/.... L/A11/... but not for L/ABC... M/ZTS... I came across some messages on the internet regarding lucene/solr and slashes but I have absolutely no idea on how I could solve this problem... ---------- Forwarded message ---------- From: rfr <[email protected]> Date: Tue, Feb 26, 2013 at 2:16 PM Subject: Strange fulltext search behaviour To: [email protected] Hello! In our application, some nodes have "record numbers" in the form [A-Z]/([A-Z]|[0-9])+/[0-9]{9} For exemple: N/620/000002032 M/AKA/000000235 or L/AMA/0000000100 If I perform a full text search on this values, the search find my nodes. If i try a search like N/*2032 or M/AK*235, I'm also able to retrieve my nodes. But for an unknown reason, if I search for L/* or even L/AMA/000000?00, the system does not find any node and seems to not even search for something. The record number is stored in a string property and I'm sure the nodes are indexed since other queries on the same nodes works for other search tokens. It is like the "L/..." format is causing some troubles to the indexer or the search code. Any pointers? Can someone test this behaviour to see if it is reproductible? Thanks a lot! Regards, Fred
