That's the question.When I get the doc by QueryParser("jakarta apache"~10),
which means it hits the query syntax, but it depends on the word position
and not on offset, and that is not my intent. There are some docs which
satisfied the ("jakarta apache"~10) but not satisfied the regex
"jakarta.{1,1
As we know, the we can sort by multi-fields, such as field1 , then field2.
But I have another scenario:
We need pick up the max(field1) record first, then sort by field2 for others
records.
Anyone can help me?
Thanks in advance.
Thanks
Jack
kiwi clive [kiwi_cl...@yahoo.com]:
> Thanks very much for the reply. I see there is not a quick win here but as
> we are going through an index consolidation process, it may pay to make
> the leap to 4.3 and put in facetting while I'm in there. We will get facetting
> slowly through the back door w
Do you mean the raw character offsets of the starting and ending characters
of the terms?
No.
Although, if you index the text as a raw string, you might be able to come
up with a regex query like "jakarta.{1,10}apache"
-- Jack Krupansky
-Original Message-
From: wgggfiy
Sent: Monda
As I know, the syntax *"jakarta apache"~10*, which is a PhraseQuery with a
slop=10 in position, but What I want is *based on offset* not on position?
Anyone can help me ? thx.
-
--
Email: wuqiu.m...@qq.com
--
--
View this message in context:
Hi guys,
If I run 2 term range queries:
new TermRangeQuery("title", new BytesRef("A"), null, true, true);
and
new TermRangeQuery("title", new BytesRef("Z"), null, true, true);
The one that starts with "Z" is several times faster (I make 1000
queries in a loop to measure). I understand that the f
Hi all,
It seems tryDeleteDocument(IndexReader, int) doesn't work with NRTManager
while deleteDocuments(Query) works.
Here are some sample code snippets:
TrackingIndexWriter mgrWriter = new NRTManager.TrackingIndexWriter(writer);
ReferenceManager mgr = new NRTManager(mgrWriter, new
SearcherFact
Hi Clive,
If you are considering indexing consolidation, then upgrading to 4.3 is the
right way since a lot of improvements have been made to the facet module
(performance, APIs).
Also, 10K+ shards ... wow. That must be a big deployment you have there :).
I'm sure it will bring with it fun requir
Hi Shai,
Thanks very much for the reply. I see there is not a quick win here but as we
are going through an index consolidation process, it may pay to make the leap
to 4.3 and put in facetting while I'm in there. We will get facetting slowly
through the back door while the consolidation runs (w
Hello ,
I downloaded and extracted lucene 4.2.1 , and set the 4 jar files in my
classpath .
But now when i execute the command
java org.apache.lucene.demo.IndexFiles -docs {path-to-lucene}/src
i get a error Document directory
'/Volumes/SindhuHosamane/IR_project/lucene-4.2.1/src' does not exist
May 2013, Apache Lucene™ 4.3 available
The Lucene PMC is pleased to announce the release of Apache Lucene 4.3
Apache Lucene is a high-performance, full-featured text search engine
library written entirely in Java. It is a technology suitable for
nearly any application that requires full-text searc
I'm sorry, there was a bug in my test case which caused deleted
documents to be shown as live documents.
Am 06.05.2013 13:36, schrieb Michael McCandless:
On Mon, May 6, 2013 at 7:32 AM, Daniel Penning wrote:
If a Document is updated multiple times in one transaction it may end up
with old ve
On Mon, May 6, 2013 at 7:32 AM, Daniel Penning wrote:
> If a Document is updated multiple times in one transaction it may end up
> with old versions not getting deleted, depending on when the IndexWriter got
> flushed.
Hmm that should not be the case.
If you use updateDocument, and the Term you
Hi
If a Document is updated multiple times in one transaction it may end up
with old versions not getting deleted, depending on when the IndexWriter
got flushed. I couln't find an details about this behaviour in the
documentation. Is this the expected behaviour and will forcing a flush
by ope
14 matches
Mail list logo
