Hi,
Yes, in some point Compass is high level abstraction layer of the Lucene low
level API. Where is no much info resources online, but reference at Compass
website is really good. Reference says that with Compass it is possible to
extract the required property from the Object model at run-time and insert
required meta data into the search engine index.
I have been reading very good reference manual at
http://www.opensymphony.com/compass/versions/0.9.0/html/index.html and also
page concerning OSEM at
http://www.opensymphony.com/compass/versions/0.9.0/html/core-osem-xml.html#meta-dataand
I haven't noticed any heavy drawbacks about OSEM.
I would appreciate any remarks if possible.
Tomas Jucius
On 5/9/06, Cris Daniluk <cris.danilu..mail.com> wrote:
>
> I'm a little concerned about the seeming limitations of Compass and
> OSEM in general... I haven't had the time to do as much research as
> I'd like, but it seems like its heavily geared toward Lucene and
> doesn't support the complex metadata more "enterprise" search engines
> might use.
>
> Tomas, are there any articles or resources that you might have to give
> me a primer on its capabilities?
>
> Thanks!
>
> Cris
>
> On 5/9/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
> > I also tend to lean the Compass way. Could you please update your
> > wiki proposal to concentrate on Compass deliverables. Also one thing
> > it would be nice to have in deliverables is a sample Cayenne
> > application that demonstrates how Cayenne and Compass work side by
> > side (e.g. looking up DataObject via Compass and then using it in a
> > normal way).
> >
> > Andrus
> >
> >
> > On May 8, 2006, at 4:14 PM, Tomas Jucius wrote:
> >
> > > Hi,
> > >
> > > I have done research and came to conclusion that implementing a
> > > plugin for
> > > Compass framework would be much more elegant approach than building
> > > a facade
> > > to the existing DB's.
> > >
> > > I'll name main reasons why I draw such conclusion:
> > >
> > > Facade approach:
> > >
> > > 1) Because not all DB's have full text search capabilities
> > > implementing as a
> > > facade to existing capabilities would make Cayenne framework
> > > inconsistent
> > > with some DB's. I suppose that one great quality of present
> > > framework is
> > > compatibility with supported databases.
> > >
> > > 2) Not elegant approach.
> > >
> > > 3) Taking care about all differences between DB's may be time
> > > consuming.
> > > Also future changes in different DB's may lead to error-prone code..
> > >
> > > Compass plugin approach:
> > >
> > > 1) Compass allows declaratively map object domain model to the
> > > underlying
> > > Search Engine, synchronizing data changes between Index and different
> > > datasources. Also implements fast index operations and optimization.
> > >
> > > 2) Provides a abstraction on top of the Lucene low level API.
> > >
> > > 3) OSEM - ability to map java objects to the search engine through
> > > simple
> > > xml mapping files.
> > >
> > > 4) Hibernate ORM framework and OJB tool has compass plugin witch
> > > provides
> > > support for indexing datasource through OSEM and the named
> > > frameworks. So we
> > > can take good points from Hibernate plugin development experience.
> > >
> > > 5) Cayenne framework is a natural match to Compass OSEM features. A
> > > simple
> > > Compass::Gps device can index all the data that has both OSEM and ORM
> > > mapping definition can be easily developed, and if the ORM tool
> > > provides
> > > support for events, then mirroring can be supported as well.
> > >
> > > I would appreciate any notes considering these two or maybe event
> > > another
> > > possible approach.
> > >
> > >
> > > Tomas Jucius
> >
> >
>
This archive was generated by hypermail 2.0.0 : Tue May 09 2006 - 16:55:33 EDT