Hi,
No, its not possible. The Version.LUCENE_23 param passed to several Lucene
components is only to emulate behaviour on analysis (like tokenization
rules) or specific settings from previous versions. The indexes created by
IndexWriter can only be read by same or newer versions.
With Lucene 4.0'
Hi,
Is it possible to create an index with lucene core version 3.3+ by using
Version.2_3 that I can then open an index with the original lucene core 2.3
version?
I tried doing the above and receive the error message "Unknown format
version: -11" error message (when trying to opening the index fro
I can't explain this. Can you get at an oal.search.Explanation? You
could write your own CustomScoreProvider - that might help you to
double check what is being passed to it, and/or allow you to provide
your own calculation.
--
Ian.
On Thu, Feb 16, 2012 at 8:32 PM, Dominika Puzio
wrote:
> He
Your example is hard to follow - too many words in the query and the
docs. Have you looked at the output from IndexSearcher.explain()? If
you don't like how lucene is scoring things you can write your own
implementation of Similarity.
--
Ian.
On Sun, Feb 19, 2012 at 5:08 AM, A Z <4azfri...@gm
Are you using StandardAnalyzer in 3.1+? You may want to use
ClassicAnalyzer instead. I can't see where in the 3.5 javadocs it
says that email addresses are recognized, but it does sound vaguely
familiar.
--
Ian.
On Thu, Feb 16, 2012 at 5:18 PM, Charlie Hubbard
wrote:
> This is a pretty simpl
Hi Pedro,
Maybe have a look at Hadoop / JAQL / HBase?
For this "simple" setup it could be a scalable and simple solution (with
additional aggregation functions).
Best
Ralf
-Original Message-
From: Pedro Ferreira [mailto:psilvaferre...@gmail.com]
Sent: Mittwoch, 15. Februar 2012 23:18
There is nothing in core lucene to do this and I don't recall seeing
anything in contrib. One approach would be to loop through all the
docs in the second index deleting them if present in first index,
commit that change, then merge the two indexes.
--
Ian.
On Mon, Feb 20, 2012 at 11:58 AM, Kar
Hi to you,
i've got a question concerning the merge of multiple indexes...
Suppose we have two indexes which contain the same content ...than the
result of a indexMerge is to have an index which contains the result
doubled..ok so far so good ...
But is there any chance/configuration that Lucen
On Sun, Feb 19, 2012 at 10:39 PM, Trejkaz wrote:
> On Mon, Feb 20, 2012 at 12:07 PM, Uwe Schindler wrote:
>> See my response. The problem is not in Lucene; its in general a problem of
>> fixed
>> thread pools that execute other callables from within a callable running at
>> the
>> moment in the
There is also MultiPassIndexSplitter, and PKIndexSplitter in contrib/misc.
PKIndexSplitter is very easy to use (one of its ctors supports passing a
Filter, all documents not matched by the filter are landing in second index,
all documents matched by the filter in the first). This splitter is way mo
Hi,
The default was and is always to create CFS files. Since recent versions of
Lucene it only changed a bit that CFS files are generated only for segments
smaller than 10% of the total index size. You can change those settings
(e.g. disabling CFS files completely) by setting the correct settings
great idea!
On Sun, Feb 19, 2012 at 9:43 PM, Li Li wrote:
> you can delete by query like -category:category1
>
> On Sun, Feb 19, 2012 at 9:41 PM, Li Li wrote:
>
> > I think you could do as follows. taking splitting it to 3 indexes for
> > example.
> > you can copy the index 3 times.
> > for co
Hello all,
I am using Lucene 3.5.0 with all default options. I have not done optimize
(forcedmerge). I could see multiple CFS files created as part of the index even
though i haven't opted for. Could anyone tell me the reason.
_4xq.fdt
_4xq.fdx
_4xq.fnm
_4xq.frq
_4xq.prx
_4xq.tii
_4xq.tis
_4xq.
13 matches
Mail list logo