Return-Path: 
 <users-return-13407-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org>
Delivered-To: apmail-jackrabbit-users-archive@minotaur.apache.org
Received: (qmail 22700 invoked from network); 21 Nov 2009 00:10:52 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 21 Nov 2009 00:10:52 -0000
Received: (qmail 71039 invoked by uid 500); 21 Nov 2009 00:10:52 -0000
Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org
Received: (qmail 70997 invoked by uid 500); 21 Nov 2009 00:10:51 -0000
Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@jackrabbit.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@jackrabbit.apache.org>
List-Post: <mailto:users@jackrabbit.apache.org>
List-Id: <users.jackrabbit.apache.org>
Reply-To: users@jackrabbit.apache.org
Delivered-To: mailing list users@jackrabbit.apache.org
Received: (qmail 70986 invoked by uid 99); 21 Nov 2009 00:10:51 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Nov 2009 00:10:51 +0000
X-ASF-Spam-Status: No, hits=-2.6 required=5.0
	tests=BAYES_00
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of
 lists+1257438615597-510167@n4.nabble.com designates 216.139.236.158 as
 permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 Nov 2009 00:10:48 +0000
Received: from joe.nabble.com ([192.168.236.151])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists+1257438615597-510167@n4.nabble.com>)
	id 1NBdYZ-0002Ow-Jn
	for users@jackrabbit.apache.org; Fri, 20 Nov 2009 16:10:27 -0800
Date: Fri, 20 Nov 2009 16:10:27 -0800 (PST)
From: pkrishnaswami <prabhakar.krishnaswami@ge.com>
To: users@jackrabbit.apache.org
Message-ID: <1258762227607-633631.post@n4.nabble.com>
Subject: Writing indexes takes a long time
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: pkrishnaswami <prabhakar.krishnaswami@ge.com>


We have observed that writing out JackRabbit indexes takes an unduly long
time and we suspect this could be because of payload indexing. I would like
some clarity on this. Here is the scenario:


We save custom Nodes in our repository. Our custom Node (call A) extends
nt:file and has many properties. In addition,we also make this custom node a
parent to another custom node (call B) that extends nt:resource. We have an
indexConfiguration file that specifically defines which properties in node
"A" will be indexed. Custom Node B only contains a binary representation of
XML or plain text contents (let call it payload). We specifically omitted an
index-rule for custom Node B since we did not want the payload to be
indexed, Would this disable indexing of payload?

I was reading up some documentation  of Nabble forum and there was a comment
in one of the posts that the default configuration disables full-text
indexing. What does this mean? It goes on to say that if full-text indexing
is required, then we have to configure a SearchIndex section in
repository.xml along with textFilterClasses property pointing to different
extractors. I looked up the repository.xml we were using and sure enough
there was a section like this:

	<SearchIndex
		class="org.apache.jackrabbit.core.query.lucene.SearchIndex">
		
		
	
		
		
	</SearchIndex>

Does this activate payload indexing? If it does, does it override the
indexConfiguration file? If we didn't want payload indexing, should I
comment or remove the param related textFilterClasses?
-- 
View this message in context: http://n4.nabble.com/Writing-indexes-takes-a-long-time-tp633631p633631.html
Sent from the Jackrabbit - Users mailing list archive at Nabble.com.