|Constructor and Description|
|Modifier and Type||Method and Description|
Choose the timestamp for
public static long chooseTimestamp(IIndex ndx, long timestamp)
TPS.TPVtuples to written on the sparse row store.
Note: Revisions written with the same timestamp as a pre-existing column value will overwrite the existing column value rather than causing new revisions with their own distinct timestamp to be written. There is therefore a choice for "auto" vs "auto-unique" for timestamps.
Note: Timestamps generated locally on the server will be consistent
within a row, and all revisions of column values for the same row will
always be in the same index partition and hence on the same server. This
means that we can use locally assigned timestamp as unique timestamps.
However, time could go backwards if there is a failover to another server
for the partition and the other server has a different clock time. This
is resolved by choosing a timestamp assigned by the global
Copyright © 2006–2019 SYSTAP, LLC DBA Blazegraph. All rights reserved.