From: Isidor Z. <cl...@qu...> - 2009-06-05 14:50:14
Attachments:
test-incremental-indexing.diff
|
The latest git commits seem to have a problem finding terms in the index when the documents were added during multiple IndexWriter sessions with create=false. Attached is a test which demonstrates this. It still worked at 3021ed62235ebbb2a5195512366dcf237adfbea9 . Best regards, Isidor |
From: Isidor Z. <cl...@qu...> - 2009-07-03 04:54:24
Attachments:
load-merged-norms.diff
|
It turns out that the searches succeed again when using the norm data from the previous segments while merging. The attached patch does this. Best regards, Isidor |
From: Ben v. K. <bva...@gm...> - 2009-07-08 09:51:53
|
Hi Isidor, I'm very sorry I haven't been replying to your emails. Things have been very busy here, my wife and I are about to have our first baby in the next few days/weeks. But today I have half a day, so I'm going to try and reply to as much as possible... Good call on this, that was a pretty bad bug. I'm not sure why that bit of code was missed out (it is in the java version), but there's no need to check the object type and cast - i've just put: reader->norms(fi->name, normBuffer->values); in that location 68bf2e05af85263fe5d3e487fd383c76feb715a2 is committed on master ben 2009/7/3 Isidor Zeuner <cl...@qu...>: > It turns out that the searches succeed again when using the norm data > from the previous segments while merging. The attached patch does > this. > > Best regards, > > Isidor > > ------------------------------------------------------------------------------ > > _______________________________________________ > CLucene-developers mailing list > CLu...@li... > https://lists.sourceforge.net/lists/listinfo/clucene-developers > > |
From: Isidor Z. <cl...@qu...> - 2009-07-09 08:29:32
|
Hi Ben, > > I'm very sorry I haven't been replying to your emails. Things have > been very busy here, my wife and I are about to have our first baby in > the next few days/weeks. But today I have half a day, so I'm going to > try and reply to as much as possible... > I completely understand that. You have my best wishes, hope it goes all well. Still, I greatly appreciate your dedication to CLucene given your situation. But the codebase by itself is a great resource, so I'm doing quite well while being on my own with it sometimes. When my fixes are committed from time to time (or I get feedback why they don't fit in), it's already very useful to me (I've been forced brokering patches lately since users had problems with the git code...). > Good call on this, that was a pretty bad bug. I'm not sure why that > bit of code was missed out (it is in the java version), but there's no > need to check the object type and cast - i've just put: > reader->norms(fi->name, normBuffer->values); in that location > Thanks. I missed that method in IndexReader. A second eye always pays... Best regards, Isidor |
From: Itamar Syn-H. <it...@di...> - 2009-07-15 21:22:35
|
> But the codebase by itself is a great resource, so I'm doing quite well while being on my > own with it sometimes. When my fixes are committed from time to time (or I get feedback > why they don't fit in), it's already very useful to me (I've been forced brokering patches > lately since users had problems with the git code...). Just keep testing, and the patches coming. You have no idea how helpful they are, Ben and I having so little time to do both development and testing at the moment :-) Just one more thing - when you report a bug or something else which requires fixing, it would be easier to track if you could post it to the tracker (you could still send a mail with a link to the item ID there so we don't miss it). It's just that sometimes I find myself digging in old mails, not knowing the status of the items you reported even if I myself attended to them. This also applies to items you've sent us before and were not handled / fixed yet.... Thanks. Itamar. -----Original Message----- From: Isidor Zeuner [mailto:cl...@qu...] Sent: Thursday, July 09, 2009 9:31 AM To: clu...@li... Subject: Re: [CLucene-dev] incrementally writing to an index Hi Ben, > > I'm very sorry I haven't been replying to your emails. Things have > been very busy here, my wife and I are about to have our first baby in > the next few days/weeks. But today I have half a day, so I'm going to > try and reply to as much as possible... > I completely understand that. You have my best wishes, hope it goes all well. Still, I greatly appreciate your dedication to CLucene given your situation. But the codebase by itself is a great resource, so I'm doing quite well while being on my own with it sometimes. When my fixes are committed from time to time (or I get feedback why they don't fit in), it's already very useful to me (I've been forced brokering patches lately since users had problems with the git code...). > Good call on this, that was a pretty bad bug. I'm not sure why that > bit of code was missed out (it is in the java version), but there's no > need to check the object type and cast - i've just put: > reader->norms(fi->name, normBuffer->values); in that location > Thanks. I missed that method in IndexReader. A second eye always pays... Best regards, Isidor ---------------------------------------------------------------------------- -- Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ CLucene-developers mailing list CLu...@li... https://lists.sourceforge.net/lists/listinfo/clucene-developers |