I suppose I exist in lala-land; today, Compass is working fine. It
created its own file-based /compass-index and seems to be indexing. The
present installation uses Derby.
Many thanks
Jack
On 9/27/2011 11:24 PM, Richard Hirsch wrote:
What database are you using? Derby or something else?
There should be log entries when ESME starts saying that the the
compass indexes have been created.
INFO - Configuring from resource [/props/compass.cfg.xml]
INFO - Mapping class [class org.apache.esme.model.Message]
INFO - Building analyzer [default]
INFO - Building analyzer [pool]
INFO - Building analyzer [stemming]
INFO - Not using highlighter - no highlighter jar included.
INFO - Starting scheduled optimizer [class org.compass.core.lucene.engine.optimi
zer.AdaptiveOptimizer] with period [10000ms]
INFO - Starting scheduled index manager with period [60000ms]
INFO - Starting scheduled refresh cache with period [5000ms]
I just tried the search on the cloudbees instance (where 1.3 is
installed) and it works.
D.
On Wed, Sep 28, 2011 at 7:53 AM, Jack Park<[email protected]> wrote:
I have a version of ESME online for experiments. There are several messages.
When I type one of the words from one of the messages into the search bar,
nothing is found. Is Compass actually wired in?
Thanks
Jack
