I'd like to commit the following two submissions...
http://issues.apache.org/jira/browse/LUCENE-496
http://issues.apache.org/jira/browse/LUCENE-577
...but it's not clear to me wether the best time to do that is before or
after the 2.0 release:
* neither patch fixes a bug, which suggests i shoul
Greetings,
I am struggling with the following. Say I want to use Lucene to search a
corporate phone book where I have workers from a database:
Workers
---
John Douglas
Davis Raymond
My first thought was to create a field called workers and put all the names
in it:
worker: john douglas da
I think having these committed to the contrib area is ok prior to
2.0. Let's see what others say.
Erik
On May 25, 2006, at 4:13 AM, Chris Hostetter wrote:
I'd like to commit the following two submissions...
http://issues.apache.org/jira/browse/LUCENE-496
http://issues.apache.org/
Summer of Code GDATA Server --Project structure and simple version to start
with--
---
Key: LUCENE-578
URL: http://issues.apache.org/jira/browse/LUCENE-578
Project: Lucene - Java
Type:
JMA,
I think you will find that multiple fields are beneficial. However, a
simple answer to your question, and one that is needed even for your
examples of multiple values in a single field, is to use a position
increment gap. See Analyzer.getPositionIncrementGap().
When you use multiple values
[ http://issues.apache.org/jira/browse/LUCENE-578?page=all ]
Simon Willnauer updated LUCENE-578:
---
Attachment: diff.txt
diff file - containing the package structure and a simple version to start with.
> Summer of Code GDATA Server --Project structure
[ http://issues.apache.org/jira/browse/LUCENE-578?page=all ]
Simon Willnauer updated LUCENE-578:
---
Attachment: libs.tar.gz
jar files from the lib directory
> Summer of Code GDATA Server --Project structure and simple version to start
> with--
>
Chris Hostetter wrote:
My gut says go ahead and commit them (ASAP if the plan is to release 2.0
this weekend), but as the guy that submited both of them, i feel like
maybe i'm not the most impartial person to decide.
+1
For new code that cannot break existing functionality the bar is lower.
D
[ http://issues.apache.org/jira/browse/LUCENE-496?page=all ]
Hoss Man resolved LUCENE-496:
-
Fix Version: 2.0
Resolution: Fixed
Assign To: Hoss Man
Commited with some small documentation additions.
> New tool for reseting the (length)norm of
I followed the instruction in wiki and generated an patch file, which I attach to this email.But I did not find where to upload this patch file in JIRA bug report.Can someone help me?
On 5/17/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
: I put Lock in IndexReader.indexExists function, and testes
You have to fill in the fields provided and finish up the two steps to
insert the bugreport. When you have finished your report you can
upload your file as an attachment to the report.
It's on the left hand side of your screen "operations --> attache file
to this issue"
simon
On 5/25/06, wenjie
On Thursday 25 May 2006 22:14, wenjie zheng wrote:
> I followed the instruction in wiki and generated an patch file, which I
> attach to this email.
> But I did not find where to upload this patch file in JIRA bug report.
Only after the JIRA issue has been created, a file can be attached.
For an
[
http://issues.apache.org/jira/browse/LUCENE-578?page=comments#action_12413304 ]
Doug Cutting commented on LUCENE-578:
-
Simon,
This looks great. I am going to wait to commit it until after tomorrow, when
we make the 2.0 release. Not that adding this
TermPositionVector offsets incorrect if indexed field has multiple values and
one ends with non-term chars
--
Key: LUCENE-579
URL: http://issues.apache.org/jira/browse/LUCENE-
[ http://issues.apache.org/jira/browse/LUCENE-577?page=all ]
Hoss Man resolved LUCENE-577:
-
Fix Version: 2.0
Resolution: Fixed
Assign To: Hoss Man
Commited with some small changes: mainly adding Apache Copyright/License and
switching the def
15 matches
Mail list logo
