RE: lucene 2.9 sorting algorithm

> Yes - I've seen a handful of non core devs report back that they > upgraded with no complaints on the difficulty. Its in the mailing list > archives. The only core dev I've seen say its easy is Uwe. He's super > sharp though, so I wasn't banking my comment on him ;) I didn't say it's easy -- for

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769099#action_12769099 ] Uwe Schindler commented on LUCENE-1997: --- bq. Thats my impression too - Java 1.6 is m

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769097#action_12769097 ] Mark Miller commented on LUCENE-1997: - bq. There was a bad stretch in Java6... But h

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769092#action_12769092 ] Mark Miller commented on LUCENE-1997: - Anyone got a Windows box to run this on? I'm on

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769090#action_12769090 ] John Wang commented on LUCENE-1997: --- bq: topn:100 I had made changes to sortBench.py to

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769089#action_12769089 ] Yonik Seeley commented on LUCENE-1997: -- There was a bad stretch in Java6... they plop

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769088#action_12769088 ] Mark Miller commented on LUCENE-1997: - John, what happened to your topn:100 results?

Re: lucene 2.9 sorting algorithm

Hi Yonik: I have been head deep in this trying to find out a good solution for better part of the past two days, it's been hard because there are so many variables: 1) how optimized are the code from either of the implementations 2) VM difference 3) HW etc. Also, there are quite a few dim

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769085#action_12769085 ] Mark Miller commented on LUCENE-1997: - bq. Java6 is standard in production servers, si

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 9:58 PM, Mark Miller wrote: > Yes - I've seen a handful of non core devs report back that they > upgraded with no complaints on the difficulty. Its in the mailing list > archives. The only core dev I've seen say its easy is Uwe. He's super > sharp though, so I wasn't banki

Hudson build is back to normal: Lucene-trunk #987

See - To unsubscribe, e-mail: java-dev-unsubscr...@lucene.apache.org For additional commands, e-mail: java-dev-h...@lucene.apache.org

Re: lucene 2.9 sorting algorithm

Jake Mannix wrote: > > > On Thu, Oct 22, 2009 at 9:25 PM, Mark Miller > wrote: > > >> he new API is much harder for the > >> average user to use, and even for the experienced user, it's not > terribly fun, > >> and more importantly: > > Do we have

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769060#action_12769060 ] Mark Miller commented on LUCENE-1997: - Same system, Java 1.6.0_15 ||Seg size||Query||

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769059#action_12769059 ] Yonik Seeley commented on LUCENE-1997: -- bq. Java6 is standard in production servers,

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769058#action_12769058 ] Jake Mannix commented on LUCENE-1997: - I would say that of course weighting more highl

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769056#action_12769056 ] Jake Mannix commented on LUCENE-1997: - Java6 is standard in production servers, since

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769055#action_12769055 ] Mark Miller commented on LUCENE-1997: - Hey John, did you pull from a wiki dump or use

[jira] Issue Comment Edited: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769055#action_12769055 ] Mark Miller edited comment on LUCENE-1997 at 10/23/09 4:37 AM: -

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 9:25 PM, Mark Miller wrote: > >> he new API is much harder for the > >> average user to use, and even for the experienced user, it's not > terribly fun, > >> and more importantly: > > Do we have enough info to support that though? All the cases I have seen > on the list, p

[jira] Issue Comment Edited: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769051#action_12769051 ] Mark Miller edited comment on LUCENE-1997 at 10/23/09 4:29 AM: -

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769053#action_12769053 ] Yonik Seeley commented on LUCENE-1997: -- While Java5 numbers are still important, I'd

Re: lucene 2.9 sorting algorithm

>> he new API is much harder for the >> average user to use, and even for the experienced user, it's not terribly fun, >> and more importantly: Do we have enough info to support that though? All the cases I have seen on the list, people have figured it out pretty easily - havn't really seen any co

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769051#action_12769051 ] Mark Miller commented on LUCENE-1997: - Another run: I made the changes to int/string

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 8:30 PM, Yonik Seeley wrote: > On Thu, Oct 22, 2009 at 11:11 PM, Jake Mannix > wrote: > > It's hard to read the column format, but if you look up above in the > thread > > from tonight, > > you can see that yes, for PQ sizes less than 100 elements, multiPQ is > > better, a

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 11:11 PM, Jake Mannix wrote: > It's hard to read the column format, but if you look up above in the thread > from tonight, > you can see that yes, for PQ sizes less than 100 elements, multiPQ is > better, and only > starts to be worse at around 100 for strings, and 50 for i

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769045#action_12769045 ] John Wang commented on LUCENE-1997: --- My machine HW spec: Model Name: MacBook Pro

