|
From: Doug C. <cu...@ap...> - 2008-03-19 19:06:05
|
Ning Li wrote: > On Mon, Mar 17, 2008 at 7:28 PM, Yonik Seeley <yo...@ap...> wrote: >> Or did you mean represent the hash as a String? > > Yes. :) I had a slightly different idea. I thought that the id string would be the external id provided by the application that we return with hits, e.g., a uri, a filename, etc. We'd also have a numeric 'position' value that places the document on the ring. The position would, by default, be the hash of the id, but an application might override that. It would be a bug for an application to ever provide different positions for the same id. I'd imagined that positions would be longs, but Yonik has argued that they might as well be ints, and I can't think why they couldn't, if we're going to keep the string id too. That makes the default implementation in Java much easier, since it can be hashCode(). Doug |