[
https://issues.apache.org/jira/browse/COUCHDB-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564330#comment-13564330
]
Benoit Chesneau commented on COUCHDB-1654:
------------------------------------------
[~janl] That's fine for me. Just wanted to skip another delay..
[~rnewson]wasn't thinking at a shell script for the rlup phase. There is no
reason you can't do that during this phase though. You can 1. do the migration
offline then trigger the update.
About the benchmark can you share the script and data? Will be easier to
compare the same figure and see if we didn't forget obvious things.
> couchdb view sig changed
> ------------------------
>
> Key: COUCHDB-1654
> URL: https://issues.apache.org/jira/browse/COUCHDB-1654
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Reporter: Robert Newson
> Priority: Blocker
> Fix For: 1.3
>
>
> view sigs and location changed between 1.2.x and 1.3.x, which would cause
> full rebuilds.
> to be clear: upgrading to 1.3 should not cause a view to rebuild from scratch.
> ➜ couchdb git:(1.3.x) find tmp
> tmp
> tmp/lib
> tmp/lib/.db1_design
> tmp/lib/.db1_design/0761939631be54bf36d3ed9172bcf689.view
> tmp/lib/.delete
> tmp/lib/_replicator.couch
> tmp/lib/_users.couch
> tmp/lib/db1.couch
> tmp/log
> tmp/log/couch.log
> tmp/run
> tmp/run/couch.uri
> tmp/run/couchdb
> ➜ couchdb git:(1.3.x) find tmp
> tmp
> tmp/lib
> tmp/lib/.db1_design
> tmp/lib/.db1_design/0761939631be54bf36d3ed9172bcf689.view
> tmp/lib/.db1_design/mrview
> tmp/lib/.db1_design/mrview/641ce136c0f1dbe93aa94d3a419a0efe.view
> tmp/lib/.delete
> tmp/lib/_replicator.couch
> tmp/lib/_users.couch
> tmp/lib/db1.couch
> tmp/log
> tmp/log/couch.log
> tmp/run
> tmp/run/couch.uri
> tmp/run/couchdb
--
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