Re: lucene 2.9 sorting algorithm

Hi Yonik I am, but I don't think I should. Even with branching etc., I should see that much of a consistent difference. I am traveling with my macbook pro, I wanted to eliminate all variables. It really does not make sense to me... -John On Thu, Oct 22, 2009 at 8:06 PM, Yonik Seeley wrote

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769042#action_12769042 ] Jake Mannix commented on LUCENE-1997: - Hah! Thanks for posting that, Mark! Much eas

[jira] Commented: (LUCENE-1997) Explore performance of multi-PQ vs single-PQ sorting API

[ https://issues.apache.org/jira/browse/LUCENE-1997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12769039#action_12769039 ] Mark Miller commented on LUCENE-1997: - Results from John Wang: ||Seg size||Query||Tot

Re: lucene 2.9 sorting algorithm

Of course, John's running on his mac laptop, which also may be a factor, which is another reason why he wanted to see if these carried over onto a linux desktop (for example). -jake On Thu, Oct 22, 2009 at 8:11 PM, Jake Mannix wrote: > It's hard to read the column format, but if you look up a

Re: lucene 2.9 sorting algorithm

It's hard to read the column format, but if you look up above in the thread from tonight, you can see that yes, for PQ sizes less than 100 elements, multiPQ is better, and only starts to be worse at around 100 for strings, and 50 for ints. -jake On Thu, Oct 22, 2009 at 8:06 PM, Yonik Seeley wro

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 10:35 PM, John Wang wrote: >        Please be patient with me. I am seeing a difference and was wondering > if Mike would see the same thing. Some differences are bound to be seen... with your changes (JVM changes, branch optimizations), are you seeing better average perfo

Re: lucene 2.9 sorting algorithm

bq. I just followed instructions in the jira and got it running. Heh - I didn't read down far enough - first comment says 2.9 branch. Thanks ; ) I've been flipping through revisions for a while now, wondering how the heck the revs in the patch match up with trunk. John Wang wrote: > Mark: > >

Re: lucene 2.9 sorting algorithm

John Wang wrote: > Mark: > >There is no reason for me to withhold information. I just want > to understand and share my findings. Right, I didn't mean to accuse you of that ;) Not that you were doing it on purpose. I was just trying to string out more :) Which I've managed to do - in my usu

Re: lucene 2.9 sorting algorithm

Mark: There is no reason for me to withhold information. I just want to understand and share my findings. My bad for not being clear. Mike's test is actually very well written, I just followed instructions in the jira and got it running. I think the tests has good coverage

Re: lucene 2.9 sorting algorithm

>> I guess I should be more clear in the email. No - If you mentioned before the other info and I missed it, just say: Mark you don't know what your talking about it and you missed the info. Thats what I'd do. You just caught me at a time when I'm trying to get these tests going myself, and a l

Re: lucene 2.9 sorting algorithm

For some reason I guess this didn't go thru and caused all the confusion. ||Seg size||Query||Tot hits||Sort||Top N||QPS old||QPS new||Pct change|| |log||100|rand string|10|91.76|108.63|{color:green}18.4%{color}| |log||100|rand string|25|92.39|106.79|{color:green}15.6%{color}| |log||100

Re: lucene 2.9 sorting algorithm

Mike: I did just post with what I saw, feel free to read and comment on it. I am simply trying to work with Michael on this and trying to understand the code. As I have expressed previously, I have seen a difference between 1.5 and 1.6 that is significant. Since Mike has post

Re: lucene 2.9 sorting algorithm

Thanks - thats all I'm asking for. A simple explanation of why you'd ask for a retest with those two things changed. Just seems its hold your cards a little to close to say - please do this with 0 explanation. As to point 2, thats fine - I'm sure it helps - I was just saying I didn't buy it helps

Re: lucene 2.9 sorting algorithm

I am patient :) And I'm not speaking for Mike, I'm speaking for me. I'm wondering what your seeing. Asking Mike to rerun the tests without giving any further info (you didn't even say that your seeing something different) is unfair to the rest of us ;) Giving 0 info along with your request just ma

