Re: re-mapping lucene index

if > you still have readers open on the index. > > Regardless of which approach you use, the old mappings will remain > "alive" until you've closed all open readers agains the old index. > > Mike McCandless > > http://blog.mikemccandless.com > > > On Tue,

Re: re-mapping lucene index

t; > On Tue, Feb 10, 2015 at 1:31 PM, Vijay B wrote: > > We use MMapdirectory impl. in our search application. Occasionally we > need > > to do a full indexing by dropping entire directory contents. How does > > re-mapping work with MMapDirectory as the directory contents

re-mapping lucene index

We use MMapdirectory impl. in our search application. Occasionally we need to do a full indexing by dropping entire directory contents. How does re-mapping work with MMapDirectory as the directory contents are going to replace with new ones? is this going to be seamless or an application restart re

Lucene improvements

We our production app uses Lucene 4.2.1. We are going to release a new version soon and contemplating whether or not to migrate to newer version of lucene. I see lot of new features were added in later versions but I want to get an idea of performance improvements?

MMapdirectory Configuration

Finally we are seeing great improvement once we switch to 64-bit java and MMapDirectory. Our Test run (multiple requests) used to take 26 minutes on 32-bit and is now improved to 10 minutes on 64-bit java. We load stored documents from lucene and pass the documents to a third party libray (closed

Benchmark testing Lucene index

We have our index located on NFS. While benchmark testing, we noticed first query would take lot of time and same query for the second time complete quickly. One of the reason for this could be fscache. To eliminate effect of caching, before start of we plan to umount and mount the NFS filesystem o

MMapdirectory

> > Finally we are seeing great improvement once we switch to 64-bit java and > MMapDirectory. Our Test run (multiple requests) used to take 26 minutes on > 32-bit and is now improved to 10 minutes on 64-bit java. > > We load stored documents from lucene and pass the documents to a third > party li

Re: unsafe memory access operation

for the error you see here. > > I would recommend to update to 1.7.0_72 or 1.8.0_25. > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > > -Original Message- > > F

Re: unsafe memory access operation

VM (build 23.25-b01, mixed mode) On Fri, Dec 12, 2014 at 12:51 PM, Vijay B wrote: > > Here is the info you requested: > > java version "1.7.0_25" > Java(TM) SE Runtime Environment (build 1.7.0_25-b15) > Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode) &g

Re: unsafe memory access operation

/ update level are you using? Those errors occur > easily if you use an outdated JDK version. > > Uwe > > - > Uwe Schindler > H.-H.-Meier-Allee 63, D-28213 Bremen > http://www.thetaphi.de > eMail: u...@thetaphi.de > > > -Original Message- > > From: Vi

unsafe memory access operation

we are running into this issue for the first time while searching a lucene index hosted on NFS. Once, this error occurs, all subsequent requests fails. help appreciated. Our Config: 64-bit Java 1.7 (we are making use of MMapDirectory) Lucene 4.2.1 Index size: 8GB Let me know if you need any f

Re: Index replication strategy

rera.blogspot.com/2013/05/the-replicator.html. > > Shai > > On Thu, Dec 4, 2014 at 4:36 PM, Vijay B wrote: > > > As indicated in my post, we use Lucene 4.2.1. > > > > On Thu, Dec 4, 2014 at 9:29 AM, Shai Erera wrote: > > > > > Do you use Lucene or S

Re: Index replication strategy

As indicated in my post, we use Lucene 4.2.1. On Thu, Dec 4, 2014 at 9:29 AM, Shai Erera wrote: > Do you use Lucene or Solr? Lucene also has a replication module, which will > allow you to replicate index changes. > > On Thu, Dec 4, 2014 at 4:19 PM, Vijay B wrote: > > > He

Index replication strategy

Hello, We index docs coming from database nightly. Current index is sitting on NFS. Due to obvious performance reasons, we are switching are planning to switch to local index. W have cluster of 4 servers and with NFS it was not a problem for us until now to share the index. but going forward, we a

Re: Order docIds to reduce disk seeks

icient to iterate through all of the stored fields. I'm not sure how to do this with the API however. Could you please eloborate more on this. On Wed, Nov 19, 2014 at 5:59 AM, Barry Coughlan wrote: > Hi Vijay, > > Could you just bypass Lucene altogether and send the documents to

Re: Order docIds to reduce disk seeks

ot2/core/Document.html> constructed out of document title and complete text. <http://download.carrot2.org/stable/javadoc/org/carrot2/core/Document.html#Document(java.lang.String, java.lang.String, java.lang.String)> On Tue, Nov 18, 2014 at 2:53 PM, Barry Coughlan wrote: > Hi Vijay, &

Re: Order docIds to reduce disk seeks

to visit every > single one and load the stored document ... > > Try to find another way to solve your problem, making use of the inverted > index? > > Mike McCandless > > http://blog.mikemccandless.com > > > On Mon, Nov 17, 2014 at 6:05 PM, Rose, Stuart J > wrote: >

