Hi,
In my index, there is a field called timestamp which is long value of date.
I am trying to get sort all documents by timestamp and get N documents.
I am trying to find a way to create a query like "timestamp > 0" and then order
the result by timestamp and get N fields. However I am not a
Hi,
if you have the document number then you can get the document by using
searcher = getSearcher();
document = searcher.doc(document number);
Prabin
On Mon, Nov 10, 2008 at 11:03 AM, fernanvi
<[EMAIL PROTECTED]>wrote:
>
> Hello.
> I am trying to obtain a Document to work directly on it.
> I h
Hello.
I am trying to obtain a Document to work directly on it.
I have already the id number, but I do not know obtain like the object
Document from this number id.
...
while (td.next()) {
int docNum = td.doc();// document number
.
I need get the docNum Document.
Tha
Excuse me. Some unchecked logic there concerning HitCollector. A
HitCollector hits all matching documents, not all documents. Sometimes
that can be a lot. With TopDocs, you only ask for the Top scoring
documents, which is usually a lesser number than all matching docs, and
generally what people
Their is definitely some stale javadoc in Lucene here and there. All of
what your talking about has been shaken up recently with the deprecation
of Hits. Hits used to pretty much be considered the non-expert API, but
its been tossed in favor of the TopDoc API's.
The HitCollector stuff has been
In fact, the search method used to populate the collector used in that
sample code also claims to be low level. It suggests using the
IndexSearcher.search( query ) method instead, but that method is deprecated.
Lower-level search API.
>
> HitCollector.collect(int,float) is called for every matchi
The sample code uses a ScoreDoc array to hold the hits.
ScoreDoc[] hits = collector.topDocs().scoreDocs;
But the JavaDoc says "Expert: Returned by low-level search
implementations." Why would the tutorial sample code use an "expert" api?
On Freitag, 7. November 2008, ChadDavis wrote:
> For
> example, Field.Keyword() is gone. Shouldn't I find this in that change
> log?
This was removed between 1.9 and 2.0. The plan was that users upgrade to
1.9, fix the deprecation warnings and only then go to 2.0. Thus no every
method is ment
There were several big ommissions.
On Sun, Nov 9, 2008 at 1:08 PM, Michael McCandless <
[EMAIL PROTECTED]> wrote:
>
> Yes you should have found this in the CHANGES.txt: we try hard to document
> all changes as we commit them.
>
> I looked and also could not find it. I'm not sure why it's missing
Conceivably, TermInfosReader could track the sequence number of each
term.
A seek/skipTo would know which sequence number it just jumped too,
because the index is regular (every 128 terms by default), and then
each next() call could increment that. Then retrieving this number
would be
Yes you should have found this in the CHANGES.txt: we try hard to
document all changes as we commit them.
I looked and also could not find it. I'm not sure why it's missing
(it was before my time!).
Mike
ChadDavis wrote:
I'm upgrading from a very old version of lucene to 2.4 I tried t
Op Sunday 09 November 2008 11:56:37 schreef markharw00d:
> >>this can't be nearly as fast as OpenBitSet.intersect() or union,
>
> respectively, can it?
>
> I had a similar concern but it doesn't seem that bad:
>
>
> https://issues.apache.org/jira/browse/LUCENE-1187?focusedCommentId=12
>596546#acti
>>this can't be nearly as fast as OpenBitSet.intersect() or union,
respectively, can it?
I had a similar concern but it doesn't seem that bad:
https://issues.apache.org/jira/browse/LUCENE-1187?focusedCommentId=12596546#action_12596546
The above test showed a slight improvement using bitset
On Saturday 08 November 2008 22:12:12 Paul Elschot wrote:
> Timo,
>
> You may be looking for class OpenBitSetDisi in the util package,
> it was made for boolean filter operations on OpenBitSets.
> Also have a look at the contrib modules, OpenBitSetDisi is
Okay, this is the third solution that is a
You can use a ContextListener in a servlet engine (like Tomcat) .
ContextListener has callback methods for init an destroy. You may open
an IndexSearcher in the init and store it in the ServletContext by a
name and every servlet can use that. When the app is stopped you get a
calllback and you can
15 matches
Mail list logo