Re: lucene 2.9 sorting algorithm

Mark, We're not seeing exactly the numbers that Mike is seeing in his tests, running with jdk 1.5 on intel macs, so we're trying to eliminate factors of difference. Point 2 does indeed make a difference, we've seen it, and it's only fair: the single pq comparator does this branch optimization

Re: lucene 2.9 sorting algorithm

Mark: Please be patient with me. I am seeing a difference and was wondering if Mike would see the same thing. I thought Michael would be willing to because he expressed interest in understanding what the performance discrepancies are. Again, it is only a request. It is perfectly fine

Re: lucene 2.9 sorting algorithm

Why? What might he find? Whats with the cryptic request? Why would Java 1.5 perform better than 1.6? It erases 20 and 40% gains? I know point 2 certainly doesn't. Cards on the table? John Wang wrote: > Hey Michael: > >Would you mind rerunning the test you have with jdk1.5? > >Als

Re: lucene 2.9 sorting algorithm

Hey Michael: Would you mind rerunning the test you have with jdk1.5? Also, if you would, change the comparator method to avoid brachning for int and string comparators, e.g. return index.order[i.doc] - index.order[j.doc]; Thanks -John On Thu, Oct 22, 2009 at 2:38 AM, Mic

[jira] Commented: (LUCENE-1960) Remove deprecated Field.Store.COMPRESS

[ https://issues.apache.org/jira/browse/LUCENE-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768916#action_12768916 ] Uwe Schindler commented on LUCENE-1960: --- I still prefer 1, but maybe it's not so goo

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768907#action_12768907 ] Uwe Schindler commented on LUCENE-2002: --- Looks good. bq. I didn't add Version to St

[jira] Updated: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless updated LUCENE-2002: --- Attachment: LUCENE-2002-29.patch New patch attached. All tests pass. Changes: *

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768889#action_12768889 ] Michael McCandless commented on LUCENE-2002: I think we are good: I just looke

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768878#action_12768878 ] Uwe Schindler commented on LUCENE-2002: --- Cool. Did you check the minimum ANT version

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768874#action_12768874 ] Michael McCandless commented on LUCENE-2002: bq. Maybe the search-replace with

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768866#action_12768866 ] Mark Miller commented on LUCENE-2003: - bq. The "total" would almost seem to tip the am

[jira] Assigned: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless reassigned LUCENE-2003: -- Assignee: Mark Miller (was: Michael McCandless) OK Mark you get this one :)

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768863#action_12768863 ] Yonik Seeley commented on LUCENE-2003: -- bq. You only need to add to the slop the larg

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768862#action_12768862 ] Mark Miller commented on LUCENE-2003: - Okay - I think this is the way to go - maxPos-

[jira] Updated: (LUCENE-1257) Port to Java5

