Re: Adding a new field to existing Index

yes, with lucene's current API's, it does not seem possible. But, as this is a problem that many might be facing, I was hoping someone might have figured out a solution. On Tue, Jun 29, 2010 at 5:29 PM, Mango wrote: > Unfortunately, I don't think it is possible to add new field without > re-ind

Re: Document Order in IndexWriter.addIndexes

On 2010-06-30 05:12, Apoorv Sharma wrote: > while calling addindexes or addindexes with no optimize can any gurantee be > given about the document order in the new documents given that the order of > directories/indexreader is fixed. > > So is it that ith document coming from jth indexreader will

inverted index in clucene

Hello , Can we use subset of documents , for searching . Lets say I have hash map of P1 -1,2,3,4 P2 - 3,4,5 P3-7,5,3 Now I have an documents in lucene index stored as 1-P1 2-P1 3-P1,P2,P3 4-P1,P2 5-P2,P3 7-P3 .. .. when i search docs with P2 I get 3,4,5 Now I want

Re: example of processing tokens from query results?

Similar kind of code is given in Lucene in Action 2nd edition book , you can dwld the code from the manning website. On Wed, Jun 30, 2010 at 2:11 AM, Peter Wilkins wrote: > Can someone point me to a code example that demonstrates processing tokens > from a query result? I want to iterate over

Document Order in IndexWriter.addIndexes

while calling addindexes or addindexes with no optimize can any gurantee be given about the document order in the new documents given that the order of directories/indexreader is fixed. So is it that ith document coming from jth indexreader will always have some x(i,j) position in the final merged

Re: A question regarding the setSlop method of class PhraseQuery (Lucene version 3.0.1)

No, I really don't have a good solution off the top of my head, perhaps others can chime in... Although I suppose you could fire multiple queries dropping out some number of search terms, but I don't know whether that satisfies your requirements. E.g. search the following phrases "this is a formal

Re: A question regarding the setSlop method of class PhraseQuery (Lucene version 3.0.1)

Hi Erick, Any comments about this requirement? 2010/6/29 a peng > Hi Erick, > > Thanks for you reply, now I get the point why I can not get the search > result. But can you guide me how can I use Lucene to implement the following > search feature: > Basically we can call this feature "fuzzy phr

AUTO: Paul Magrath is out of the office (returning 01/07/2010)

I am out of the office until 01/07/2010. Note: This is an automated response to your message "example of processing terms in query results?" sent on 29/6/10 18:09:45. This is the only notification you will receive while this person is away. -

example of processing tokens from query results?

Can someone point me to a code example that demonstrates processing tokens from a query result? I want to iterate over TermPositions but can't find my way to an object that instantiates that interface. Thank you for the assistance, Peter ---

example of processing terms in query results?

Can someone point me to a code example that demonstrates processing terms from a query result? I want to extract payloads from the terms that are selected by the query. I'm having difficulty getting to an object in the query result that implements getPayload(). Thank you for the assistance, P

IndexWriter.mergeDocument(Term term, Document doc)

Hi all, I'm looking for a functionality similar to IndexWriter.updateDocument() *IndexWriter.**updateDocument *(Term

Re: Adding a new field to existing Index

Unfortunately, I don't think it is possible to add new field without re-indexing. As for extracting content from the field, it should be possible to retrieve data if the term vectors were stored with positions offset (Field.TermVector.WITH_POSITIONS_OFFSETS). If not, I don't think it's possible.

Adding a new field to existing Index

Hey, I need to add a new field (a stored , not indexed field) for all documents present in an existing large index. Reindexing the whole index will be very costly. Is there a way to do this or any work around? I would also like to know, if data or term vector, of a field indexed without storing,

Re: Date Fields

I was afraid this would be the answer.. Thanks a lot! Liat On 29 June 2010 12:03, Ian Lea wrote: > How are you searching? If looking for exact dates I guess you could > make it work by passing in the exact value but ranges would be > challenging. > > My advice would be to upgrade to a current v

Unsupported operation in TermDocs.next() when migrating from 2.4 to 2.9

Hi All, I am finally having some time to upgrade our lucene from the 2.4 series to the 2.9 series. And I am having a problem that while everything compiles great I am getting a new UnsupportedOperationException. java.lang.UnsupportedOperationException at org.apache.lucene.index.AbstractAll

Re: Lucene In Action free chapter on CLucene

You're welcome! One small clarification: it's the section (10.2 -- CLucene) not the whole chapter 10 that's free for downloading... Mike On Mon, Jun 28, 2010 at 4:57 PM, Itamar Syn-Hershko wrote: > Hi, > > > Just to let everyone know Manning have released an extra chapter from the > excellent L

Re: Date Fields

How are you searching? If looking for exact dates I guess you could make it work by passing in the exact value but ranges would be challenging. My advice would be to upgrade to a current version of Lucene and reindex everything with the date as a NumericField. -- Ian. On Tue, Jun 29, 2010 at

Re: searching for wildcard as valid character

Thank you all for your support. I'm using now RegEx query from Lucene Contrib package which handles it fine in my unit test. I'm waiting for confirmation from the other developer team if this fixed their issue. -- View this message in context: http://lucene.472066.n3.nabble.com/searching-for-

Date Fields

Hi all, I made a mistake, finished indexing all my database (millions of documents..), regarding field dates as usual fields. Instead of doing: doc.add(Field.Keyword("indexDate", new Date()); I added it as: doc.add(new Field("indexDate", String.valueOf(new Date().toString()), Field.Store.YES, Fiel