Do you mean SHA1 of the document itself? I'm pretty sure that would be a
problem for us as we can have nested documents with identical values. For
example, you could have:
If "author" is indexed as a nested document it will need an id which can't
just be the SHA1 of the content we provided. Now I suppose if it has the
_parentId as part of the "content" then the SHA1 would be different, but I
don't know when/how the parent id is associated with nested docs. -- Dan
On Tue, Jul 26, 2011 at 6:25 PM, ajsie firstname.lastname@example.org wrote:
CouchDB is using a 40 long characters SHA1 id and they say that the
risk is very minimal.
I wonder if there is a risk that the id Elastic search auto generates
will collide with another one since it's only 22 characters long.