You are probably not creating a query correctly. Are you creating a
query with IntPoint#newExactQuery?
On Wed, Jan 23, 2019 at 3:52 PM Ayuketah David Tabi
wrote:
>
>
>
> Greetings.
> I am using Lucene 7.6.
> To do indexing i am using StandardAnalyzer()
> and to index a numeric field this is what
Hi,
I would recommend to first upgrade to Lucene 3.6. The changes to that version
are much easier to do, because you can do the following migration steps: Remove
any deprecated code from your classes (so carefully remove any deprecation
warning when compiling your code with 2.9 - after that it
Are you able to reindex the data from source? Typical practices around
search indexes is to treat them as secondary stores for full-text search
that mirrors a primary database or data store.
-Doug
On Thu, Mar 20, 2014 at 12:52 PM, NarasimhaRao DPNV <
narasimha.jav...@gmail.com> wrote:
> Hi
>
>
Just add the lucene jar files in the build path of the project.
On Sat, Sep 28, 2013 at 5:04 PM, sajad naderi wrote:
> hi
> i want run code sample of "lucene in action"book by eclipse
> please tell me how configure eclipse to run those code
>
ier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Chris Zhang [mailto:zhangjcm...@gmail.com]
> Sent: Sunday, July 07, 2013 6:26 PM
> To: java-user@lucene.apache.org
> Subject: Re: Please Help solve problem of bad read
ge" engines.
>> Has someone claimed otherwise to you?
>>
>> What is your query performance in in 4.x vs. 3.x? That's the true, proper
>> measure of Lucene and Solr performance.
>>
>> -- Jack Krupansky
>>
>> -Original Message----- From: Chris Zhan
ry performance in in 4.x vs. 3.x? That's the true, proper
> measure of Lucene and Solr performance.
>
> -- Jack Krupansky
>
> -Original Message- From: Chris Zhang
> Sent: Sunday, July 07, 2013 12:26 PM
> To: java-user@lucene.apache.org
> Subject: Re: Please
e-
From: Chris Zhang
Sent: Sunday, July 07, 2013 12:26 PM
To: java-user@lucene.apache.org
Subject: Re: Please Help solve problem of bad read performance in lucene
4.2.1
thianks Adrien,
In my project, almost all hit docs are supposed to be fetched for every
query, what's why I am upset b
thianks Adrien,
In my project, almost all hit docs are supposed to be fetched for every
query, what's why I am upset by the poor reading performance. Maybe I
should store field values which are expected to be stored in high
performance storage engine.
In the above test case, time consuming of readi
Indeed, Lucene 4.1+ may be a bit slower for indices that comptelely
fit in your file-system cache. On the other hand, you should see
better performance with indices which are larger than the amount of
physical memory of your machine. Your reading benchmark only measures
IndexReader.get(int) which s
thank you very much :)
> Date: Mon, 27 May 2013 16:19:18 -0400
> Subject: Re: please help
> From: brendan.grain...@gmail.com
> To: java-user@lucene.apache.org
>
> Java is telling you the issue there. You're trying to cast a
> StandardDirectoryReader to an AtomicReader.
Java is telling you the issue there. You're trying to cast a
StandardDirectoryReader to an AtomicReader. I think AtomicReaders are per
segment readers and in this case you actually want to get a view of all the
terms in the index (i.e. over all segments), so I think you could wrap the
reader you ha
Hi,
It is possible to use SOLR which only requires schema configurations for use
(based on Lucene). You'll still need some java to look at the source code and
understand things better.
But it's potentially a Java free route to make it work for you as a search
solution.
Hope that helps,
Mou
O
the problem you're having is that you haven't learn about java yet.
you need to know about imports statement, about jars file that contain
java classes. you need to learn about this first then you can run
java. the LIA (lucene in action) package that you're downloaded can
all be run if you put them
Dear Saurabh
In fact I'm a *beginner*, I never used java before! now I need to use
lucene, and in this part I need to calculate Precision and Recall! I found
the code and just copied and pasted it in eclipse enviroment! and when I run
this, program dosent know some import classes and some other t
Not sure if I understood the issue right but if you are searching for jars
which might have the imported classes (classes in the import statements)
then just give fully qualified name of that class in findjar.com search and
you will get which jar has that class file in it.
Select the appropriate ja
Before you get into Java, you should know that it's posible to find a lucene
implementation for your language. Lucene is available in python, c# .net,
etc... Search for that first.
If you chose Java, you'll need to make baby steps. Install yourself an IDE
(eclipse, netbeans...) to get rid of all t
This is really not the forum for questions like this (which are not
related to Lucene but rather to Java) but for a very simple checklist of
what you need, try this:
http://download.oracle.com/javase/tutorial/getStarted/cupojava/win32.html
But I ask that any further questions which are purely j
: On trunk, you can add the "debug.explain.structured=true" param which will
: cause the explanation messages to be returned as structured data.
backported to 3x for inclusion in 3.2...
https://issues.apache.org/jira/browse/SOLR-1915
-Hoss
: I stumbled upon the 'Explain' function yesterday though it returns a crowded
: message using debug in SOLR admin. Is there another method or interface
: which returns more or cleaner info?
On trunk, you can add the "debug.explain.structured=true" param which will
cause the explanation messages
On Fri, May 20, 2011 at 2:46 PM, Doron Cohen wrote:
> I stumbled upon the 'Explain' function yesterday though it returns a crowded
>> message using debug in SOLR admin. Is there another method or interface
>> which returns more or cleaner info?
>>
>
> I am not familiar with the use of Solr for thi
Hi Rich,
SeetSpotSimilarity looks promising. Does it not favor shorter docs by not
> normalizing or does it make some attempt to standardized.
>
> > - using e.g. SeetSpotSimilarity which do not favor shorter documents.
>
SweetSpotSimilarity (I misspelled it previously) defines a range of lengths
Bingo. That appears to be the essence of the problem, which makes sense
given TF/IDF.
I stumbled upon the 'Explain' function yesterday though it returns a crowded
message using debug in SOLR admin. Is there another method or interface
which returns more or cleaner info?
I feel uncomfortable with
Hi Rich,
If I understand correctly you are concerned that short documents are
preferred too much over long ones, is this really the case?
It would help to understand what goes on to look at the Explanation of the
score for say two result documents - one that you think is ranked too low,
and one tha
Thanks Paul,
I do not know what duplicates are in this case and it is the denominator of
the TF that bothers me more than the numerator of the TF (if that is in fact
what you are suggesting).
What have been the effects of ignoring the IDF? When is it appropriate. It
would seem that by doing so ra
Richard,
in SOLR at least there's an analyzer that avoids duplicates.
I think that would solve it.
There's also somewhere the option to ignore IDF (in similarity? in solrconfig?).
paul
Le 18 mai 2011 à 21:30, Rich Heimann a écrit :
> Hello all,
>
> This is my first time on the list and my fir
Hi,
You could just try the following code to print the term freq for individual
terms.
public static void printTermFreq(String indexPath) throws
CorruptIndexException, IOException{
IndexReader ir = IndexReader.open(new NIOFSDirectory(new
File(indexPath)));
TermEnum
OK, you're officially beyond where I can help. But the
rewritten query is your problem, and I'm going to appeal to
people who understand things waaay better than I do to answer
it. Can you recognize it when I run away ...
You might consider posting that question over on the nutch
user's list if yo
Thank you Erick!
I got Luke and it's a great tool! I verified from Luke my queries posted
originally worked as expected (i.e., "Canadian pepsi" produced fewer results
than "pepsi" along.)
Based on your suggestion, I found out the program re-wrote the query before
it was sent to Nutch as the foll
For Luke, see http://www.getopt.org/luke/ or just google lucene luke
About the same analyzers at index and search. No, it's not *required*
that you use the same analyzer, but unless and until you understand
what analyzers do, I would *strongly* recommend that you use the
same one. See PerFieldAnal
Hi Eric,
Thanks a bunch for your pointers. I will need to find out the analyzers at
index and query time. But is it critical to have the same analyzers during
these two times?
I had tested with lucli from some of my local segment data and they appeared
working fine (i.e., their result sets are r
Hi Dan,
Thanks for your suggestion. I will definitely check that out.
-student_t
Daniel Naber-10 wrote:
>
> On Freitag, 26. September 2008, student_t wrote:
>
>> A. query1 = +(content:(Pepsi))
>
> I guess this is the string input you use for your queries, isn't it? It's
> more helpful to
That certainly doesn't look right. What analyzers are you using at index
and query time?
Two things that will help track down what's really happening:
1> query.toString() is your friend.
2> get a copy of the excellent Luke tool and have it do its explain magic on
your query. Watch that the analyz
On Freitag, 26. September 2008, student_t wrote:
> A. query1 = +(content:(Pepsi))
I guess this is the string input you use for your queries, isn't it? It's
more helpful to look at the toString() output of the parsed query to see
how Lucene interpreted your input.
Regards
Daniel
--
http://ww
Here you go:
Analyzer a=new StandardAnalyzer();
//open an index
String textFieldName="contents";
IndexReader reader=IndexReader.open("E:/indexes/uksites");
IndexSearcher searcher=new IndexSearcher(reader);
QueryParser qp=new QueryParser(textFieldNa
The test code in the Highlighter contrib also has some synonym code.
On 2/13/07, Michael Wechner <[EMAIL PROTECTED]> wrote:
Saroja Kanta Maharana wrote:
> Hi All,
>
> Any one help to implements synonyms search in lucene.
>
you might want to take a look at the ontology module within nutch.
Saroja Kanta Maharana wrote:
Hi All,
Any one help to implements synonyms search in lucene.
you might want to take a look at the ontology module within nutch.
HTH
Michael
*Regards*
*Saroj*
On 2/13/07, karl wettin <[EMAIL PROTECTED]> wrote:
13 feb 2007 kl. 12.41 skrev Saro
7 13:45
To: java-user@lucene.apache.org
Subject: Re: Please Help me
Hi All,
Any one help to implements synonyms search in lucene.
*Regards*
*Saroj*
On 2/13/07, karl wettin <[EMAIL PROTECTED]> wrote:
13 feb 2007 kl. 12.41 skrev Saroja Kanta Maharana:
"When i searche
I have a similar request. Does anyone know if Lucene is capable of
implementing polyheirarchical taxonomies?
-Original Message-
From: Saroja Kanta Maharana [mailto:[EMAIL PROTECTED]
Sent: 13 February 2007 13:45
To: java-user@lucene.apache.org
Subject: Re: Please Help me
Hi All
Hi All,
Any one help to implements synonyms search in lucene.
*Regards*
*Saroj*
On 2/13/07, karl wettin <[EMAIL PROTECTED]> wrote:
13 feb 2007 kl. 12.41 skrev Saroja Kanta Maharana:
> "When i searched for "AND", "OR", "NOT" as query, it gives me the
> following
> Exception"
>
>
13 feb 2007 kl. 12.41 skrev Saroja Kanta Maharana:
"When i searched for "AND", "OR", "NOT" as query, it gives me the
following
Exception"
Exception in thread "main"
org.apache.lucene.queryParser.ParseException:
Encountered "" at line 1, column 3.
You tried to parse the string "OR" as a
I believe that this happens because "AND", "OR" and "NOT" are all
reserved words for joining together other search terms and therefore if
you don't want the exception thrown then you must capture any "AND",
"OR" and "NOT"s that are entered on their own and not pass them to the
QueryParser.
-O
Please, do not ever, under any circumstances at all, cross post a
message to all of these lists -- there is absolutely no reason for it, and
doing so will most likely only make people mad and uncooporative.
if you are trying to use Java Lucene, then post your message to java-user
list. if you ar
I am also only novice, but that should work for you.
One row in your table ==> one doc in lucene:
I would indice it like that for one row/document:
Document doc = new Document();
doc.add(new Field("prod_Id
doc.add(new Field("prod_name...
...
writer.addDocument(doc);
Now check your index
44 matches
Mail list logo
