<br><br><div><span class="gmail_quote">On 3/1/06, <b class="gmail_sendername">Olly Betts</b> <<a href="mailto:olly@survex.com">olly@survex.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Wed, Mar 01, 2006 at 01:58:50PM -0500, jarrod roberson wrote:<br>> On to my delimna, I want to index arbitarly long logical paths. And I have<br>> run up on the ~240 character term limit way more than once so far.
<br>> So I am trying to decide the best way to index path information.<br>><br>> My ideas are as follows:<br>><br>> /usr/jarrod/very/long/path/to/a/file.txt<br>><br>> use prefixes like P000:usr, P001:jarrod, P002:very P003:long . . . you get
<br>> the idea<br><br>There's no need for each term to correspond to a directory level - you<br>could make them a fixed number of characters long, which would reduce<br>the number needed, which should make finding a particular existing entry
<br>more efficient - if you make the length 240 characters then many files<br>will only need a single term. Also, this'll work even if you have a<br>directory name which is 300 characters long...</blockquote><div><br><br>
thanks for the suggestion, I can't afford even the miniscule chance that a hash collision might happen.<br>so what you are suggesting is for terms that are > 240 have a term entry for each 240 character piece and<br>
prefix them with a position? This will probably be a single term per directory in most cases as you suggest.<br></div><br></div><br>