Compass Framework
Hi all, I recently came across the Compass Framework, which is built on top of lucene. I am interested in it because it stores the lucene index in an RDBMS and provides transaction support for index updates (it also has several other features but this is the part I'm mostly interested in). I wanted to know if any people here have had any experience with compass and what they think about it. Is the database implementation of the index fast enough and does it introduce any additional issues/problems? Thanks in advance, Marios Msg sent via eXis webmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compass Framework
Database implementation of the index is always bound to be slow compared to storing it on the filesystem. Probably the group which stores indexes into Berkley DB should be able to give you a performance measuer of what will happen you store indexex in databases. Rgds Prabhu On 4/8/06, Marios Skounakis [EMAIL PROTECTED] wrote: Hi all, I recently came across the Compass Framework, which is built on top of lucene. I am interested in it because it stores the lucene index in an RDBMS and provides transaction support for index updates (it also has several other features but this is the part I'm mostly interested in). I wanted to know if any people here have had any experience with compass and what they think about it. Is the database implementation of the index fast enough and does it introduce any additional issues/problems? Thanks in advance, Marios Msg sent via eXis webmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compass Framework
As far as I know, Compass Framework does not store index into database. It just index data when data pass Hibernate, iBatis, or other layer. So if you use these layers in your code, you can use Compass. Chris Lu -- Full-Text Lucene Search on Any Databases http://www.dbsight.net Faster to setup than reading marketing materials! On 4/8/06, Raghavendra Prabhu [EMAIL PROTECTED] wrote: Database implementation of the index is always bound to be slow compared to storing it on the filesystem. Probably the group which stores indexes into Berkley DB should be able to give you a performance measuer of what will happen you store indexex in databases. Rgds Prabhu On 4/8/06, Marios Skounakis [EMAIL PROTECTED] wrote: Hi all, I recently came across the Compass Framework, which is built on top of lucene. I am interested in it because it stores the lucene index in an RDBMS and provides transaction support for index updates (it also has several other features but this is the part I'm mostly interested in). I wanted to know if any people here have had any experience with compass and what they think about it. Is the database implementation of the index fast enough and does it introduce any additional issues/problems? Thanks in advance, Marios Msg sent via eXis webmail - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Compass Framework 0.8 + Jdbc Lucene Directory
We are pleased to announce the 0.8.0 release of Compass Framework - A Java Search Engine Framework based on Lucene. Major feature of this release is the ability to store Lucene index within a database. The feature has two parts: A complete Lucene Jdbc Directory implementation which is separated from any Compass related code (currently part of the compass-core module and jar), allowing using it in pure Lucene implementations. The Lucene Jdbc Directory comes with documentation as an Appendix in Compass documentation (http://static.compassframework.org/docs/latest/jdbcdirectory.html). The second part is the integration of Jdbc Directory with Compass Framework, allowing existing compass code to work as is, requiring changes to configuration settings only. The integration includes several Data Source Providers (Dbcp, c3p0, Jndi, and more), and special automatic performance improvements. Cheers, Shay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
