Le mer. 4 juil. 2018 à 05:34, Yonghui Zhao a
> écrit :
>
> > In lucene 4.10,
> > If one collector throw CollectionTerminatedException, all collectors are
> > terminated.
> >
> > In lucene 7.2.1, CollectionTerminatedException will only terminate
>
In lucene 4.10,
If one collector throw CollectionTerminatedException, all collectors are
terminated.
In lucene 7.2.1, CollectionTerminatedException will only terminate current
collector, the others won't be terminated.
How to keep old behavior?
I found there was
"org.apache.hadoop.contrib.index.lucene.FileSystemDirectory" for lucene in
hadoop old version.
http://www.massapi.com/class/org/apache/hadoop/contrib/index/lucene/FileSystemDirectory.html
But I don't find this in recent hadoop code base.
Is there any plugin support new lucene
Thanks Adrien!
Yes I am aware of this "that EarlyTerminatingSortingCollector does not
exactly do that
since it works on a per-segment basis"
I use EarlyTerminatingSortingCollector for performance when docs hit are
too much.
2018-06-04 19:09 GMT+08:00 Adrien Grand :
> You are right that TopFieldC
Hi,
I find EarlyTerminatingSortingCollector is expired in lucene 7.2.1.
Java doc says Pass trackTotalHits=false to {@link TopFieldCollector}
instead of using this class.
But I find TopFiledCollector can not fully replace
EarlyTerminatingSortingCollector.
In EarlyTerminatingSortingCollector ther
lude deleted docs
> either (actually they shouldn't do it) as live docs are now checked on top
> of scorers.
>
> Le mer. 30 mai 2018 à 12:57, Yonghui Zhao a écrit
> :
>
> > I find TermsEnum.posting(docsAndPostiions API before) in new lucene
> has
> > no a
I find TermsEnum.posting(docsAndPostiions API before) in new lucene has
no acceptDocs parameter
So any replacement? or implement the filter by myself?
I am upgrading my project now, I find there is no disableCoord feature in
boolean query now?
So now the default behavior is disableCoord = true and not configurable?
In my project I implement a NullFieldFilter, which will filter the docs
index some field regardless the value.
The implementation is traverse the index field use TermsEnum and
PostingsEnum, or using DocValues advance function to traverse the docs
which have this field. In this way I get FixedBitSe
Got it, make sense. Thanks Adrien.
2018-04-13 19:16 GMT+08:00 Adrien Grand :
> Queries should be fine: they are required to produce sorted iterators since
> 5.0 when we removed the accetDocsOutOfOrder option on collectors.
>
> Le ven. 13 avr. 2018 à 13:10, Yonghui Zhao a
> écri
neck should be query
> processing, not retrieving stored fieds.
>
> Le ven. 13 avr. 2018 à 05:27, Yonghui Zhao a
> écrit :
>
> > My case is when I get some docs from lucene, I need also get some field
> > value of the retrieved docs.
> >
> >
h
> exists on all doc-value iterators. Just make sure to never call it on
> decreasing doc IDs. If that doesn't work for you, can you describe you
> use-case, maybe there are better ways to implement what you need.
>
> Le jeu. 12 avr. 2018 à 13:54, Yonghui Zhao a
> écrit :
>
Hi,
I am upgrading my project from Lucene 4 to 7.
FieldCache is removed in lucene 7, DocValue is replacement?
But seems DocValue doesn't support random access.
I need random access to get some specified field value quickly.
So how to solve it?
the associated factory in
> ,,,/solr/core/src/java/org/apache/solr/index/
> SortingMergePolicyFactory.java
> so I'm not sure what you're having trouble with
>
> Best,
> Erick
>
> On Tue, Apr 10, 2018 at 4:56 AM, Yonghui Zhao
> wrote:
> > I can&#x
I can't find this class now? Which is replacement?
Thanks!
Hi,
Is there any public API that I can get segment number of current version
index?
I didn't find in indexwriter or indexsearcher in lucene 4.10.
gt; On Thu, Dec 28, 2017 at 11:13 AM, Yonghui Zhao
> wrote:
>
>> Hi,
>>
>> I specified a SortingMergePolicy in my case. I find only the first N-1
>> segments are sorted as expected, the last segment is still disordered
>> when
>> I call forceMerge(N), N &g
Hi,
I specified a SortingMergePolicy in my case. I find only the first N-1
segments are sorted as expected, the last segment is still disordered when
I call forceMerge(N), N > 1,
I think it is by design, but is there any way to make all segments sorted.
Thanks !
Hi,
I clone lucene 4.10.4 tag from github and use ant to build.
My ant and local jdk in mac info:
*Apache Ant(TM) version 1.9.9 compiled on February 2 2017*
*Trying the default build file: build.xml*
*Buildfile: /Users/yozhao/src/lucene-solr/lucene/core/build.xml*
*Detected Java version: 1.7 in:
Hi,
I use the code below to test same query on same index in one time.
long t0 = System.currentTimeMillis();
indexSearcher.search(query, from + size);
long t1 = System.currentTimeMillis();
LOGGER.info("indexSearcher.search(query, from + size) took:" + (t1 -
t0) + "ms");
TopScoreDocCollector coll
> this is only an implementation detail. The internal IDs are also not
> stable!!!
>
> Uwe
>
> -
> Uwe Schindler
> Achterdiek 19, D-28357 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
> > -Original Message-
> > From: Yonghui Zhao [mailto:zha
Hi,
It is easier to elaborate my question with an example.
My lucene version is 4.10.4
I use
SortField sortField = new SortField(null, SortField.Type.DOC, true);
sort = new Sort(sortField);
return new SortingMergePolicy(new TieredMergePolicy(), sort);
to make sure my index merger will make
quot;D E F"，3rd is "G H I".
If I concatenate these values with space, "A B C D E F G H I" , so each doc
only index this field one 1 time, but has the same effect, no exception
occurs.
2017-03-10 13:43 GMT+08:00 Yonghui Zhao :
> My version is 4.10.0 which is later
...@mikemccandless.com> wrote:
> >
> > This seems likely to be a Lucene bug, and it seems vaguely familiar. I
> > tried to find the issue / commit that may have fixed it, but so far
> failed.
> >
> > But 4.10.0 is truly ancient; you should at least try upgrading to
Seems it is related to an empty segment, all docs in this segment are
deleted before commit.
Any one can confirm it? Maybe I need upgrade my lucene version.
2017-03-03 10:19 GMT+08:00 Yonghui Zhao :
> Hi all,
>
> Anyone see this exception before? Is it a lucene bug or something wron
be solution.
> Please see types attribute of the word delimiter filter for customising
> characters.
>
> ahmet
>
>
>
> On Monday, March 6, 2017 12:22 PM, Yonghui Zhao
> wrote:
> Yes whitespace analyzer will keep punctuation, but it only breaks word by
> space
tokenizer for example.
>
> Ahmet
>
>
>
> On Monday, March 6, 2017 10:21 AM, Yonghui Zhao
> wrote:
> Lucene standard anlyzer will remove almost all punctuation.
> In some cases, we want to keep some punctuation, for example in music
> search, some singer name and album na
Lucene standard anlyzer will remove almost all punctuation.
In some cases, we want to keep some punctuation, for example in music
search, some singer name and album name could be a punctuation.
Is there any analyzer that we can customized punctuation to be removed?
Hi all,
Anyone see this exception before? Is it a lucene bug or something wrong in
my code?
Exception in thread "Thread-14" java.lang.IllegalArgumentException:
maxValue must be non-negative (got: -1)
at
org.apache.lucene.util.packed.PackedInts.bitsRequired(PackedInts.java:1141)
It seems lucene query parser doesn't support SpanNearQuery.
Is there any query parser supports SpanNearQuery?
Does lucene query parser support disableCoord in query string？
Thanks
re making them visible to the next
> near-real-time reader.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, Apr 15, 2016 at 3:04 AM, Yonghui Zhao
> wrote:
> > As we know when a new IndexReader is create, search performance is very
> bad.
>
As we know when a new IndexReader is create, search performance is very bad.
So we should warm up the reader before serving real traffic.
A simple way is to send some mocked queries.
Is there any elegant or built-in method?
Thanks
I mean sort and filter. I want to filter all documents within some
hamming distances say 3, and sort them from distance 0 to 3.
2015-12-22 21:42 GMT+08:00 will martin :
> Yonghui:
>
> Do you mean sort, rank or score?
>
> Thanks,
> Will
>
>
>
> > On Dec 2
Hi,
Is there any query can sort docs by hamming distance if field values are
same length,
Seems fuzzy query only works on edit distance.
If I index one filed more than 1 times, it seems I can't get all values
from lucene field cache?
right?
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_8/lucene/demo/src/java/org/apache/lucene/demo/facet/SimpleFacetsExample.java
In SimpleFacetsExample,
/** Runs the search example. */
public List runFacetOnly() throws IOException {
index();
return facetsOnly();
}
/*
If we want to implement simple facet counting feature, it seems we can do
it via sortedset or taxonomy writer/reader.
Seems sortedset is simpler but doesn't support hierarchical facet count
such as A/B/C.
I want to know what's advantage/disadvantage of sortedset or taxonomy?
Is there any troubl
Hi，
I want to implement a query like phrase query with slop 0, but I can allow
one term mismatch.
For example, the text is "A B C D E"
I want to match this text with the query "A B C X E".
X mismatches the D.
i.e. Query "A B C D E" will match “W1 W2 W3 W4 W5”, the 5 words are
consecutive
now whether the doc had that
> field?
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Wed, Mar 5, 2014 at 7:00 AM, Yonghui Zhao
> wrote:
> > Hi,
> >
> > Is there any data type in lucene can support functions like
> SortedDocValues
Hi,
Is there any data type in lucene can support functions like SortedDocValues
for any numeric(int, long, float, double) type.
SortedDocValues only supports bytes, I want some data type can get numeric
value and ord(-1 for doc doesn't have the field) for each doc.
NumericDocValues only supports
Hi,
I am new to lucene and I get a simple question about index reader.
If I open a DirectoryReader say reader1 based on a disk directory, then the
lucene index directory is changed, to get new result I need get a new
DirectoryReader.
Suppose reader1 will get the result before the change forever.
e any file extension.
>
> On Wed, Sep 18, 2013 at 1:03 PM, Yonghui Zhao
> wrote:
> > In lucene 4.3.0 there is no IndexFileNameFilter.
> >
> > And I find in org.apache.lucene.index.IndexFileNames the index file
> > extensions have only 3 types.
> >
> &g
In lucene 4.3.0 there is no IndexFileNameFilter.
And I find in org.apache.lucene.index.IndexFileNames the index file
extensions have only 3 types.
public static final String INDEX_EXTENSIONS[] = new String[] {
COMPOUND_FILE_EXTENSION,
COMPOUND_FILE_ENTRIES_EXTENSION,
GEN_EXTENSION,
n
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Yonghui Zhao [mailto:zhaoyong...@gmail.com]
> > Sent: Wednesday, August 21, 2013 1:38 PM
> > To: java-user@lucene.apache.org
> > Subject: NumericField traverse
If we traverse a string field use code below, the value order is string
older.
Terms terms = reader.terms(“strField");
if (terms != null) {
TermsEnum termsEnum = terms.iterator(null);
BytesRef text;
while ((text = termsEnum.next()) != null)
How about numeric field. Int
t have been
> passing in Lucene 3.5 if it did not index positions ...
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Tue, Aug 13, 2013 at 7:41 AM, Yonghui Zhao
> wrote:
> > One of my UT is passed In lucene 3.5, but it is failed in lucene4.3.
> > The exceptio
One of my UT is passed In lucene 3.5, but it is failed in lucene4.3.
The exception is:
IllegalStateException("field \"" + term.field() + "\" was indexed without
position data; cannot run SpanTermQuery (term=" + term.text() + ")");
After I change index option of the field from DOCS_ONLY to
DOCS_A
In lucene 4.3, SortField is not serializable now.
When I try to serialize a request which has SortField,
java.io.NotSerializableException: org.apache.lucene.search.SortField
exception is thrown out.
Any work around?
Got it， thank you very much.
在 2013-7-29 下午11:34，"Adrien Grand" 写道：
> Hi,
>
> On Mon, Jul 29, 2013 at 4:56 PM, Yonghui Zhao
> wrote:
> > I want to know what will be returned if the input docID is not a valid
> id,
> > for examples:
> >
> > 1. th
In luncene 4.3 AtomicReader has this interface
public abstract NumericDocValues getNumericDocValues(String field)
throwsIOException
If I get a NumericDocValues of one field from a reader.
NumericDocValues has get interface.
/**
* Returns the numeric value for the specified document ID.
"? It's best to open IndexWriter with OpenMode.CREATE to purge
> (rather than remove the files yourself).
>
> Lock obtain timed out means another IndexWriter is currently using
> that directory.
>
>
>
> Mike McCandless
>
> http://blog.mikemccandless.com
Recently I find my unit test will failed sometimes but no always. I use
Lucene 4.3.0
After inverstigation, I found when I try to open a IndexWriter for a disk
directory.
Some time it will throw this exception:
org.apache.lucene.store.LockObtainFailedException: Lock obtain timed out:
NativeFSLoc
D-28213 Bremen
> http://www.thetaphi.de
> eMail: u...@thetaphi.de
>
>
> > -Original Message-
> > From: Yonghui Zhao [mailto:zhaoyong...@gmail.com]
> > Sent: Tuesday, July 09, 2013 1:45 PM
> > To: java-user@lucene.apache.org
> > Subject: getLocale of
I am updating one project from lucene 3.x to lucene 4.x
I found getLocale of SortField is moved. How can I fix it?
gt;
> Does that cover your question?
>
>
> --
> Ian.
>
>
> On Mon, Jul 8, 2013 at 12:32 PM, Yonghui Zhao
> wrote:
> > Hi,
> >
> > What's proper replacement of "TermDocs termDocs = reader.termDocs(null);“
>
Hi,
What's proper replacement of "TermDocs termDocs = reader.termDocs(null);“
in lucene 4.x
It seems reader.termDocsEnum(term) can't take null as a input parameter.
then files will be held open and you'll
> eventually exhaust the limit of open file descriptors.
>
> Mike McCandless
>
> http://blog.mikemccandless.com
>
>
> On Fri, May 31, 2013 at 8:12 PM, Yonghui Zhao
> wrote:
> > After we use IndexReader do we always need call
After we use IndexReader do we always need call decRef explicitly?
What will happen, if I don't call decRef? Thanks
Sent from my iPad
-
To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
For additional commands, e-m
59 matches
Mail list logo
