[
https://issues.apache.org/jira/browse/COUCHDB-956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12933540#action_12933540
]
Randall Leeds commented on COUCHDB-956:
---------------------------------------
I think it's actually important that the high watermark is based on position in
the input sequence or the worst that happens is documents are missed.
Last I looked at it the best solution that came to mind was to actually assign
a local ephemeral sequence *within this replication session* to changes as they
arrived for the purposes of tracking the high watermark during parallel
fetching.
> Return all _seq values as strings not integers
> ----------------------------------------------
>
> Key: COUCHDB-956
> URL: https://issues.apache.org/jira/browse/COUCHDB-956
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Robert Newson
> Fix For: 2.0
>
>
> Some fields are returned as strings in db_info and other places to protect
> against numeric overflow;
> {"db_name":"db","doc_count":0,"doc_del_count":0,"update_seq":0,"purge_seq":0,"compact_running":false,"disk_size":79,"instance_start_time":"1290088043619158","disk_format_version":5,"committed_update_seq":0}
> here, instance_start_time is protected but, more critically, update_seq is
> not.
> If update_seq were to be wrapped due to precision issues, what breaks?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
