[jira] Commented: (LUCENE-1236) EdgeNGram* documentation improvement

[ https://issues.apache.org/jira/browse/LUCENE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579015#action_12579015 ] [EMAIL PROTECTED] commented on LUCENE-1236: - Dear sender, This domain is

[jira] Updated: (LUCENE-1236) EdgeNGram* documentation improvement

[ https://issues.apache.org/jira/browse/LUCENE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiroaki Kawai updated LUCENE-1236: -- Attachment: EdgeNGram.patch > EdgeNGram* documentation improvement > -

[jira] Created: (LUCENE-1236) EdgeNGram* documentation improvement

EdgeNGram* documentation improvement Key: LUCENE-1236 URL: https://issues.apache.org/jira/browse/LUCENE-1236 Project: Lucene - Java Issue Type: Improvement Components: contrib/* Repo

Summer of Code idea for lucene

If no one objects (I don't think it's too late) would you mind a GSOC project to implement BM25 relevancy/scoring? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (LUCENE-1235) NGramTokenizer optimization in query phase

[ https://issues.apache.org/jira/browse/LUCENE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiroaki Kawai updated LUCENE-1235: -- Attachment: NGramTokenizer.patch NGramTokenizer.patch includes LUCENE-1227, LUCENE-1225. > NG

[jira] Created: (LUCENE-1235) NGramTokenizer optimization in query phase

NGramTokenizer optimization in query phase -- Key: LUCENE-1235 URL: https://issues.apache.org/jira/browse/LUCENE-1235 Project: Lucene - Java Issue Type: Improvement Components: contrib/*

[jira] Assigned: (LUCENE-1202) Clover setup currently has some problems

[ https://issues.apache.org/jira/browse/LUCENE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reassigned LUCENE-1202: Assignee: Grant Ingersoll I was hoping seeing it again would jog your memory : ) i committed th

[jira] Commented: (LUCENE-1202) Clover setup currently has some problems

[ https://issues.apache.org/jira/browse/LUCENE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578992#action_12578992 ] Grant Ingersoll commented on LUCENE-1202: - You expect me to remember something sai

[jira] Resolved: (LUCENE-1234) BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access

[ https://issues.apache.org/jira/browse/LUCENE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved LUCENE-1234. - Resolution: Fixed Lucene Fields: [New, Patch Available] (was: [Patch Available, N

[jira] Assigned: (LUCENE-1234) BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access

[ https://issues.apache.org/jira/browse/LUCENE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned LUCENE-1234: --- Assignee: Grant Ingersoll > BoostingTermQuery's BoostingSpanScorer class should be p

[jira] Commented: (LUCENE-1234) BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access

[ https://issues.apache.org/jira/browse/LUCENE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578976#action_12578976 ] Andi Vajda commented on LUCENE-1234: The inaccessible class is called BoostingSpanScor

[jira] Updated: (LUCENE-1234) BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access

[ https://issues.apache.org/jira/browse/LUCENE-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andi Vajda updated LUCENE-1234: --- Attachment: patches-lucene-2.3.1 patch against lucene-2.3.1 sources > BoostingTermQuery's BoostingS

[jira] Created: (LUCENE-1234) BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access

BoostingTermQuery's BoostingSpanScorer class should be protected instead of package access -- Key: LUCENE-1234 URL: https://issues.apache.org/jira/browse/LUCENE-1234

Re: [jira] Commented: (LUCENE-1232) Use segments generation instead of version

ok... On Fri, Mar 14, 2008 at 10:00 PM, Michael McCandless (JIRA) <[EMAIL PROTECTED]> wrote: > >[ > https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578912#action_12578912] > > Michael McCandless comment

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578912#action_12578912 ] Michael McCandless commented on LUCENE-1232: That's a good point; because vers

[jira] Resolved: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1232. Resolution: Won't Fix > Use segments generation instead of version > -

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578904#action_12578904 ] Yonik Seeley commented on LUCENE-1232: -- A nice thing about version is that it has rel

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578897#action_12578897 ] Michael McCandless commented on LUCENE-1232: I like your new patch Doron. But

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578894#action_12578894 ] Doron Cohen commented on LUCENE-1232: - {quote} Anyhow I think that SegmentsInfo can be

[jira] Updated: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen updated LUCENE-1232: Attachment: LUCENE-1232.dc.patch I otoh liked this side effect of this change, i.e. that index ver

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578886#action_12578886 ] Michael McCandless commented on LUCENE-1232: Hoss, you're right: if an app ha

[jira] Resolved: (LUCENE-1230) Source release files missing the *.pom.template files

[ https://issues.apache.org/jira/browse/LUCENE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Busch resolved LUCENE-1230. --- Resolution: Fixed Committed to trunk & 2.3 branch. > Source release files missing the *.pom

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578871#action_12578871 ] Hoss Man commented on LUCENE-1232: -- if i'm understanding this correctly: we're removing t

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578870#action_12578870 ] Doron Cohen commented on LUCENE-1232: - Yes you're right, thanks. > Use segments gener

[jira] Commented: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578866#action_12578866 ] Michael McCandless commented on LUCENE-1232: I think this is OK: it looks like

[jira] Updated: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen updated LUCENE-1232: Attachment: check.version.vs.gen.diff To test this I added to SegmentInfos a comparison of *curren

Re: Should Document.getFieldables really return null

On Friday 14 March 2008 11:46:42 Michael McCandless wrote: > I agree, this makes sense. I'll commit it. Thanks Stefan! > > Except, the last one you list (getBinaryValue) I think should still > return null if no field by that name exists? Yes, you are right. Looking at the array notion made me so

[jira] Resolved: (LUCENE-1233) Fix Document.getFieldables and others to never return null

[ https://issues.apache.org/jira/browse/LUCENE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1233. Resolution: Fixed Thanks Stefan! > Fix Document.getFieldables and others to never

How to avoid byte[] allocation in Document.getBinaryValue(String name)

I am looking for ideas on how I could pass my byte[] to Document.getBinaryValue(String name) in order to avoid allocation of new byte[] for each Field retrieved. first idea I had was to add something like this in Document: public final byte[] getBinaryValue(String name, byte[] myBuffer) {

[jira] Created: (LUCENE-1233) Fix Document.getFieldables and others to never return null

Fix Document.getFieldables and others to never return null -- Key: LUCENE-1233 URL: https://issues.apache.org/jira/browse/LUCENE-1233 Project: Lucene - Java Issue Type: Improvement

Re: Should Document.getFieldables really return null

I agree, this makes sense. I'll commit it. Thanks Stefan! Except, the last one you list (getBinaryValue) I think should still return null if no field by that name exists? Mike Stefan Trcek wrote: Hello The 'Document.getFieldables(String name)' is documented to return 'null' in some c

[jira] Resolved: (LUCENE-1228) IndexWriter.commit() does not update the index version

[ https://issues.apache.org/jira/browse/LUCENE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doron Cohen resolved LUCENE-1228. - Resolution: Fixed Lucene Fields: [Patch Available] (was: [Patch Available, New]) Committ

[jira] Updated: (LUCENE-1232) Use segments generation instead of version

[ https://issues.apache.org/jira/browse/LUCENE-1232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-1232: --- Attachment: LUCENE-1232.patch Attached patch. I plan to commit in a day or two. >

Re: [jira] Created: (LUCENE-1231) Column-stride fields (aka per-document Payloads)

"A better way to do this is using payloads. By creating a "special" posting list that has one posting with payload for each document you can "simulate" a column- stride field. The performance is significantly better compared to stored fields, however still not optimal. The reason is that for each d

Re: [jira] Created: (LUCENE-1229) NGramTokenFilter optimization inquery phase

Thanks for your replay. > > I found that NGramTokenFilter-ed token stream could be optimized in query. > > > > A standard 1,2 NGramTokenFilter will generate a token stream from "abcde" > > as follows: > > a ab b bc c cd d de e > > > > When we index "abcde", we'll use all of the tokens. > > > > Bu

[jira] Created: (LUCENE-1232) Use segments generation instead of version

Use segments generation instead of version -- Key: LUCENE-1232 URL: https://issues.apache.org/jira/browse/LUCENE-1232 Project: Lucene - Java Issue Type: Improvement Components: Index Affe

[jira] Commented: (LUCENE-1187) Things to be done now that Filter is independent from BitSet

[ https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578656#action_12578656 ] Eks Dev commented on LUCENE-1187: - Michael, I do not think we need to add Factory (for th

Re: [jira] Created: (LUCENE-1229) NGramTokenFilter optimization in query phase

Hiroaki Kawai (JIRA) a écrit : NGramTokenFilter optimization in query phase Key: LUCENE-1229 URL: https://issues.apache.org/jira/browse/LUCENE-1229 Project: Lucene - Java Issue Type: Improvement

[jira] Commented: (LUCENE-1228) IndexWriter.commit() does not update the index version

[ https://issues.apache.org/jira/browse/LUCENE-1228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578649#action_12578649 ] Michael McCandless commented on LUCENE-1228: {quote} Does SegmentInfos really

[jira] Updated: (LUCENE-1202) Clover setup currently has some problems

[ https://issues.apache.org/jira/browse/LUCENE-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated LUCENE-1202: - Attachment: LUCENE-1202.patch builds on previous patch to fix contrib/db (which i should note: also cen

[jira] Commented: (LUCENE-1187) Things to be done now that Filter is independent from BitSet

[ https://issues.apache.org/jira/browse/LUCENE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12578626#action_12578626 ] Michael Busch commented on LUCENE-1187: --- {quote} Test that now fails with ChainedFil