Am 13.03.2013 10:23, schrieb dizh:
I just recompile it.
Luckily, It doesn't need to do much work. Only a few modifications according
to Lucene4.1 API change doc.
That's great news. Are you going to publish a ready-made version somewhere?
Also, I've made the experience that Luke 4.0.0-ALPHA
OK , tomorrow I will put it on spmewhere such as GitHub or googlecode.
But, I really don't look into details, when I compile Luke src , I found about
ten's errors.
Most are TermEnums API , so I fixed them.
So judging from the (lack of) response so far it seems Luke development
has stopped (last update on Google code is from August 2012) and it is now
up to anyone to adopt te code.
And... Luke / Lucene 4.2 is not just a matter of recompile.
Wouter
Am 13.03.2013 10:23, schrieb dizh:
I just
I compile 4.1
4.2 change a lot ??
I really think Luke should be in control of Lucene developer teams.
---
Confidentiality Notice: The information contained in this e-mail and any
accompanying
DocValues is the main problem in 4.2/Luke.
For 4.1 there is a working Luke on github:
https://github.com/mingfai/luke
Wouter
I compile 4.1
4.2 change a lot ??
I really think Luke should be in control of Lucene developer teams.
OK , Thank you !
Anyone saw my last question ? Lucene Pagination
Look for a deepy answer.
---
Confidentiality Notice: The information contained in this e-mail and any
accompanying attachment(s)
is
On Thu, 2013-03-14 at 04:11 +0100, dizh wrote:
each document has a timestamp identify the time which it is indexed, I
want search the documents using sort, the sort field is the timestamp,
[...]
but when you do paging, for example in a web app , the user want to go
to the last
On Thu, 2013-03-14 at 11:03 +0100, Toke Eskildsen wrote:
(timestamp_in_ms 10) counter++
This should be
(timestamp_in_ms 10) | counter++
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional
You could also use Lucene's search after capability.
It's designed for exactly this use-case (deep paging).
See https://issues.apache.org/jira/browse/LUCENE-2215
Mike McCandless
http://blog.mikemccandless.com
On Thu, Mar 14, 2013 at 6:03 AM, Toke Eskildsen t...@statsbiblioteket.dk
wrote:
On
Hi list,
a stupid question about the naming of the index files.
While using lucene (and solr) 4.2 I still see files with Lucene41 in the name.
This is somewhat confusing if lucene 4.x produces files with Lucene4y.
This also means indexes built with 4.2 or 4.3 are fully compatible with 4.1 ?
On Thu, Mar 14, 2013 at 7:22 AM, Bernd Fehling
bernd.fehl...@uni-bielefeld.de wrote:
Hi list,
a stupid question about the naming of the index files.
While using lucene (and solr) 4.2 I still see files with Lucene41 in the
name.
This is somewhat confusing if lucene 4.x produces files with
Could you give us some examples of what you expect? I mean, how is your
suggested set of documents any different from simply executing a query with
the list of suggested terms (using q.op=OR)?
Or, maybe you want something like MoreLikeThis?
-- Jack Krupansky
-Original Message-
From:
Let's refine this...
If a top suggestion is X, do you simply want to know a few of the documents
which have the highest term frequency for X?
Or is there some other term-oriented metric you might propose?
-- Jack Krupansky
-Original Message-
From: Bratislav Stojanovic
Sent:
Hi Bratislav,
LUCENE-4517 sounds like what you want:
https://issues.apache.org/jira/browse/LUCENE-4517: Suggesters: allow to pass
a user-defined predicate/filter to the completion searcher
There's a patch there, against Lucene trunk from about 5 months ago, so if you
want to give it a try
On Tue, Mar 12, 2013 at 10:42 PM, Hu Jing huj@gmail.com wrote:
so my question is how to achieve a non-sort query method, this method can
get result constantly and don't travel all unnecessary doc.
Does Lucene supply some strategies to implement this?
If you want the result as soon as
15 matches
Mail list logo
