It depends on the number of fields. If you search on 3 fields it is not likely
to be a problem (the general use case 3 fields: plain, stemmed, folded). But if
you have like 50 fields, the slow down is likely very large!
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http
tch?v=mARACndILQc
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Michael McCandless [mailto:luc...@mikemccandless.com]
> Sent: Saturday, July 18, 2015 12:43 AM
> To: Lucene Users; coone
the
recommendation is to not use such tools unless you know how to correctly use
them (so they preserve and merge the META-INF/services folder inside the JAR
file).
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Origi
Hi,
> On Mon, Jul 6, 2015 at 4:32 PM, Uwe Schindler wrote:
> > Hi,
> >
> > It could be the reason for this is your classpath:
> >
> > If you load all Lucene Versions into the same classloader (but with
> > different
> package names - I assume you us
Lucene 5 ships with "modified" versions of
the old Lucene 4 codecs - but they are not identical.
You can only workaround by loading the Lucene JARs into completely different
classloaders (don't forget to also set context classloader!). In that case you
would not even need to ch
l commands, e-mail: java-user-h...@lucene.apache.org
>>
>
>-
>To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>For additional commands, e-mail: java-user-h...@lucene.apache.org
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
that has default
codec).
After that you can read the 4.10 index with 5.0 using
lucene-backward-codecs.jar in classpath.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Uwe Schindler [ma
Hi,
you need to add the JAR file lucene-backward-codec.jar to the classpath (or add
it via Maven). It contains the codecs to read pre-5.0 versions.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
>
er used in Lucene. It was
there to forcefully remove a lock, which is a bad idea. The only available
method is, as said before, Directory#makeLock that should return a Lock
instance.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@t
Hi,
> > BytesRef#clone()'s javadoc comment says that the result will be a
> > shallow clone, sharing the backing array with the original instance,
> > and points to another utility method for deep cloning:
> BytesRef#deepCopyOf(BytesRef).
>
> There is no hard contract for clone
> https://docs.or
va 8, but you should in any case test it. One example
> that uses Lucene 3.3.0 (a bit newer, based on Java 5) is "Atlassian JIRA".
> This
> one works perfectly fine with Java 8!
>
> Uwe
>
> -
> Uwe Schindler
> H.-H.-Meier-Allee 63, D-28213 Bremen
>
it newer, based on Java 5) is "Atlassian JIRA". This
one works perfectly fine with Java 8!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Erick Erickson [mailto:erickerick...@gmail
) was only searching in context class loader for metadata. Lucene 4.3 fixes
this issue by also searching for metadata in the classloader that originally
loaded the lucene jars: https://issues.apache.org/jira/browse/LUCENE-4713
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
is the one you want to
have.
It is easy to do if you use the corresponding ANT task for regenerating ("ant
jflex" or "ant regenerate").
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message
e correct version of
JFlex and regenerate the scripts. Currently this is version 1.6.0. The warning
was primarily there because of older versions of JFlex that used the Unicode
version of the JVM which is no longer the case.
Could you may be open an issue to update the documentation in the fi
TokenFilter does not implement reset() correctly, so the whole
thing cannot be reused in analyzers.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Spyros Kapnissis [mailto:ska...@yahoo.com.I
u have any questions, comments, or just want to hang out with us
before and during the event, follow us on Twitter - @apachecon - or drop by
#apachecon on the Freenode IRC network.
Hope to see you in Austin!
-
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Hi,
http://lucene.apache.org/core/4_10_3/core/org/apache/lucene/search/FieldCacheDocIdSet.html
You just have to implement the "protected boolean matchDoc(int docId)" method.
You should return this DocIdSet from your filter instead of the manual code you
created.
Uwe
-
Uwe Schi
Hi Chris,
> Hi Uwe, thanks for your suggestions. I have tried a couple of things with no
> luck yet:
>
> > Sorry,
> > I just noticed, you are using TermFilter not TermsFilter: This one
> > does not support random access (using bits()). Because of this the
> > filtered docs cannot be passed down
the same field name for both.
> I must add that a full reindex all in one go is currently not an option, so
> the
> solution must support this mixed mode.
Uwe
> Any thoughts on how this could be best achieved ..?
>
> Thanks
>
> Chris
>
> Sent from my iPhone
>
a while until also the address space gets exhausted.
Just a few additional questions:
How many indexes are you opening at the same time? What is the approx. size?
What Lucene version are you using?
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u
efore (use
ConstantScoreQuery).
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: Wednesday, March 11, 2015 8:07 PM
> To: java-user@lucene.apa
the TermsFilter on the top level IndexSearcher (which
internally rewrites to FilteredQuery(query, filter)), the documents matching
the TermsFilter will be applied as acceptDocs by your BooleanQuery, which will
pass it also down to the MyNDVFilter.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D
misc module. It "emulates" DocValues for fields that don't have them by
uninverting like FieldCache did before
(http://lucene.apache.org/core/5_0_0/misc/org/apache/lucene/uninverting/UninvertingReader.html).
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.theta
NumericField, it is a bit more
complicated. You have to understand how the spatial module works. We are sorry
that the release notes were not precise enough.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
>
Hi,
Solr uses DocValues and falls back to wrapping with UninvertingReader, if user
have not indexed them (with negative startup performance and memory effects).
But in general, you should really enable DocValues for fields you want to sort
on.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D
, but the file stays
alive. This was different in Lucene 3, where the lock was also removed. But
this caused problems because of non-atomic file operations. Lock factory only
checks the "lock on the file", not "the existence of the file as a lock".
Uwe
-
Uwe Schindler
H.-
e the org.apache.lucene.analysis package documentation for more
details."
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Clemens Wyss DEV [mailto:clemens...@mysign.ch]
> Sent: Monday, February 23
re is a section following). Maybe fix this on the web page,
for the mail it's too late.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Anshum Gupta [mailto:ans...@anshumgupta.net]
>
would not help you, too - you need the default Codec be available at
the time your custom codec is loaded... Same issue, no idea how to solve this.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> F
Maybe try it out, was just an idea :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com]
> Sent: Thursday, February 12, 2015 2:11
ing a new index.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Vijay B [mailto:vijay.nip...@gmail.com]
> Sent: Tuesday, February 10, 2015 8:38 PM
> To: java-user@lucene.apache.org
>
done at all, in that case the whole
field is indexed as a single term - but that’s not useful for searching in full
text anyways. So use a suitable analyzer!
> Is that right?
Yes!
Uwe
> Best Regards,
> Sreedevi S
>
> On Tue, Feb 10, 2015 at 2:45 PM, Uwe Schindler wrote:
>
&g
Hi,
> OK. I found the Alfresco code on GitHub. So it's open source it seems.
>
> And I found the DateTimeAnalyser, so I will just take that code as a starting
> point:
> https://github.com/lsbueno/alfresco/tree/master/root/projects/repository/
> source/java/org/alfresco/repo/search/impl/lucene/an
://goo.gl/SRf45A
If you have a limitation to 10,000 characters somewhere, it might be your TIKA
text extraction.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: sreedevi s [mailto:sreedevi
Hi,
> I am in the beginning of implementing a Lucene application which would
> supposedly search through some log files.
>
> One of the requirements is to return results between a time range. Let's say
> these are two lines in a series of log files:
> 2015-02-08 00:02:06.852Z INFO...
> ...
> 2015
SHOULD be in results (at least one occurrence in total), or MUST_NOT. The
Operators are applied to the clauses (terms) in Lucene.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Ian Koe
ead.
So please: Use MMapDirectory where possible - this is completely unrelated to
how much RAM you have available!
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: sreedevi s [mailto:sreed
rks.com/blog/why-not-and-or-and-not/
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Ralf Heyde [mailto:ralf.he...@gmx.de]
> Sent: Monday, February 02, 2015 4:28 PM
> To: java-u
h boosts multiplied). But if you have many
Boolean clauses, how could those be optimized? If you have multiple term
queries as clauses with identical terms, one could optimize that by merging
those clauses and add their boosts, but this is not done automatically.
Uwe
-
Uwe Schindler
H.-H
nd replace the index, as you suggested.
You might open a bug report for Lucene so we can fix this interesting corner
case in IndexUpgrader, and we can fix it in later versions, but we cannot do
this in 3.x anymore, because the development has ended there.
Uwe
-
Uwe Schindler
H.-H.-Meier-A
ds of Elasticsearch and Lucene."
(http://www.elasticsearch.org/guide/en/elasticsearch/guide/current/_don_8217_t_touch_these_settings.html)
In fact, the problems with G1GC can sometimes lead to index corruption, and are
hard to reproduce. So better don't use...
Uwe
-
Uwe Schindler
H.
Java 8 update 20 or later is also fine. At current time, always use latest
update release and you are be fine with Java 7 and Java 8. Don't use older
releases and don't use G1 Garbage Collector.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.d
/elasticsearch/guide/current/multi-field-search.html
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Alexey Morozov [mailto:moro...@gmail.com]
> Sent: Monday, January 26, 2015 11:49 AM
> T
looks like you prevented
IndexWriter from merging at all. This of course would make queries slow,
because you have way too many index segments (CFS files).
If you upgrade from very old Lucene versions, it is wise to remove any
customizations and start with plain default settings.
Uwe
-
Uwe
Hi,
> we use 4.8.1. We know that the javadoc advises against it. Like I wrote, the
> deletion of old documents (that appear during an update) would be done
> while closing the writer.
This is not true. The merge policy continuously merges segments that contain
deletions. The problem you might ha
ommon cases, but whenever you have
custom requirements, you have to define your Analyzer *completely* yourself.
This is also what Solr and Elasticsearch users do in their config files.
Uwe
> Thank you.
>
> On Mon, Jan 12, 2015 at 1:36 PM, Uwe Schindler wrote:
>
> > Hi,
> >
>
, because those are instantiated before
the TokenFilters which depend on them, so changing the Tokenizer afterwards is
impossible.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Vihari P
for a specific field is done above –
this one is more to execute Querys and so on):
<http://lucene.apache.org/core/4_10_3/core/org/apache/lucene/index/IndexReader.html#getTermVectors(int)>
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
<http://www.thetaphi.de/> http
Hi,
I checked it out a second time. We *can* implement deep clone. Actually this is
a bug from the time when we changed to BytesRefBuilder. I opened
https://issues.apache.org/jira/browse/LUCENE-6173 about this. Thanks.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http
"standard" Analyzers you
would not see those TokenStreams. Lucene also never adds TokenFilters on top.
Let me check if this TokenStream is really marked as @lucene.internal in
Javadocs.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@t
ument/abb73b45a48cb89e
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
> Sent: Wednesday, January 07, 2015 10:17 PM
> To: java-user@lucene.apache.
y create a new IndexSearcher instance for
every search request (...and I always do this).
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Barry Coughlan [mailto:b.coughl...@gmail.com]
> Sent:
In addition, use NoMergePolicy to prevent automatic merging once the segments
were added. :-)
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent
ll files, that were not copied unmodified, keep alive in the source
directory, but all those that are copied as-is will move and disappear from
source directory.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original M
sible, because the files reference each other by segment name (segments_n
refers to them, also the segment ids are used all over). So You would need to
change some index files already for merge to make the SegmentInfos structures
use the correct names, so you can do a real merge anyways.
Uwe
----
Hi Dawid,
Unfortunately, for that to work, Solr needs to solely use NIO.2, too. Only
Lucene disallows java.io.File and related classes, Solr is excluded from this
forbidden-check.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
rick here is to clone the file and
its inode, but keep the blocks the same (only when one writes to the file, it
clones the block). This could speed up tests, especially Solr where some dirs
are copied over and over for every test case. :-)
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Dawid Weiss [mailto:dawid.we...@gmail.com]
> Sent: Monday, December 22, 2014 8:48 AM
> To: java-user@lucene.apache.org
> Cc: Uwe Schindler
file it will also not work.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de <http://www.thetaphi.de/>
eMail: u...@thetaphi.de
From: Shlomit Rosen [mailto:shlom...@il.ibm.com]
Sent: Wednesday, December 17, 2014 8:04 PM
To:
Subject: Index corr
ion.
> --
> on a side note,not related to this, could you please reply to my comments on
> your blog for MMap directory post.
What was your question?
Uwe
> On Fri, Dec 12, 2014 at 12:59 PM, Uwe Schindler wrote:
> >
> > Hi,
> >
> > I noticed, you
ere NFS is a problem with MMap,
because whenever the connection to the NFS server drops, it may crush the whole
JVM or produce strange errors. This could also be the reason for the error you
see here.
I would recommend to update to 1.7.0_72 or 1.8.0_25.
Uwe
-
Uwe Schindler
H.-H.-Meier-A
Hi,
Which Java 7 build number / update level are you using? Those errors occur
easily if you use an outdated JDK version.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Vijay B [mailto:vij
with SearcherManager in Lucene to warm searchers.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Li Li [mailto:fancye...@gmail.com]
> Sent: Wednesday, December 03, 2014 3:46 AM
> T
Hello everyone,
We have extended the deadline for submissions to the FOSDEM 2015 Open Source
Search Dev
Room to Monday, 9 December at 23:59 CET.
We are looking forward to your talk proposal!
Cheers,
Uwe
-
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Bremen
Hi,
Use FieldValueFilter for that:
http://lucene.apache.org/core/4_10_2/core/org/apache/lucene/search/FieldValueFilter.html
If you need a query instead of a Filter, wrap it with ConstantScoreQuery.
This is also much faster than a RangeQuery like suggested by Ahmed.
Uwe
-
Uwe Schindler
H
rs,
LH on behalf of the Open Source Search Dev Room Program Committee*
* Boaz Leskes, Isabel Drost-Fromm, Leslie Hawthorn, Ted Dunning, Torsten Curdt,
Uwe Schindler
-
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Bremen, Germany
http:
The old constants are still working in later versions.
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Robert Nikander [mailto:rob.nikan...@gmail.com]
> Sent: Saturday, November 22, 2014 8:3
Hi,
This generally happens, if you have an older version of Lucene somewhere in
your classpath. E.g., if older Lucene was placed outside of the webapp
somewhere in the classpath of Websphere itself.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u
Hi,
> It is expected: those are the "prefix" terms, which come after all the full-
> precision numeric terms.
>
> But I'm not sure why you see 0s ... the bytes should be unique for every term
> you get back from the TermsEnum.
That's easy to explain:
The lower precision terms at the end have mo
ter case insensitive (there is a boolean to do this):
StopFilter(boolean enablePositionIncrements, TokenStream input, Set
stopWords, boolean ignoreCase)
Uwe
> Martin O'Shea.
> -Original Message-
> From: Uwe Schindler [mailto:u...@thetaphi.de]
> Sent: 10 Nov 2014 1
and add your "configuration" there.
If you use Apache Solr or Elasticsearch you can create your analyzers by XML or
JSON configuration.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From:
Hi,
> That error can also be thrown when the number of open files exceeds the
> given limit. "OutOfMemory" should really have been named
> "OutOfResources".
This was changed already. Lucene no longer prints OOM (it removes the OOM from
stack trace). It also adds useful information. So I think th
use case? Any suggestions on the best/most
>efficient way to achieve?
>
>Thanks!
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
ation
fault (crush) of your Java VM. Otherwise there is no real difference between
the directory implementations. Writing and locking the index is the main
problem (see above).
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -
Hi Jean-Claude,
> We have a NetBeans RCP application using Lucene 4.7 for indexing and
> searching.
>
> When indexing, the following message is displayed:
>
> Dangerous reflection access to sun.misc.Cleaner by class
> org.apache.lucene.store.MMapDirectory$MMapIndexInput$1 detected!
This message
Hi,
forgot to mention:
FOSDEM 2015 takes place in Brussels on January 31th and February 1st, 2015. See
also: https://fosdem.org/2015/
I hope to see you there!
Uwe
> -Original Message-
> From: Uwe Schindler [mailto:uschind...@apache.org]
> Sent: Monday, November 03, 2014 1:29 P
zers: opensourcesearch-devr...@lists.fosdem.org
Cheers,
LH on behalf of the Open Source Search Dev Room Program Committee*
* Boaz Leskes, Isabel Drost-Fromm, Leslie Hawthorn, Ted Dunning, Torsten Curdt,
Uwe Schindler
-----
Uwe Schindler
uschind...@apache.org
Apache Lucene PMC Member / Committer
Br
Hi,
You have to implement createComponents(). The old way of Lucene 3 does no
longer work because Analyzers have to provide reusable TokenStreams.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
>
urself. An alternative would be to
> use another query parser (like the SimpleQueryParser, see
> http://goo.gl/4blGsp) that allows to expand the query to search on multiple
> fields with different weight factors.
> >
> > Uwe
> >
> > -
> > Uwe Schindle
An alternative would be to use
another query parser (like the SimpleQueryParser, see http://goo.gl/4blGsp)
that allows to expand the query to search on multiple fields with different
weight factors.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMa
2.9, but this is no
longer the case - every segment is handled on its own.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: aurelien.mazo...@francelabs.com
> [mailto:aurelien.mazo...@franc
rewriting and set it
on the MultiTermQuery variant and rewrite it to collect the terms.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Christian Reuschling [mailto:reuschl...@dfki.uni-kl.de]
> Sen
s space,
but why do you think a "higher" address space is better for a larger index?
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Gaurav gupta [mailto:gupta.gaurav0...@gmail.com]
&
Hi,
1 GiB is the maximum possible. The chunk size is only applicable for 32 bit
JDKs because of limited address space.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Gaurav
Hi
> Background: My company has built an Android application that utilizes
> Lucene 4.7.0 to index and search upon a fairly static set of about 100,000
> documents. We have used numerous versions of Lucene over the years, and
> they have all worked well to accomplish this purpose.
>
> Issue: Upo
acked together as an .aar file (which is a
special JAR, too). Maybe this step misses to add the the META-INF/services
folder.
Sorry I cannot help here more.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Messag
you have to
use them as-is. If you for example unpack them and use the .class files in them
directly or if you repackage them into a so called "uber-jar" (one JAR
containing everything), the additional metadata often gets lost.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 B
n and its resource
transformers.
Uwe
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Rajendra Rao [mailto:rajendra@launchship.com]
> Sent: Wednesday, September 24, 2014 10:03 AM
&
re, that SpanQueries are expensive and may take a lot of time!
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: teko [mailto:tec...@gmail.com]
> Sent: Monday, September 22, 2014 8:45 PM
>
if someone could point out the right direction.
>
>Regards,
>Patrick
>
>-
>To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org
>For additional commands, e-mail: java-user-h...@lucene.apache.org
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
(name, yourTokenStream)".
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Sachin Kulkarni [mailto:kulk...@hawk.iit.edu]
> Sent: Sunday, September 14, 2014 10:06 PM
> To: java-
/IndexWriter to think it was
created in 3.x.
TestBackwards compatibility did not find that bug, because the backwards index
in the tests directory was created with the Alpha version :(
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
If you want to upgrade the index, you may try to run IndexUpgrader on Lucene
4.9, to have it up to date. But Index upgrading may fail because of the
BETA-Status of the original creator.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
In Lucene 4.10 we changed version
handling and parsing version numbers a bit, so this may be the cause for the
error.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Ian Lea [mailto:ian@g
es the
approach you should use, if you don't need "syntax".
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: atawfik [mailto:contact.txl...@gmail.com]
> Sent: Tuesday, S
whole issue are those stale file handles, which makes commits
in Lucene unreliable.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Shlomit Rosen [mailto:shlom...@il.ibm.com]
> Sent: Monday,
Elasticsearch works perfectly fine with one node, also embedded :-)
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u...@thetaphi.de
> -Original Message-
> From: Larry White [mailto:ljw1...@gmail.com]
> Sent: Thursday, September 04, 201
completely outside DirectoryReader on the older commit
point opens all segments on its own. Maybe a solution would be to extends
IndexWriter.open() to also take a commit point with IndexWriter.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: u
Hi,
there is no need to have an index in a relational database. Lucene indexes are
commonly stored as files on local disks. Use FSDirectory subclasses to do this!
For more details about performance problem, you should maybe give us more
details.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63
301 - 400 of 1452 matches
Mail list logo
