Mailing-List: contact java-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-user@lucene.apache.org
Received-SPF: pass (athena.apache.org: domain of youngestachiever@gmail.com
 designates 209.85.215.43 as permitted sender)
MIME-Version: 1.0
Date: Mon, 10 Jun 2013 18:05:34 +0530
Message-ID: 
 <CAPzrt-2+HvNU2Z2KNhmJbuhcSe7cJmr_Q_hKLPkDt0+Uj8cp6A@mail.gmail.com>
Subject: TermsEnum close()
From: Ramprakash Ramamoorthy <youngestachiever@gmail.com>
To: java-user@lucene.apache.org
Content-Type: multipart/alternative; boundary=089e0158c09a60d2b204decc0433

--089e0158c09a60d2b204decc0433
Content-Type: text/plain; charset=ISO-8859-1

Dear all,

          We recently migrated from lucene 2.3.1 to lucene 4.1. We have a
custom facet implementation, which has also been migrated. We resorted to
stay with the same facet approach instead of moving to the taxonomy index
style faceting.

          But the problem is that, whenever we do a continuous/deep drill
down with the faceting module, we get a too many files open exception. This
does not happen when searching multiple times through the same index.

          One suspect is that we had a TernEnum.close() in the earlier
versions, whereas we don't have a TermsEnum.close() in the current version.
Is it the TermsEnum and/or DocsEnum that is occupying namespaces? Is there
a way to close the same? Please help. TIA.

-- 
With Thanks and Regards,
Ramprakash Ramamoorthy,
Chennai, India

--089e0158c09a60d2b204decc0433--