[
https://issues.apache.org/jira/browse/COUCHDB-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668578#comment-13668578
]
Adam Kocoloski commented on COUCHDB-1769:
-----------------------------------------
Thanks! The lack of emits is not necessarily significant; the dupes are
detected one level up, as it were, and we record information about each doc at
that level regardless of the number of emits.
On the other hand the results from _all_docs and _changes are interesting. In
the past I'm fairly certain that we'd *always* observe dupes in at least one of
those indexes.
> Duplicates in View indexes
> --------------------------
>
> Key: COUCHDB-1769
> URL: https://issues.apache.org/jira/browse/COUCHDB-1769
> Project: CouchDB
> Issue Type: Bug
> Components: JavaScript View Server
> Affects Versions: 1.3
> Reporter: Stefan Kögl
> Attachments: duplicate.log
>
>
> The compaction of a view (created with CouchDB 1.3) failed due to
> view_duplicate_id. The database to which the view belongs was created with
> 1.2.x but compacted (with the 0-byte-compact-file trick) with 1.3.
> A full log of the failed compaction can be found at
> https://friendpaste.com/1AL050bzwyLCa9KJUKJw1u
> I experienced the same behaviour already with previous versions but assumed
> it might be gone with 1.3, but this seems not to be the case.
> When such duplicates happen (and appear during compaction), they seem to be
> at the beginning of the view index. The view in question has the following
> _info:
> {noformat}
> {"name":"listeners","view_index":{"signature":"854a8065b438b3e53fcdbbe0a79a8e80","language":"javascript","disk_size":2679632207,"data_size":1026614011,"update_seq":58353111,"purge_seq":0,"updater_running":false,"compact_running":false,"waiting_commit":false,"waiting_clients":0}}
> {noformat}
> Compaction stopped with a 39M large .compact.view file.
> Also the problem seems to happen only one some machines.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
