[
https://issues.apache.org/jira/browse/LUCENE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-790:
---
Attachment: TrecDocMaker.patch
Attached TrecDocMaker.patch also contains the changes in current patch
[
https://issues.apache.org/jira/browse/LUCENE-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doron Cohen updated LUCENE-790:
---
Lucene Fields: [Patch Available] (was: [New])
> contrib/benchmark - few improvements and a bug fix
>
Antony Bowesman wrote:
Yonik Seeley wrote:
Lucene 2.1 has been a long time in coming, but I think we should plan
on making a release when the file format changes settle down.
Was there any kind of consensus of what 'soon' meant. Is it likely to
be days, this month, or sometime later? I'd re
Michael McCandless wrote:
I plan on committing this one today. Once that's in I think we can
and should get the release process going (Yonik had graciously
volunteered to be the release manager)?
+1 for starting the release process. Especially the big new features
"lazy field loading", "lock
[
https://issues.apache.org/jira/browse/LUCENE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael McCandless resolved LUCENE-565.
---
Resolution: Fixed
Fix Version/s: 2.1
I just committed this.
Thank you Ning.
Update the Wiki
---
Key: LUCENE-791
URL: https://issues.apache.org/jira/browse/LUCENE-791
Project: Lucene - Java
Issue Type: Improvement
Components: Website
Reporter: Grant Ingersoll
Priority: Mi
-1
I would like a few more days to get https://issues.apache.org/jira/
browse/LUCENE-762, as it may involve moving some classes and I don't
want to do that after an official release. It is not a major issue,
but I do think it is important to get right before the release.
Sorry for the de
Michael Busch wrote:
Michael McCandless wrote:
I plan on committing this one today. Once that's in I think we can
and should get the release process going (Yonik had graciously
volunteered to be the release manager)?
+1 for starting the release process. Especially the big new features
"lazy
The Lucene PMC has voted to add Michael Busch as a Lucene committer.
Welcome, Michael!
Doug
P.S. The traditional initiation ritual is to add yourself to the "Who We
Are" page's source, then re-generate and re-publish the site.
-
Welcome aboard, Michael!
So how about keeping the new-committer-introduction tradition alive :-)
-Yonik
On 2/1/07, Doug Cutting <[EMAIL PROTECTED]> wrote:
The Lucene PMC has voted to add Michael Busch as a Lucene committer.
Welcome, Michael!
Doug
---
Dear all
I am happy to send my first email to Lucene community after some time
standing aside, following many interesting discussions.
As part of my school project, I am intending to make some improvements in
Lucene source code, and I need some advices on how significance my
modification work wo
On 2/1/07, Thang Luong Minh <[EMAIL PROTECTED]> wrote:
I'm thinking of replace the byte-aligned scheme with the "fixed binary"
coding scheme mentioned in the paper "Index compression using Fixed Binary
Codewords" by Vo Ngoc Anh and Alistair Moffat (the abstract can be found
here
http://www.cs.m
Hi All,
I am new to LUCENE,I have an query that, I have to index a Product table,
Suppose that table has following Columns.
product [ prod_Id as primary key, prod_name, prod_price]
I have an requirement like if someone searches for prod_id or prod_price, I
have to fetch the rows( pr
On 1/25/07, Grant Ingersoll <[EMAIL PROTECTED]> wrote:
Mike,
Do you have any preference on making FieldInfo public versus moving
the FieldSelector stuff into the index package?
Not at all. Our use is pretty basic as will be easy to modify to
conform to class movement/renaming.
-Mike
---
I have discovered a serious bug in QueryParser. The following query:
contents:sales && contents:marketing || contents:industrial &&
contents:sales
is parsed as:
+contents:sales +contents:marketing +contents:industrial +contents:sales
The same parsed query occurs even with parenthesis:
(contents:
Correction:
The query parser produces the correct query with the parenthesis.
But, I'm still looking for a fix for this. I could use some advice on where
to look in QueryParser to fix this.
Thanks,
Peter
On 2/1/07, Peter Keegan <[EMAIL PROTECTED]> wrote:
I have discovered a serious bug in Que
Welcome Michael! You're a tremendous asset to the Lucene community,
and you've just made lives of the other hardcore committers (myself
most definitely excluded) a lot easier. You knocked my socks off in
person. You and your team are amazing. I'm so thankful of the
amazing community we
On Feb 1, 2007, at 12:24 PM, Yonik Seeley wrote:
Welcome aboard, Michael!
So how about keeping the new-committer-introduction tradition
alive :-)
Here's a new tradition we can start...
"Hi, my name is Erik, I write shitty code."
[
https://issues.apache.org/jira/browse/LUCENE-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12469586
]
Daniel Naber commented on LUCENE-791:
-
I consider it important for old urls to still work after the move. If this
OK, I see that I'm not the first to discover this behavior of QueryParser.
Can anyone vouch for the integrity of the PrecedenceQueryParser here:
http://svn.apache.org/repos/asf/lucene/java/trunk/contrib/miscellaneous/src/java/org/apache/lucene/queryParser/precedence/
Thanks,
Peter
On 2/1/07, Pe
Dear all,
My primary research interest is Information retrieval, with a focus on
developing
effective and robust retrieval models. I am happy to send my first email
to Lucene community.
Lucene and nutch are really useful IR systems. But I think that the current
retrieval function
implemented in
more then once, people have suggested that QueryParser should either throw
and Exception or implicitly put a MatchAllDocsQuery in any BooleanQuery it
produces when the string it's parsing contains entirely negative clauses.
I've argued against this idea because QueryParser doesn't know how the
Qu
22 matches
Mail list logo
