Re: Lucene Index backboned by DB

2005-11-16 Thread Robert Kirchgessner
Hi, > 1) It might be OK to implement retrieving field values separately for a > document. However, I think from a simplicity point of view, it might be > better to have the application code do this drudgery. Adding this feature > could complicate the nice and simple design of Lucene without much

Re: Lucene Index backboned by DB

2005-11-15 Thread jian chen
Dear All, I have some thoughts on this issue as well. 1) It might be OK to implement retrieving field values separately for a document. However, I think from a simplicity point of view, it might be better to have the application code do this drudgery. Adding this feature could complicate the nice

Re: Lucene Index backboned by DB

2005-11-15 Thread Robert Kirchgessner
Hi, a discussion in http://issues.apache.org/jira/browse/LUCENE-196 might be of interest to you. Did you think about storing the large pieces of documents in a database to reduce the size of Lucene index? I think there are good reasons to adding support for storing fields in separate files: 1

Lucene Index backboned by DB

2005-11-15 Thread Karel Tejnora
Hi all, in our testing application using lucene 1.4.3. Thanks you guys for that great job. We have index file around 12GiB, one file (merged). To retrieve hits it takes nice small amount of the time, but reading fields takes 10-100 times more (the stored ones). I think because all the fields