Hey Mike,
That was a very useful response, also for long time Lucene users like
myself who were stuck in legacy ways of doing things!
I managed to easily change indexing of keys to DocValues and found myself
wondering why I did not get anything returned, it appears indexing works
transparent to an
Hi,
I would index it in a field, you can use the database id and even add
additional information so compose your own key and retrieve that (only)
when you collect search results.
Wouter
> Hi,
>
> what is the best way to retrieve our "real" ids (as they are in our
> database) while searching?
>
>
Great to read this, there is hope!
And Luke definitely deserves to be a Lucene module.
Wouter
> If anyone is able to donate some effort, a nice future scenario could be
> that Luke comes fully up to date with every Lucene release:
> https://issues.apache.org/jira/browse/LUCENE-2562
>
> - Mark
>
>
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.
--
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 recom
Anybody knows what is happening to Luke?
Staying with the latest Lucene has become a risk since Luke seems to stay
behind of the Lucene development.
For 4.1 it was possible to find a patch on github, for 4.2 DocValues are
broken in Luke.
Wouter
-
Hi,
We use a solution where we have our own implementation similar to
ASCIIFoldingFilter for German language specific characters (and also
French and Dutch).
Wouter
> Hello,
>
> I have two questin regarding handling German umlauts in Lucene:
>
> 1. I'm trying to find a way to convert German Umlau
Hi,
We faced a similar problem.
The solution was to give the indexer less work and let worker threads do
all the work. They would result in pre-processed/analyzed/tokenized
Documents that could be indexed by the writer without any processing.
Wouter
> Hi
>
> the file to be indexed depends on the
Hi Grant,
These are 2 cases into work i've done that I can think of:
-use Lucene to match products in a database with eBay auctions, the title
of the auction is used as the query to Lucene.
-use a servlet filter and Lucene to map well-formed URL's into a website
to it's individual (product) page
I'm doing the upgrade to Lucene 3.1.0.
The upgrade failed on WhitespaceTokenizer being final in this version.
I don't understand why anyone would make this tokenizer final, I was
happlily extending it for many Lucene versions!
Wouter
-
Hi,
Same here, don't want Solr, so if you want facets BoBo is your friend!
http://sna-projects.com/bobo/
Works great, very easy to use...the only thing is the name, is like dog
food :-)
But give BoBo a try!
Wouter
> Hello all,
>
> I am using Lucene for my project and we have new requirement to
>
> Where do you get your Lucene/Solr downloads from?
>
> [] ASF Mirrors (linked in our release announcements or via the Lucene
> website)
>
> [X] Maven repository (whether you use Maven, Ant+Ivy, Buildr, etc.)
>
> [] I/we build them from source via an SVN/Git checkout.
>
> [] Other (someone in you
llector, use the doc number to get the filename from
> the
> cache. I think the speed improve will be >>10 times as fast!
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>> -Original Mes
Will this do?
IndexReader indexReader = searcher.getIndexReader();
TopDocs topDocs = searcher.search(Query query, int n);
for (int i = 0; i < topDocs.scoreDocs.length; i++) {
Document document = indexReader.document( topDocs.scoreDocs[i].doc);
final File f = new File( document.get( "FILE" ) )
Hi,
It sounds to me that you are highlighting the query string and not the
document. You will have to pass the document's content to
getBestFragments() and it will work I think.
Wouter
> hi there,
> I am using lucene highlighter to highlight the searched result
> but it shows only the query s
i came across that one, only the java doc says that it is expensive so I
was hoping for a less expensive solution...
Wouter
> searcher.explain definitely seems to do the trick, going through the
> sub-queries.
>
> paul
>
>
> Le 23-mars-09 à 13:12, Wouter Heijke a écrit :
&g
I want to know for each term in a query if it matched the result or not.
What is the best way to implement this?
Highlighter seems to be able to do the trick only that I don't need to
'highlight' any text. After knowing if terms in the query matched I want
do do something else based on this.
Woute
This is 2.9 code.
For 2.4 you're stuck with the system property.
Wouter
> Thanks!
> -John
>
> On Thu, Dec 4, 2008 at 2:16 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
>> Details in the bug:
>> https://issues.apache.org/jira/browse/LUCENE-1451
>>
>> Use this constructor to create an instance of N
I had the same problem, only got it to work when I set the system property
the way you do... UGLY!
So if there is a solution like you ask for that use 2.4 I would be
interested to know as well.
Wouter
> That does not help. The File/path is not stored with the instance. It is
> in
> a map FSDirect
19 matches
Mail list logo
