memory's cheap! (I know processing it is not' though ) Dennis Gearon
Signature Warning ---------------- It is always a good idea to learn from your own mistakes. It is usually a better idea to learn from others’ mistakes, so you do not have to make them yourself. from 'http://blogs.techrepublic.com.com/security/?p=4501&tag=nl.e036' EARTH has a Right To Life, otherwise we all die. ----- Original Message ---- From: Toke Eskildsen <t...@statsbiblioteket.dk> To: "solr-user@lucene.apache.org" <solr-user@lucene.apache.org> Sent: Mon, November 1, 2010 11:45:34 PM Subject: RE: Ensuring stable timestamp ordering Dennis Gearon [gear...@sbcglobal.net] wrote: > how about a timrstamp with either a GUID appended on the end of it? Since long (8 bytes) is the largest atomic type supported by Java, this would have to be represented as a String (or rather BytesRef) and would take up 4 + 32 bytes + 2 * 4 bytes from the internal BytesRef-attributes + some extra overhead. That is quite a large memory penalty to ensure unique timestamps.
