Menu
▾
▴
springframework-developer
|
From: Brian M. <br...@ap...> - 2005-04-02 21:19:59
|
I have a set of classes for Apache Lucene integration with Spring (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which are designed to a) make it easier to work with Lucene from Spring (the template in particular optimizes common cases nicely, and does the resource open/closing like the other templates) b) make lucene index modifications abide by Spring's transaction system by doing write-behind on adds (which are ignored on rollback) and rolling back deletes via a transaction synchronization. I'd like to contribute them to Spring (if ya'll are interested), but to clean up the code and design some first, I have a few questions: 1) Should transaction binding be "on" by default? Lucene is semi-transactional by nature (supports r and r/w locks, changes are flushed on reader/writer closing, etc), but I am not sure people expect Lucene to be bound by other transactions. Potential confusion. 2) What is a good tx manager to use for the unit tests? I am using a modified version of the TestTransactionManager in Spring right now (just changed to make it accessible and use synchonrizations). It is much easier to use the TransactionTemplate than to manually manage the tx's for tests =) 3) Not all of the ~interesting things you can do in lucene are convenient to expose (splitting indexes etc) from the configuration. Right now, rather than make a hack, the factory beans only support single indexes. The only multi-index thing exposed right now is really a configuration option on the SearcherBean which allows for multiple indexes and a MultiSearcher ~transparently. Thanks! -Brian |
|
From: Brian M. <br...@ap...> - 2005-04-02 21:35:38
|
snapshot of the classes as they are now: http://morphy.skife.org/spring-lucene/ -Brian On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > I have a set of classes for Apache Lucene integration with Spring > (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which > are designed to > > a) make it easier to work with Lucene from Spring (the template in > particular optimizes common cases nicely, and does the resource > open/closing like the other templates) > > b) make lucene index modifications abide by Spring's transaction > system by doing write-behind on adds (which are ignored on rollback) > and rolling back deletes via a transaction synchronization. > > > > I'd like to contribute them to Spring (if ya'll are interested), but > to clean up the code and design some first, I have a few questions: > > 1) Should transaction binding be "on" by default? Lucene is > semi-transactional by nature (supports r and r/w locks, changes are > flushed on reader/writer closing, etc), but I am not sure people > expect Lucene to be bound by other transactions. Potential confusion. > > 2) What is a good tx manager to use for the unit tests? I am using a > modified version of the TestTransactionManager in Spring right now > (just changed to make it accessible and use synchonrizations). It is > much easier to use the TransactionTemplate than to manually manage the > tx's for tests =) > > 3) Not all of the ~interesting things you can do in lucene are > convenient to expose (splitting indexes etc) from the configuration. > Right now, rather than make a hack, the factory beans only support > single indexes. The only multi-index thing exposed right now is really > a configuration option on the SearcherBean which allows for multiple > indexes and a MultiSearcher ~transparently. > > Thanks! > > -Brian > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Rob H. <ro...@ca...> - 2005-04-03 11:02:17
|
Brian, I took a look at the code and it looks really useful. I had actually started something similar but I am no where near where you are with your code. I'm happy to work with you on this code - we just need to decide where to put it. I had originally intended to put my code in the fledgling Spring Modules project, but we should evaluate the possibility of putting it in Spring main. What are everyone's thought. Lucene is a relatively small JAR at only 316K so it won't have a huge impact on distribution size. Rob Brian McCallister wrote: > snapshot of the classes as they are now: > > http://morphy.skife.org/spring-lucene/ > > -Brian > > On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > >> I have a set of classes for Apache Lucene integration with Spring >> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >> are designed to >> >> a) make it easier to work with Lucene from Spring (the template in >> particular optimizes common cases nicely, and does the resource >> open/closing like the other templates) >> >> b) make lucene index modifications abide by Spring's transaction >> system by doing write-behind on adds (which are ignored on rollback) >> and rolling back deletes via a transaction synchronization. >> >> >> >> I'd like to contribute them to Spring (if ya'll are interested), but >> to clean up the code and design some first, I have a few questions: >> >> 1) Should transaction binding be "on" by default? Lucene is >> semi-transactional by nature (supports r and r/w locks, changes are >> flushed on reader/writer closing, etc), but I am not sure people >> expect Lucene to be bound by other transactions. Potential confusion. >> >> 2) What is a good tx manager to use for the unit tests? I am using a >> modified version of the TestTransactionManager in Spring right now >> (just changed to make it accessible and use synchonrizations). It is >> much easier to use the TransactionTemplate than to manually manage >> the tx's for tests =) >> >> 3) Not all of the ~interesting things you can do in lucene are >> convenient to expose (splitting indexes etc) from the configuration. >> Right now, rather than make a hack, the factory beans only support >> single indexes. The only multi-index thing exposed right now is >> really a configuration option on the SearcherBean which allows for >> multiple indexes and a MultiSearcher ~transparently. >> >> Thanks! >> >> -Brian >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > |
|
From: Brian M. <br...@ch...> - 2005-04-03 14:30:40
|
Cool. I've been javadoc-ing it, and cleaning up some of the duplication. Will keep poking at it locally until we figure out what to do with it. Spring main, Spring Modules, Lucene contrib, just self hosted, however it goes =) Figured I had it, and a bunch of folks I know asked for it, so might as well share. -Brian On Apr 3, 2005, at 7:00 AM, Rob Harrop wrote: > Brian, > > I took a look at the code and it looks really useful. I had actually > started something similar but I am no where near where you are with > your code. > > I'm happy to work with you on this code - we just need to decide where > to put it. I had originally intended to put my code in the fledgling > Spring Modules project, but we should evaluate the possibility of > putting it in Spring main. > > What are everyone's thought. Lucene is a relatively small JAR at only > 316K so it won't have a huge impact on distribution size. > > Rob > > Brian McCallister wrote: > >> snapshot of the classes as they are now: >> >> http://morphy.skife.org/spring-lucene/ >> >> -Brian >> >> On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: >> >>> I have a set of classes for Apache Lucene integration with Spring >>> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >>> are designed to >>> >>> a) make it easier to work with Lucene from Spring (the template in >>> particular optimizes common cases nicely, and does the resource >>> open/closing like the other templates) >>> >>> b) make lucene index modifications abide by Spring's transaction >>> system by doing write-behind on adds (which are ignored on rollback) >>> and rolling back deletes via a transaction synchronization. >>> >>> >>> >>> I'd like to contribute them to Spring (if ya'll are interested), but >>> to clean up the code and design some first, I have a few questions: >>> >>> 1) Should transaction binding be "on" by default? Lucene is >>> semi-transactional by nature (supports r and r/w locks, changes are >>> flushed on reader/writer closing, etc), but I am not sure people >>> expect Lucene to be bound by other transactions. Potential >>> confusion. >>> >>> 2) What is a good tx manager to use for the unit tests? I am using a >>> modified version of the TestTransactionManager in Spring right now >>> (just changed to make it accessible and use synchonrizations). It is >>> much easier to use the TransactionTemplate than to manually manage >>> the tx's for tests =) >>> >>> 3) Not all of the ~interesting things you can do in lucene are >>> convenient to expose (splitting indexes etc) from the configuration. >>> Right now, rather than make a hack, the factory beans only support >>> single indexes. The only multi-index thing exposed right now is >>> really a configuration option on the SearcherBean which allows for >>> multiple indexes and a MultiSearcher ~transparently. >>> >>> Thanks! >>> >>> -Brian >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Brian M. <br...@ap...> - 2005-04-03 16:29:22
|
Cool. I've been javadoc-ing it, and cleaning up some of the duplication. Will keep poking at it locally until we figure out what to do with it. Spring main, Spring Modules, Lucene contrib, just self hosted, however it goes =) Figured I had it, and a bunch of folks I know asked for it, so might as well share. -Brian On Apr 3, 2005, at 7:00 AM, Rob Harrop wrote: > Brian, > > I took a look at the code and it looks really useful. I had actually > started something similar but I am no where near where you are with > your code. > > I'm happy to work with you on this code - we just need to decide where > to put it. I had originally intended to put my code in the fledgling > Spring Modules project, but we should evaluate the possibility of > putting it in Spring main. > > What are everyone's thought. Lucene is a relatively small JAR at only > 316K so it won't have a huge impact on distribution size. > > Rob > > Brian McCallister wrote: > >> snapshot of the classes as they are now: >> >> http://morphy.skife.org/spring-lucene/ >> >> -Brian >> >> On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: >> >>> I have a set of classes for Apache Lucene integration with Spring >>> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >>> are designed to >>> >>> a) make it easier to work with Lucene from Spring (the template in >>> particular optimizes common cases nicely, and does the resource >>> open/closing like the other templates) >>> >>> b) make lucene index modifications abide by Spring's transaction >>> system by doing write-behind on adds (which are ignored on rollback) >>> and rolling back deletes via a transaction synchronization. >>> >>> >>> >>> I'd like to contribute them to Spring (if ya'll are interested), but >>> to clean up the code and design some first, I have a few questions: >>> >>> 1) Should transaction binding be "on" by default? Lucene is >>> semi-transactional by nature (supports r and r/w locks, changes are >>> flushed on reader/writer closing, etc), but I am not sure people >>> expect Lucene to be bound by other transactions. Potential >>> confusion. >>> >>> 2) What is a good tx manager to use for the unit tests? I am using a >>> modified version of the TestTransactionManager in Spring right now >>> (just changed to make it accessible and use synchonrizations). It is >>> much easier to use the TransactionTemplate than to manually manage >>> the tx's for tests =) >>> >>> 3) Not all of the ~interesting things you can do in lucene are >>> convenient to expose (splitting indexes etc) from the configuration. >>> Right now, rather than make a hack, the factory beans only support >>> single indexes. The only multi-index thing exposed right now is >>> really a configuration option on the SearcherBean which allows for >>> multiple indexes and a MultiSearcher ~transparently. >>> >>> Thanks! >>> >>> -Brian >>> >>> >>> ------------------------------------------------------- >>> SF email is sponsored by - The IT Product Guide >>> Read honest & candid reviews on hundreds of IT Products from real >>> users. >>> Discover which products truly live up to the hype. Start reading now. >>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >>> _______________________________________________ >>> Springframework-developer mailing list >>> Spr...@li... >>> https://lists.sourceforge.net/lists/listinfo/springframework- >>> developer >>> >> >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> >> > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
|
From: Thierry T. <te...@ya...> - 2005-04-04 08:15:41
|
Great Brian!! > Cool. I've been javadoc-ing it, and cleaning up some > of the duplication. Will keep poking at it locally > until we figure out what to do with it. > > Spring main, Spring Modules, Lucene contrib, just > self hosted, however > it goes =) Figured I had it, and a bunch of folks I > know asked for it, > so might as well share. > > -Brian Take a look at my blog: http://templth.blogspot.com/ __________________________________________________________________ Découvrez le nouveau Yahoo! Mail : 250 Mo d'espace de stockage pour vos mails ! Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com/ |
|
From: Rob H. <rob...@in...> - 2005-04-10 14:56:05
|
Brian, I think if no-one else has any objections, this module is ideal for inclusion in Spring Modules. Rob -----Original Message----- From: spr...@li... [mailto:spr...@li...] On Behalf Of Brian McCallister Sent: 02 April 2005 22:36 To: spr...@li... Subject: Re: [Springframework-developer] Lucene Integration snapshot of the classes as they are now: http://morphy.skife.org/spring-lucene/ -Brian On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > I have a set of classes for Apache Lucene integration with Spring > (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which > are designed to > > a) make it easier to work with Lucene from Spring (the template in > particular optimizes common cases nicely, and does the resource > open/closing like the other templates) > > b) make lucene index modifications abide by Spring's transaction > system by doing write-behind on adds (which are ignored on rollback) > and rolling back deletes via a transaction synchronization. > > > > I'd like to contribute them to Spring (if ya'll are interested), but > to clean up the code and design some first, I have a few questions: > > 1) Should transaction binding be "on" by default? Lucene is > semi-transactional by nature (supports r and r/w locks, changes are > flushed on reader/writer closing, etc), but I am not sure people > expect Lucene to be bound by other transactions. Potential confusion. > > 2) What is a good tx manager to use for the unit tests? I am using a > modified version of the TestTransactionManager in Spring right now > (just changed to make it accessible and use synchonrizations). It is > much easier to use the TransactionTemplate than to manually manage the > tx's for tests =) > > 3) Not all of the ~interesting things you can do in lucene are > convenient to expose (splitting indexes etc) from the configuration. > Right now, rather than make a hack, the factory beans only support > single indexes. The only multi-index thing exposed right now is really > a configuration option on the SearcherBean which allows for multiple > indexes and a MultiSearcher ~transparently. > > Thanks! > > -Brian > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Springframework-developer mailing list Spr...@li... https://lists.sourceforge.net/lists/listinfo/springframework-developer |
|
From: Brian M. <br...@ch...> - 2005-04-11 13:49:43
|
Yep, just checked it in there =) -Brian On Apr 10, 2005, at 10:56 AM, Rob Harrop wrote: > Brian, > > I think if no-one else has any objections, this module is ideal for > inclusion in Spring Modules. > > Rob > > -----Original Message----- > From: spr...@li... > [mailto:spr...@li...] On > Behalf Of > Brian McCallister > Sent: 02 April 2005 22:36 > To: spr...@li... > Subject: Re: [Springframework-developer] Lucene Integration > > snapshot of the classes as they are now: > > http://morphy.skife.org/spring-lucene/ > > -Brian > > On Apr 2, 2005, at 4:19 PM, Brian McCallister wrote: > >> I have a set of classes for Apache Lucene integration with Spring >> (reasonable factory beans, a LuceneTemplate, and LuceneUtils) which >> are designed to >> >> a) make it easier to work with Lucene from Spring (the template in >> particular optimizes common cases nicely, and does the resource >> open/closing like the other templates) >> >> b) make lucene index modifications abide by Spring's transaction >> system by doing write-behind on adds (which are ignored on rollback) >> and rolling back deletes via a transaction synchronization. >> >> >> >> I'd like to contribute them to Spring (if ya'll are interested), but >> to clean up the code and design some first, I have a few questions: >> >> 1) Should transaction binding be "on" by default? Lucene is >> semi-transactional by nature (supports r and r/w locks, changes are >> flushed on reader/writer closing, etc), but I am not sure people >> expect Lucene to be bound by other transactions. Potential confusion. >> >> 2) What is a good tx manager to use for the unit tests? I am using a >> modified version of the TestTransactionManager in Spring right now >> (just changed to make it accessible and use synchonrizations). It is >> much easier to use the TransactionTemplate than to manually manage the >> tx's for tests =) >> >> 3) Not all of the ~interesting things you can do in lucene are >> convenient to expose (splitting indexes etc) from the configuration. >> Right now, rather than make a hack, the factory beans only support >> single indexes. The only multi-index thing exposed right now is really >> a configuration option on the SearcherBean which allows for multiple >> indexes and a MultiSearcher ~transparently. >> >> Thanks! >> >> -Brian >> >> >> ------------------------------------------------------- >> SF email is sponsored by - The IT Product Guide >> Read honest & candid reviews on hundreds of IT Products from real >> users. >> Discover which products truly live up to the hype. Start reading now. >> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click >> _______________________________________________ >> Springframework-developer mailing list >> Spr...@li... >> https://lists.sourceforge.net/lists/listinfo/springframework-developer >> > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real > users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
