Thanks a lot Shai! That was really quick response.
On Thu, May 16, 2013 at 11:32 AM, Shai Erera wrote:
> Hi Raj,
>
> Unfortunately the userguide is outdated after refactorings made to the
> package. We have an issue open to fix that.
> Until then, you can find an example code here:
>
> https://
Hi Raj,
Unfortunately the userguide is outdated after refactorings made to the
package. We have an issue open to fix that.
Until then, you can find an example code here:
https://svn.apache.org/repos/asf/lucene/dev/branches/lucene_solr_4_3/lucene/demo/src/java/org/apache/lucene/demo/facet/SimpleFac
Hi,
I was checking on Lucene Faceted search and need some guidance.
http://lucene.apache.org/core/4_3_0/facet/org/apache/lucene/facet/doc-files/userguide.html#facet_indexingmentions
about
DocumentBuilder categoryDocBuilder = new CategoryDocumentBuilder(taxo);
But I am unable to find Document
You are right, this was only possible in early versions...
You have to write a non anonymous public subclass of FilterCodec and list it in
your META-INF/services folder.
Vitaly Funstein schrieb:
>Yes, I thought about inlining an anonymous subclass of Lucene41Codec
>but
>unfortunately all of
Yes, I thought about inlining an anonymous subclass of Lucene41Codec but
unfortunately all of its methods are final, which effectively rules out
this approach. I think I may have to do the latter, since I am obviously in
control of internal JAR packaging anyway...
On Wed, May 15, 2013 at 4:06 PM,
You don't change the Codec at all just the stored fields implementation, so you
dont need to give it a new name. The simpliest is to anonymous subclass
Lucene41Codec without FilterCodec.
If your codec gets a new name, this name must be regustered in the codec
manager by adding META-INF files t
Uwe,
I may not be doing this correctly, but I tried to see what would happen if
I were to a reopen an index created with a custom codec that disables
stored fields compression, and it doesn't seem to work. Here's how I
configure the writer to disable compression, prior to indexing:
final
This seems like a bug caused due to the fact that we moved the CFS
building into DWPT. Can you open an issue for this?
simon
On Wed, May 15, 2013 at 5:50 PM, Sergiusz Urbaniak
wrote:
> Hi all,
>
> We have an obvious deadlock between a "MaybeRefreshIndexJob" thread
> calling ReferenceManager.mayb
Yes. You can also force this by using IW.forceMerge(1), unless your index is
not already consisting of only one segment. Another alternative is to use
IndexUpgrader, but this one would only merge if there are segments created with
an older Lucene version. You can change this by overriding IndexU
Thanks for the quick reply, this is certainly good news. So just to clarify
- doing a manual segment merge is optional when changing codecs, correct? I
mean, I can just restart my application with a new codec config and let the
regular, background merging task do the work of eventually converting a
Hi Vitaly,
what you call an "index" is just a collection (a CompositeReader) of atomic
readers. They can be mixed regarding compression, just like you could have a
MultiReader with different indexes using different codecs. Every atomic segment
of an index can only have one stored fields format.
Is it possible to have a mix of compressed and uncompressed documents
within a single index? That is, can I load an index created with Lucene 4.0
into 4.1 and defer the decision of whether or not to use
CompressingStoredFieldsFormat until a later time, or even go back and forth
between compressed a
Hi all,
We have an obvious deadlock between a "MaybeRefreshIndexJob" thread
calling ReferenceManager.maybeRefresh(ReferenceManager.java:204) and a
"RebuildIndexJob" thread calling
IndexWriter.deleteAll(IndexWriter.java:2065).
Lucene tries to flush in the "MaybeRefreshIndexJob" thread while
simult
Are the indexes on local disks? Is the same index present on all 6
servers or split or different or what? Do you see the slowdown on all
servers/indexes or what? Any IO/memory/CPU problems being reported
anywhere? Are you always loading the same fields with approx the same
volume of data or do y
See
http://search-lucene.com/m/Z2GP220szmS&subj=RE+What+is+equivalent+to+Document+setBoost+from+Lucene+3+6+inLucene+4+1+
--
Ian.
On Tue, May 14, 2013 at 3:34 PM, Tamer Gür wrote:
> Hello all,
>
> i was wondering why unindexed fields can't be boosted compare to lucene 3.
> since these fields ar
there is also elasticsearch (elasticsearch.org) build on top of lucene
that might feel more natural if you come from mongo
simon
On Wed, May 15, 2013 at 11:38 AM, Rider Carrion Cleger
wrote:
> Thanks you Hendrik,
> I'm new with Apache Lucene, the problem that arises is like starting with
> lucen
Thanks you Hendrik,
I'm new with Apache Lucene, the problem that arises is like starting with
lucene-solr ASAP, in order to move quickly in my project.
Do you know a guide or ejemple code about how does lucene-solr works (
storing index in solr as you say) ?
Kind regards,
Rider
On Wed, May 1
17 matches
Mail list logo