[ https://issues.apache.org/jira/browse/LUCENE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated LUCENE-1257: Attachment: LUCENE-1257_unnnecessary_casts_2.patch > Port to Java5 > - > > Key

[jira] Updated: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-2003: Attachment: LUCENE-2003.patch This should be more correct - add the largest inc to the slop if its

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768853#action_12768853 ] Mark Miller commented on LUCENE-2003: - Hmm - well now you have me worried - never seen

[jira] Issue Comment Edited: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768845#action_12768845 ] Uwe Schindler edited comment on LUCENE-2002 at 10/22/09 7:59 PM: ---

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768843#action_12768843 ] Yonik Seeley commented on LUCENE-2003: -- Could you explain this part? {code} +

[jira] Resolved: (LUCENE-1373) Most of the contributed Analyzers suffer from invalid recognition of acronyms.

[ https://issues.apache.org/jira/browse/LUCENE-1373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1373. Resolution: Duplicate Dup of LUCENE-2002. > Most of the contributed Analyzers suf

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768845#action_12768845 ] Uwe Schindler commented on LUCENE-2002: --- Eric Hatcher :-) Maybe the search-replace

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768840#action_12768840 ] Michael McCandless commented on LUCENE-2002: bq. We may want to see if it can

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768838#action_12768838 ] Grant Ingersoll commented on LUCENE-2002: - bq. OK I'll take that approach, and I g

[jira] Updated: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller updated LUCENE-2003: Attachment: LUCENE-2003.patch Here is a patch showing essentially what I mean > Highlighter has p

[jira] Issue Comment Edited: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768829#action_12768829 ] Mark Miller edited comment on LUCENE-2003 at 10/22/09 7:40 PM: -

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768829#action_12768829 ] Mark Miller commented on LUCENE-2003: - Well no crap - MultiPhraseQuery already does th

[jira] Commented: (LUCENE-2003) Highlighter has problems when you use StandardAnalyzer with LUCENE_29 or simplier StopFilter with stopWordsPosIncr mode switched on

[ https://issues.apache.org/jira/browse/LUCENE-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768827#action_12768827 ] Mark Miller commented on LUCENE-2003: - Umm - its hard to emulate the positions stuff f

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768815#action_12768815 ] Glen Newton commented on LUCENE-2005: - Yes, it was just concerned with adding hyperlin

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768810#action_12768810 ] Robert Muir commented on LUCENE-2005: - bq. Right... and I think we really shouldn't tr

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768805#action_12768805 ] Michael McCandless commented on LUCENE-2005: bq. Michael, actually this issue

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768795#action_12768795 ] Yonik Seeley commented on LUCENE-2005: -- bq. Michael, actually this issue was just to

[jira] Updated: (LUCENE-1257) Port to Java5

[ https://issues.apache.org/jira/browse/LUCENE-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kay Kay updated LUCENE-1257: Attachment: LUCENE-1257_contrib_benchmark.patch > Port to Java5 > - > > Key: L

contrib and lucene 3.0

Hi, What is the consensus on new features for contrib for Lucene 3.0? I know that for core, its mostly a java 5 upgrade and deprecation removal. I want to make sure LUCENE-1606 is set to the right version, but I figured its really not just about that specific issue, I would like to know the plans

[jira] Resolved: (LUCENE-1258) Increment position by default in StopFilter & QueryParser -> PhraseQuery

[ https://issues.apache.org/jira/browse/LUCENE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael McCandless resolved LUCENE-1258. Resolution: Duplicate Dup of LUCENE-2002. > Increment position by default in Stop

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768752#action_12768752 ] Michael McCandless commented on LUCENE-2002: bq. Michael, what about LUCENE-1

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768749#action_12768749 ] Robert Muir commented on LUCENE-2005: - bq. LuSql looks great! It'd be wonderful to hav

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768746#action_12768746 ] Michael McCandless commented on LUCENE-2005: LuSql looks great! It'd be wonde

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768747#action_12768747 ] Robert Muir commented on LUCENE-2002: - bq. Ahh yes indeed. Is there a corresponding is

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768745#action_12768745 ] Robert Muir commented on LUCENE-2005: - Glen, I think it would be good to bring the co

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768744#action_12768744 ] Michael McCandless commented on LUCENE-2002: bq. Michael, if you do this, can

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768743#action_12768743 ] Glen Newton commented on LUCENE-2005: - [DBSight|http://www.dbsight.net/] is a commerci

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768740#action_12768740 ] Robert Muir commented on LUCENE-2002: - {quote} Or, with this issue I could add Version

[jira] Commented: (LUCENE-1606) Automaton Query/Filter (scalable regex)

[ https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768739#action_12768739 ] Uwe Schindler commented on LUCENE-1606: --- 3.0 is just the switch to 1.5 and generics.

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768738#action_12768738 ] Michael McCandless commented on LUCENE-2002: bq. Many analyzers can use a stop

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768733#action_12768733 ] Michael McCandless commented on LUCENE-2002: bq. Thus, I think, unfortunately,

[jira] Commented: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768727#action_12768727 ] Robert Muir commented on LUCENE-2005: - glen, I know there is an oracle domain index im

How to loop through all the entries for a field

I have a field in called BookTitle. I want to loop through all the entries without doing a search. I just want to get the list of BookTitle's that is in this field: I tried IndexReader but MaxDocs() doesnt work because it returns everything and I have other fields in their which is allot bigger

[jira] Updated: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

[ https://issues.apache.org/jira/browse/LUCENE-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Glen Newton updated LUCENE-2005: Description: Add [LuSql|http://lab.cisti-icist.nrc-cnrc.gc.ca/cistilabswiki/index.php/LuSql] to t

[jira] Created: (LUCENE-2005) Add LuSql project to "Apache Lucene - Contributions" wiki page

Add LuSql project to "Apache Lucene - Contributions" wiki page -- Key: LUCENE-2005 URL: https://issues.apache.org/jira/browse/LUCENE-2005 Project: Lucene - Java Issue Type: Task

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768717#action_12768717 ] Grant Ingersoll commented on LUCENE-2002: - {quote}Unfortunately, JavaCC generates

[jira] Commented: (LUCENE-2002) Add oal.util.Version ctor to QueryParser

[ https://issues.apache.org/jira/browse/LUCENE-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768711#action_12768711 ] Mark Miller commented on LUCENE-2002: - I think we need more doc as well - stopfilter i

[jira] Commented: (LUCENE-1606) Automaton Query/Filter (scalable regex)

[ https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768705#action_12768705 ] Robert Muir commented on LUCENE-1606: - Grant, I thought it was ok from Uwe's comment:

[jira] Commented: (LUCENE-1606) Automaton Query/Filter (scalable regex)

[ https://issues.apache.org/jira/browse/LUCENE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768700#action_12768700 ] Grant Ingersoll commented on LUCENE-1606: - Why are new features going into 3.0? I

[jira] Resolved: (LUCENE-2001) wordnet parsing bug

[ https://issues.apache.org/jira/browse/LUCENE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll resolved LUCENE-2001. - Resolution: Fixed Committed revision 828728. > wordnet parsing bug > --

[jira] Commented: (LUCENE-2001) wordnet parsing bug

[ https://issues.apache.org/jira/browse/LUCENE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768695#action_12768695 ] Grant Ingersoll commented on LUCENE-2001: - I'll take care of the branch. > wordne

[jira] Assigned: (LUCENE-2001) wordnet parsing bug

[ https://issues.apache.org/jira/browse/LUCENE-2001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll reassigned LUCENE-2001: --- Assignee: Grant Ingersoll > wordnet parsing bug > --- > >

[jira] Commented: (LUCENE-1973) Remove deprecated query components

[ https://issues.apache.org/jira/browse/LUCENE-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768661#action_12768661 ] Uwe Schindler commented on LUCENE-1973: --- Anybody wants to help? > Remove deprecated

RE: svn commit: r828334 - /lucene/java/branches/lucene_2_9_back_compat_tests/src/test/org/apache/lucene/index/TestCheckIndex.java

Done! - Uwe Schindler H.-H.-Meier-Allee 63, D-28213 Bremen http://www.thetaphi.de eMail: u...@thetaphi.de > -Original Message- > From: Michael McCandless [mailto:luc...@mikemccandless.com] > Sent: Thursday, October 22, 2009 11:39 AM > To: java-dev@lucene.apache.org > Subject: Re: svn

Re: svn commit: r828334 - /lucene/java/branches/lucene_2_9_back_compat_tests/src/test/org/apache/lucene/index/TestCheckIndex.java

OK let's do first! Mike On Thu, Oct 22, 2009 at 5:31 AM, Uwe Schindler wrote: >> Putting the LUCENE_VERSION in front of the string instead of in back seems >> fine? > > I would prefer this, as it makes it possible to do compareTo() comparisons > and so on, which may be used in client code, too (

Re: lucene 2.9 sorting algorithm

On Thu, Oct 22, 2009 at 2:17 AM, John Wang wrote: > I have been playing with the patch, and I think I have some information > that you might like. > Let me spend sometime and gather some more numbers and update in jira. Excellent! > say bottom has ords 23, 45, 76, each correspond

  1   2   >