Re: Order docIds to reduce disk seeks

Thank you Stuart. I got it working with: // sort by docids Arrays.sort(scoreDocs, new Comparator() { @Override public int compare(ScoreDoc o1, ScoreDoc o2) { return Integer.compare(o1.doc, o2.doc); } }); On Mon, Nov 17, 2014 at 6:05 PM, Rose, Stuart J wrote: > Hi Vijay, > > ...so

Order docIds to reduce disk seeks

*Could someone point me how to order docIds as per **http://wiki.apache.org/lucene-java/ImproveSearchingSpeed * *"Limit usage of stored fields and term vectors. Retrieving these from the index is quite costly. Typically you should only retr

Re: Using Lucene with an existing dataset

/apache/lucene/search/Searcher.html#setSimilarity(org.apache.lucene.search.Similarity) . -- Vijay - Original Message > From: hari narayanan > To: java-user@lucene.apache.org > Sent: Sun, March 27, 2011 2:15:54 PM > Subject: Using Lucene with an existing datase

Using Lucene to Query File properties in Windows

Hi , I am planning to use Apache lucense in one of my projects, I want to index files based on the file properties (I won’t be indexing the data) and I want lucense to query the index so that I can quickly find list

Re: Using IndexReader in the web environment

/indexer and the web application, are totally different. Vijay On 5/4/10, Ian Lea wrote: > For best performance you should aim to keep a shared index searcher, > or the underlying index reader, open as long as possible. You may of > course need to reopen it if/when the index changes. As

Re: Using IndexReader in the web environment

Hi, Thanks for the reply. So I will have a dedicated servlet to search the index, but does it mean that the indexsearcher does not close the index, keep it open? Is it not possible to keep it in the application scope? Vijay On 5/3/10, Vijay Veeraraghavan wrote: > Hi all, > > In a

Using IndexReader in the web environment

IndexReader in the session/application scopes and use the same for each request? Any other idea? Viay On 5/3/10, Vijay Veeraraghavan wrote: > dear all, > > as replied below, does searching again for the document in the index > and if found skip the indexing else index it, is this no

Re: Indexing only newly created files

need not reindex it) but just the paths of the documents. Vijay >> Hey there, >> >> you might have to implement a some kind of unique identifier using an >> indexed lucene field. When you are indexing you should fire a query with >> the >> uuid of your document

Re: Indexing only newly created files

and save the pdfs to a remote file server. Is it advisable to create a local index and add it the main index shared by the nodes? Or create a local index and copy it to the nodes? Thanks Vijay On 5/3/10, Simon Willnauer wrote: > Hey there, > > you might have to implement a some kind

Indexing only newly created files

parameter is for this purpose? Please guide me. -- Thanks Vijay Veeraraghavan -- Thanks & Regards Vijay Veeraraghavan - To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-us

Re: Using lucene in NFS

solution? Thanks Vijay On 4/30/10, Ian Lea wrote: > You don't say what version of lucene you are using, but in recent > versions you may need to use SimpleFSLockFactory rather than the > default, NativeFSLockFactory. See the javadocs. Lucene in general > does work on NFS but ther

Using lucene in NFS

need to do? any reference codes? docs? How do i lock the index when my scheduler is updating the index? P.S: Please add CC to vij...@kggroup.com Thanks Vijay Veeraraghavan -- Thanks & Regards Vijay Veeraraghavan

Question on Efficient field updates in the Lucene index in Nutch

creating the same effect as indexing the webpage afresh with all the given tags? Alternatively is there any other efficient way to do this? Thanks a ton, Vijay

Problem compiling with JBoss portal server

t have the MultiFieldQueryParser constructor that takes 3 params. Problem should be fixed with moving to a newer version of the Jboss portal or replacing the lucene.jar with the newer version of lucene.jar in the portal-cms.sar/lib folder. Vijay Kumar, Rackspace Managed Hosting Confi

Exact searches with PhraseQuery

Otherwise; Between SpanFirstQuery, RegexQuery and the many other solutions at http://www.nabble.com/Search-for-docs-containing-only-a-certain-word-in-a-sp ecified-field--tf3655925.html I should have a good solution. Thanks for your help Guys! Vijay Santhanam B.Eng.(Soft.) Spectrum Wired

Exact field searches

ot;Tomorrow the Pink" appear in the results (along with the CDs just titled "Pink"). Obviously, the PhraseQuery finds instances of that phrase in the title field, but I need to somehow exclude those titles that have a different number of tokens from the query. How do I make search fo

Multiple time ranges in a document

respective term positions for each field. Thanks for your help, -Vijay

My Category Search Problem

Hi Lucene Users! I've been playing around with dotLucene on a few projects since for about 4 months, and I've found Lucene to be exceptionally powerful, speedy and thanks to LIA, really easy to use. But I've hit a problem that I fear will pose a performance problem for our architecture and Lu