Hi Jack, When I test on http://esmecloudserverapache.dickhirsch.staxapps.net/ using the messages "Hello world.", "Hello there", and "hello", and then search for "hello", I see all three messages. (Though it does appear that search for old messages is borked, so it seems something killed off the index persistence across restarts on Stax again.)
By default, our indexes are persisted on the file system (since you are running on Derby for the database, I am assuming you are using the default setup). So if you are losing those indexes between restarts for some reason, then you will not be able to search for messages posted before the last restart. Is it possible that this is what is happening? Cheers, Ethan On Thu, Oct 20, 2011 at 6:58 AM, Jack Park <[email protected]> wrote: > Hi Dick, > > I see nothing that suggests any issues in any of the compass prop files, > though one of them, specific to MySQL prompts this: should it matter that > I'm running under Derby in my trials? > > Thanks > Jack > > > On 10/19/2011 8:30 PM, Richard Hirsch wrote: > >> Hi Jack, >> >> The search in ESME is compass-based, so we would probably have to look >> at the compass configuration to fine-tune it. Have you seen the >> compass properties file in resources/props? That might be a first >> place to start. >> >> Regards, >> >> Dick >> >> >> >> On Thu, Oct 20, 2011 at 12:50 AM, Jack Park<[email protected]> >> wrote: >> >>> I have several messages with "hello" in one form or another, e.g. Hello >>> world, and hello there >>> >>> When I type hello into the search bar, it brings up just the message with >>> Hello world. >>> >>> When I type world in the search bar, it brings up a message with "worlds" >>> in >>> it, but not the one with Hello world >>> >>> What do we know about the stability and reliability of search? Are there >>> specific heuristics, a command line to clear it and cause it to re-index? >>> >>> Thanks in advance >>> Jack >>> >>>
