lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <e...@ehatchersolutions.com>
Subject Re: Text storing design and performance question
Date Wed, 10 Jan 2007 16:20:52 GMT
You don't have to store a field to highlight text.  If you've got it  
in your database, retrieve it from there and pass that string to the  
highlighter instead.

	Erik


On Jan 10, 2007, at 10:45 AM, moraleslos wrote:

>
> I'm running into a little dilemma with Lucene highlighting and  
> indexing.  I
> currently index anything and everything that gets inserted into a  
> database.
> This database includes all the content that is searched.  Now I'll  
> have lots
> and lots of content, thinking of the range of 50GB+, all stored in  
> the DB.
> Using Lucene, I index all of this.  But since I'm using highlighting
> features, I'll also need to store the content into the index.  Not  
> sure what
> the performance implications are during a search but I know that  
> indexing
> performance should be slower as well as the index size being enormous.
> Because I have duplicated data, one in the index and the other in  
> the db,
> are there other ways of handling this situation in a more efficient  
> and
> performant way?  Thanks in advance.
>
> -los
> -- 
> View this message in context: http://www.nabble.com/Text-storing- 
> design-and-performance-question-tf2953201.html#a8259883
> Sent from the Lucene - Java Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
> For additional commands, e-mail: java-user-help@lucene.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org


Mime
View raw message