ondra-novak commented on issue #984: update_seq of a view is set to zero after compaction URL: https://github.com/apache/couchdb/issues/984#issuecomment-343759935 > Also for reference, please see https://issues.apache.org/jira/browse/COUCHDB-2849 which discusses why this is a problematic request and unlikely to be fixed anytime soon. Essentially, each copy of each view shard will have its own update_seq value... The new seqId is several bytes long (still trying to figure why) Is it really to hard to put there list of update_seqs from each node? My suggestion: [3587,3257,2325,3422] Or with a better node addressing ``` {"node-name":update_seq,"node-name":update_seq,"node-name":update_seq,"node-name":update_seq} ``` It is impossible in general, or it is impossible only for current developers?
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
