Re: Abandoning Searchable Plugin

Jean-Noël Rivasseau-3 wrote:

At first the Searchable Plugin seems great,
unfortunately as my application grew in complexity I am having more
and more problems with it.

I crossed this line 2 times recently. From my PoV the problem lies not in the Plugin itself, but rather in Compass's own restrictions, which becomes too tight with the time.
At the very beginning the Compass/Searchable seem to be ok, but later you face obstacles, you cannot nicely overcome.

As a result, I had no other way than abandoning Compass for different really simple reasons in favor of the direct Lucene.

A simple example, which led to plugin removal, was following:

I have 2 classes like:

class Core {

  Date date

  Set<LocalizedInfo> localizedContents

}

class LocalizedInfo {

  String name

  String lang

  String text

}

So each Core can contain a collection of LocalizedInfo's, each of those are language-specific.

In Compass I would have to create locale-specific "marker" classes and mappings for them, like LocalizedInfoEnglish and LocalizedInfoGerman, which is anything but "groovy". The worst part is, that if I suddenly need a LocalizedInfoSpanish, I would have to redeploy and restart the whole app!

I built a service to index the objects, and it's smaller, that the SearchableConfiguration.groovy!
Now I can index any number of LocalizedInfo's in any language and search among them, using plain Lucene and Groovy with no additional complexity levels.

The only thing I kinda miss now is Searchable's QueryBuilder. It would be great, if Maurice or someone else publish it as a stand-alone module.