Mailing-List: contact user-help@lucenenet.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@lucenenet.apache.org
Message-ID: <BLU180-W408CFE21D70FFCE0541C7FF6A90@phx.gbl>
Content-Type: multipart/alternative;
	boundary="_bd3a0840-774c-4cd9-878d-52909ac515a0_"
From: Monica Black <ml_black@hotmail.com>
To: "user@lucenenet.apache.org" <user@lucenenet.apache.org>
Subject: Lucene.Net 4.8 Directory question
Date: Mon, 24 Oct 2016 14:34:22 -0300
Importance: Normal
MIME-Version: 1.0
archived-at: Mon, 24 Oct 2016 17:35:58 -0000

--_bd3a0840-774c-4cd9-878d-52909ac515a0_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Lucene Devs.
I am using Lucene again after many years for data caching in an application=
 where we didn't want a lot of components to install.  It's really quite pe=
rfect for this.
The question I have is how best to approach the use of directories=2C indic=
es=2C and searchers.
My cache is structured with a Lucene cache per subdirectory (lowest leaves =
only) like so:-Address Type 1----AK----AL----AR.....
-Address Type 2----AK----AL----AR.....
and so on for each US State.
The bad thing about this type of cache breakdown is that I need one FSDirec=
tory for each of two address types per US State--that's a lot of FSDirector=
ies.  I notice the FSDirectory is very slow to open. =20
This will be a library called from another application=2C so I have no way =
to know how many queries the application would need per cache.  What do you=
 suggest to avoid this slow opening of FSDirectory over and over?
Thanks=2CMonica 		 	   		  =

--_bd3a0840-774c-4cd9-878d-52909ac515a0_--