[
https://issues.apache.org/jira/browse/COUCHDB-956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-956:
-----------------------------------
Fix Version/s: 2.0
Yes, it would be a good idea not to sort them. If I recall correctly, the
reason for the sorting is that the reader will rearrange documents through its
use of parallel connections. But really, we can leave them unsorted. Worst
that will happen is that a few documents get checked again on the next
replication.
> 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.
