A question about "seek past EOF: MMapIndexInput"

Hi, folks I build lucene index using lucene-4.3. However, I found for a field, some terms are searchable while searching the others will throw the following exception: java.io.EOFException: seek past EOF: MMapIndexInput(path="/tmp/galeneTestData/input/base/index/_2ca_Lucene41_0.doc") at org.

Re: Can you escape characters you don't want the analyzer to modify

It sounds like you either need to have a custom analyzer or a field-aware analyzer. -- Jack Krupansky -Original Message- From: Scott Smith Sent: Tuesday, September 17, 2013 4:26 PM To: java-user@lucene.apache.org Subject: Can you escape characters you don't want the analyzer to modify

How to modify the Lucene 4 index?

Hi all, is there any good documentation of how to change and modify the index of Lucene version 4 other than what is already on the website? Blogs, papers, reports etc. or just a report on experience in some form --- anything would be good. Based on an early-stage project, I would like to ge

Re: IndexUpdater (4.4.0) fails when -verbose is not set

Done. LUCENE-5223 On Mon, Sep 16, 2013 at 6:39 PM, Uwe Schindler wrote: > Hi Bruce, > > Thanks for investigating! Can you open a bug report on > https://issues.apache.org/jira/browse/LUCENE ? > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Al

Can you escape characters you don't want the analyzer to modify

Suppose I have a string like "ab@cd%d". My analyzer will turn this into "ab cd d". Can I pass it "ab\@cd\%d" and force it to treat it as a single word? I want to use the Query parser, but I don't want it messing with fields that have not been analyzed.

Position problems in 4.3.0

Most of my terms return the correct position that they are in, but there is a percent or them that return really bad values. For example, I have a field that contains 5 terms, when I ask for term position of one of the terms (that I know is in position 3) I am getting a value of 43 returned. If I

Re: SPI class of type org.apache.lucene.codecs.Codec error

Hey, I had the same problem and it was only due to the Maven Shade plugin configuration. As mentioned earlier you should edit your pom.xml like that: http://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html#ServicesResourceTransformer

Writing Lucene analyzers - in Scala

I know this is the Lucene Java forum but it seemed vaguely appropriate. I'm using Lucene from Scala and I needed to subclass a couple of the analyzers to set the position increment gap. As the standard analysers in question were all final classes I couldn't simply subclass them. However it's pe

Re: Multiple field instances and Field.Store.NO

On 17/09/2013 13:03, Michael McCandless wrote: I haven't fired up Luke for a while, but it is really useful in general ) Yes, It's been invaluable. But, this does sound confusing. It could be it's telling you all fields that are present in this segment, regardless of whether that one docume

Re: Search in a specific ScoreDiopoc result

Kkkutterujjjbbb hgggja Den 17/09/2013 12.55 skrev "David Miranda" : > > Hi, > > I want to do a kind of 'facet search', that initial research in a field of > all documents in the Lucene index, and second search in other field of the > documents returned to the first research. > > Currently I'm do th

Re: Search in a specific ScoreDoc result

Why not? You can use a standard query as a filter query from the Solr side, so it's got to be possible in Lucene. What about using filters doesn't seem to work for this case? Best, Erick On Tue, Sep 17, 2013 at 6:54 AM, David Miranda wrote: > Hi, > > I want to do a kind of 'facet search', that

Re: exception while writing to index

On Mon, Sep 16, 2013 at 3:12 PM, nischal reddy wrote: > I seem to be getting this error when i hit the max rambuffer size and > lucene is trying to flush my ram. > > When i debugged i found out that there were couple of negative values in > offsetStartDeltaBuffer field of "Lucene41PostingsWriter"

Re: Multiple field instances and Field.Store.NO

On Tue, Sep 17, 2013 at 6:27 AM, Alan Burlison wrote: > On 16/09/2013 19:04, Alan Burlison wrote: > >>> Is Luke showing you stored fields? If so, this makes no sense ... >>> Field.Store.NO (single or multiple calls) should have resulted in no >>> stored fields. >> >> >> It shows the field but sho

Search in a specific ScoreDoc result

Hi, I want to do a kind of 'facet search', that initial research in a field of all documents in the Lucene index, and second search in other field of the documents returned to the first research. Currently I'm do the first research : Query q = new QueryParser(Version.LUCENE_43, "label", analyzer

Re: Multiple field instances and Field.Store.NO

On 16/09/2013 19:04, Alan Burlison wrote: Is Luke showing you stored fields? If so, this makes no sense ... Field.Store.NO (single or multiple calls) should have resulted in no stored fields. It shows the field but shows the content as I think perhaps what I'm seeing is an artefact of how

Re: Regarding Compression Tool

Thanks Mark. I know all this scenarios about battery and space. But at the same I am just checking the feasibility only. Actually I started this to ask how to use the CompressionTool to compress the data and store it in index. I observed the below things and I tried using this way * Field field =