info about private int processField(IndexableField field, long fieldGen, int fieldCount)

2016-08-22 Thread Cristian Lorenzetto
i m investigating about the update method for understanding if it is possible update a single field , not only all document the code try { for (IndexableField field : docState.doc) { fieldCount = processField(field, fieldGen, fieldCount); } seams to tell that is not so d

Re: Using Lucene's Multi Dimensional Space Search for Air traffic handling.

2016-08-22 Thread Michael McCandless
Hi Janaka, Unfortunately, Geo3D does not in fact search three dimensions: it only handles the same 2D earth surface as lat/lon. It's just that, internally, it's using three x,y,z coordinates to do all its math. But those three coordinates must be on the earth's surface for the math to be correct

Re: info about private int processField(IndexableField field, long fieldGen, int fieldCount)

2016-08-22 Thread Michael McCandless
The problem is how you implement that method to push changes down to the inverted index, which has written postings for this field and document ID to several files already. You would probably need some sort of approach that can delete the old docID, from just this one field, and then add new posti

inverted table

2016-08-22 Thread Cristian Lorenzetto
i have a curiosity when a document is updated or deleted , lucene must update inverted table. considering the size of record about a specific term (before used) is changing ... how lucene resave term record? maybe flag the old term row as tombstone?

Re: inverted table

2016-08-22 Thread Adrien Grand
Lucene only marks documents as deleted, it keeps the inverted index as-is. Deleted terms are only expunged at merge time since Lucene ignores terms that only match deleted documents. Le lun. 22 août 2016 à 14:21, Cristian Lorenzetto < cristian.lorenze...@gmail.com> a écrit : > i have a curiosity

Re: Problems Refactoring a Lucene Index

2016-08-22 Thread Michael McCandless
This is unfortunately "by design": Lucene makes no guarantees that the Document you retrieve from an IndexReader is precisely the same Document you had indexed. Lucene only preserves the metadata it needs for each field. Your only recourse is to create a new Document using your application level

RE: Problems Refactoring a Lucene Index

2016-08-22 Thread Stuart Goldberg
Thanks for the quick response. I kind of figured on my own that I had to recreate the document from scratch But there is something in your response that I don’t understand. You say “Lucene only preserves the metadata it needs for each field”. What does that mean? In my posting I gave exam

Re: searchAfter behavior after reindexing

2016-08-22 Thread Rajnish kamboj
Please help me in understanding the behaviour of searchAfter(). On Sunday 21 August 2016, Rajnish kamboj wrote: > Hi Team > > What is the searchAfter behavior if index is continuously being updated. > Document numbers changes if indexes are updated. Also indexes are update > on segment merge. >

RE: searchAfter behavior after reindexing

2016-08-22 Thread Uwe Schindler
Hi, SearchAfter always reexecutes the whole query regardless if the index changed or is a new index. It just sorts out documents, which are not part of the topdocs based on the criteria passed in as the last doc. It does this by comparing the docid and score before inserting it into the priorit

Text field matching

2016-08-22 Thread Jeremy Glesner
Good day, I'm trying to get my head wrapped around one of the fundamental aspects of Lucene ... whether or not I need to index the document a certain way in order to query it the way I want. I'm inserting documents using a Whitespace Tokenizer to process content into a Lucene 5.4.1 index. Here's

Re: Problems Refactoring a Lucene Index

2016-08-22 Thread Michael McCandless
The design is indeed trappy, and many users have hit the situation you have, and we have tried to fix this before (to change IndexReader.document to return a different class than Document), but it didn't "take": https://issues.apache.org/jira/browse/LUCENE-6971 Have a look at FieldInfo.java to see

RE: Problems Refactoring a Lucene Index

2016-08-22 Thread Stuart Goldberg
Understood, but did it used to work? Stuart M Goldberg Senior Vice President of Software Develpment FIX Flyer LLC http://www.FIXFlyer.com/ NOTICE TO RECIPIENT: THIS E- MAIL IS MEANT ONLY FOR THE INTENDED RECIPIENT(S) OF THE TRANSMISSION, AND CONTAINS CONFIDENTIAL INFORMATION WHICH IS PROPRIE

Re: Problems Refactoring a Lucene Index

2016-08-22 Thread Michael McCandless
It has never worked, though I do think the metadata has changed over time, so the degree to which it didn't work has changed? Mike McCandless http://blog.mikemccandless.com On Mon, Aug 22, 2016 at 4:41 PM, Stuart Goldberg wrote: > Understood, but did it used to work? > > > > Stuart M Goldberg

Re: Lucene commit

2016-08-22 Thread Paul Masurel
Awesome! Thank you very much! On Mon, Aug 22, 2016 at 3:45 PM, Christoph Kaser wrote: > Hello Paul, > > this is already possible using > DirectoryReader.openIfChanged(indexReader,indexWriter). > This will give you an indexreader that already "sees" all changes made by > the writer (up to that

Fwd: Warning from java-user@lucene.apache.org

2016-08-22 Thread Phaneendra N
Hi, Is there anything i can do from my end to fix this bouncing problem? I'm not sure what is wrong with my id. I am able to send/receive e-mails. Anyone please advise. Thanks Phaneendra -- Forwarded message -- From: Date: Tue, Aug 23, 2016 at 4:21 AM Subject: Warning from java