-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Friday, August 24, 2012 9:52 AM
To: java-user@lucene.apache.org
Subject: Re: Problem with TermVector offsets and positions not being preserved
Calling IR.document does not restore your 'original Document'
completely. This is really an ag
> supposed to work this way? What is it about closing the writer that alters
> the term vectors in the affected fields? Is there a way to add a field to the
> documents in an index in which this doesn't occur?
> Thanks,
> Mike
>
>
> -Original Message-
> F
term vectors
in the affected fields? Is there a way to add a field to the documents in an
index in which this doesn't occur?
Thanks,
Mike
-Original Message-
From: Robert Muir [mailto:rcm...@gmail.com]
Sent: Friday, July 20, 2012 5:59 PM
To: java-user@lucene.apache.org
Subje
On Fri, Jul 27, 2012 at 9:10 AM, Andrzej Bialecki wrote:
>
> Catching up with this thread ... Luke 4.0-ALPHA makes a similar mistake. I
> fixed this in svn (to be released in a week or so) so that:
>
> * Luke now actually checks whether a doc has term vectors for a particular
> field and adjusts t
012 5:59 PM
To: java-user@lucene.apache.org
Subject: Re: Problem with TermVector offsets and positions not being preserved
On Fri, Jul 20, 2012 at 8:24 PM, Mike O'Leary wrote:
Hi Robert,
I'm not trying to determine whether a document has term vectors, I'm trying to
determine whet
Subject: Re: Problem with TermVector offsets and positions not being preserved
On Fri, Jul 20, 2012 at 8:24 PM, Mike O'Leary wrote:
> Hi Robert,
> I'm not trying to determine whether a document has term vectors, I'm trying
> to determine whether the term vectors that are in th
On Fri, Jul 20, 2012 at 8:24 PM, Mike O'Leary wrote:
> Hi Robert,
> I'm not trying to determine whether a document has term vectors, I'm trying
> to determine whether the term vectors that are in the index have offsets and
> positions > stored.
Right: what i'm trying to tell you is that offsets
o: java-user@lucene.apache.org
Subject: Re: Problem with TermVector offsets and positions not being preserved
I think its wrong for DumpIndex to look at term vector information from the
Document that was retrieved from IndexReader.document, thats basically just a
way of getting access to your store
out.writeEndElement();
> out.writeEndDocument();
> out.flush();
> reader.close();
> }
>
> private void dumpDocument(Document document, XMLStreamWriter out)
> throws XMLStreamException {
>
-user@lucene.apache.org
Subject: RE: Problem with TermVector offsets and positions not being preserved
Hi Robert,
I put together the following two small applications to try to separate the
problem I am having from my own software and any bugs it contains. One of the
applications is c
eld.name());
out.writeAttribute("value", field.stringValue());
out.writeEndElement();
}
out.writeEndElement();
}
}
-
Hi Mike:
I wrote up some tests last night against 3.6 trying to find some way
to reproduce what you are seeing, e.g. adding additional segments with
the field specified without term vectors, without tv offsets, omitting
TF, and merging them and checking everything out. I couldnt find any
problems.
I created an index using Lucene 3.6.0 in which I specified that a certain text
field in each document should be indexed, stored, analyzed with no norms, with
term vectors, offsets and positions. Later I looked at that index in Luke, and
it said that term vectors were created for this field, but
13 matches
Mail list logo
