Hello to every body
I have integrated Lucene into a knowledge software, the main goal of lucene
will be to index and search files given by this knowledge software.
My problem now is, I need to get back from lucene text "snippets" where the
search query has been found and it should be highlighted
[ http://issues.apache.org/jira/browse/LUCENE-534?page=all ]
Karl Wettin updated LUCENE-534:
---
Attachment: se.snigel.lucene.crud.tar.gz
updated
> CRUD facade on top of Lucene
>
>
> Key: LUCENE-534
> URL: http:
[ http://issues.apache.org/jira/browse/LUCENE-534?page=all ]
Karl Wettin updated LUCENE-534:
---
Attachment: se.snigel.lucene.crud.tar.gz
my CRUD pattern
> CRUD facade on top of Lucene
>
>
> Key: LUCENE-534
> UR
CRUD facade on top of Lucene
Key: LUCENE-534
URL: http://issues.apache.org/jira/browse/LUCENE-534
Project: Lucene - Java
Type: New Feature
Reporter: Karl Wettin
Priority: Minor
29 mar 2006 kl. 15.43 Erik Hatcher wrote:
Lazy loa
Grant Ingersoll wrote:
My main
concern is the semantics of the fieldsStream and whether that would be
closed behind the back of the LazyField implementation. My
understanding is that as long as the IndexReader is open, this stream
should also be open. Is that correct? What am I forgetting
[
http://issues.apache.org/jira/browse/LUCENE-413?page=comments#action_12372299 ]
paul.elschot commented on LUCENE-413:
-
The date doesn't show up in the list of the attachments until clicking the
"manage" link.
Today's patch is called DisjunctionSumScor
[ http://issues.apache.org/jira/browse/LUCENE-413?page=all ]
paul.elschot updated LUCENE-413:
Attachment: DisjunctionSumScorerPatch5.txt
Patch for org.apache.lucene.search.DisjunctionSumScorer.java .
This query was reported by Ramana Jelda on java-user
Of course, another option is to make all fields lazy all the time and
the user never even needs to think about it. Need some strategy for
when the IndexReader gets closed, but we have this in all cases.
Donovan Aaron wrote:
I've done a lot of work with Verity's search engine, and I like the
I've done a lot of work with Verity's search engine, and I like the way
they handle fields. At query time you specify the fields you want
returned from matching documents.
Aaron
-Original Message-
From: Grant Ingersoll [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 9:05 AM
To
Hmmm, I guess I always thought of it as a property of the field that
user's would want to explicitly control. I assumed that most fields
would not be lazy and a few would be.
Now that you have backed me up a bit on it (in a good way), I think it
could just as easily be a parameter that any fiel
Lazy loaded fields will be a nice addition to Lucene. I'm curious
why the flag is set at indexing time rather than it being something
that is controlled during retrieval somehow. I'm not sure what that
API would look like, but it seems its a decision to be addressed
during searching and
I have a base implementation of lazy field loading that I am starting to
test and wanted to run my approach by everyone to hear their thoughts.
I have, as per Doug's suggestion from a while ago, created an interface
named Fieldable that is implemented by Field and a new, private class,
owned b
SpanQuery scoring: SpanWeight lacks a recursive traversal of the query tree
---
Key: LUCENE-533
URL: http://issues.apache.org/jira/browse/LUCENE-533
Project: Lucene - Java
Type: Bug
Components:
13 matches
Mail list logo