Dear Shai,
I only made the mistake by using the same directory for both IndexWriter
and FacetWriter. Now it is working fine .Thank you :)
Could you please tell me if there is any major performance difference in
using *3.6 and 4.x* *Facet *library?.
Since I use the Lucene 3.6 version, I am using F
Thanks Mike,
Will try your suggestion. I will try to describe the actual use-case itself
There is a requirement for merging time-adjacent segments [append-only,
rolling time-series data]
All Documents have a timestamp affixed and during flush I need to note down
the least timestamp for all docum
Dear Shai,
Thank you for your reply.
Actually I am using Lucene3.6 in Android. It is working fine. but with the
latest versions there are some issues.
Now I just added this Facet search library also along with the old Lucene
code.
After this Facet search integration, it is giving these Corrupted
Y, if you're game to try it, that is one option. If svn and build tools (mvn)
are new to you, there are some startup costs to getting it up and running (e.g.
http://stackoverflow.com/a/10073686/2938927).
This might help:
http://lucene.472066.n3.nabble.com/How-can-I-compile-and-debug-Solr-from-s
Sorry, but I don't know what exactly you mean by compile from these locations.
Do you mean I could download and customize the code?
Regards,
Raghu
-Original Message-
From: Allison, Timothy B. [mailto:talli...@mitre.org]
Sent: Thursday, February 06, 2014 2:35 PM
To: java-user@lucene.apa
Sorry, you're right. I'm not sure that it analyzes multiterm components,
either. The Surround query parser also has similar limitations.
Best bet might be to compile:
https://issues.apache.org/jira/i#browse/LUCENE-5205 or
https://issues.apache.org/jira/browse/LUCENE-1486 .
-Original Mes
Thank you, Tim.
I have read that ComplexPhraseQueryParser has issues while searching in more
than one field. In my case, I need to search the value in multiple fields of
each document.
Do you think it is possible? Also, could you please direct me to any useful
links for ComplexPhraseQueryParse
It looks like something's wrong with the index indeed. Are you sure you
committed both the IndexWriter and TaxoWriter?
Do you have some sort of testcase / short program which demonstrates the
problem?
I know there were few issues running Lucene on Android, so I cannot
guarantee it works fully .. w
Hi,
I am using Lucene 3.6 version for indexing and searching in Android
application.
I have implemented Facet search. But when I try to search, it is giving the
below exception while creating the DirectoryTaxonomyReader object.
02-06 21:00:58.082: W/System.err(15518):
org.apache.lucene.index.Cor
On 2/6/2014 12:53 AM, Earl Hood wrote:
On Tue, Feb 4, 2014 at 6:05 PM, Michael Sokolov wrote:
Thanks for the feedback. I think it's difficult to know what to do about
attribute value highlighting in the general case - do you have any
suggestions?
That is a challenging one since one has to kno
Ditto Jack on ComplexPhraseQueryParser.
See also: https://issues.apache.org/jira/i#browse/LUCENE-5205
-Original Message-
From: Jack Krupansky [mailto:j...@basetechnology.com]
Sent: Wednesday, February 05, 2014 6:59 PM
To: java-user@lucene.apache.org
Subject: Re: Wildcard searches
Take a
Somewhere in those numeric trie terms are the exact integers from your
documents, encoded.
You can use oal.util.NumericUtils.prefixCodecToInt to get the int
value back from the BytesRef term.
But you need to filter out the "higher level" terms, e.g. using
NumericUtils.getPrefixCodedLongShift(term
I use a Codec to flush data. All methods delegate to actual Lucene42Codec,
except for intercepting one single-field. This field is indexed as an
IntField [Numeric-Trie...], with precisionStep=4.
The purpose of the Codec is as follows
1. Note the first BytesRef for this field
2. During finish() ca
13 matches
Mail list logo