[GitHub] couchdb pull request: installs npm while building the docker image...
Github user till commented on the pull request: https://github.com/apache/couchdb/pull/318#issuecomment-97705547 @tillkahlbrock â Hey, first of, great choice of first name. ;) Then, I was wondering, is it a good idea to install the latest npm always? It could lead to unexpected breakage in the build script. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
Re: [PROPOSAL] Move transactional email out of dev@
We use this in-house: https://github.com/heroku/devdigest/ Gives you the daily run-down on what happened on a set of given repos or in an org. It's tweak-able (= open source, Ruby code). Till On Tue, Mar 17, 2015 at 4:40 PM, Noah Slater nsla...@apache.org wrote: I am +1 on a monthly reminder. Do we have a volunteer to code that up? Could even be a weekly reminder. I'm imagining it would contain a summary of all open/active PRs, so people might be like ooh, I am interested in that one while the discussion is still happening! On 16 March 2015 at 23:04, Sebastian Rothbucher sebastianrothbuc...@googlemail.com wrote: +1 with Joan and Alexander also, i.e. do a monthly thing instead of blasting out dozens a day to dev@ = this is great, thanks for bringing it up! Sebastian On Mon, Mar 16, 2015 at 6:42 PM, Alexander Shorin kxe...@gmail.com wrote: On Mon, Mar 16, 2015 at 7:46 PM, Joan Touzet woh...@apache.org wrote: I'd be in support of an automated email monthly to dev@ that reminds people where to go to look for GH PRs, JIRA ticket updates, etc. Good idea btw. +1 -- ,,,^..^,,, -- Noah Slater https://twitter.com/nslater
Re: Plugin Registry (Was Summary of IRC meeting in #couchdb-meeting)
On Thursday 14 November 2013 at 20:15, Brian Mitchell wrote: On Thu, Nov 14, 2013 at 1:52 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: On Thursday 14 November 2013 at 18:28, Simon Metson wrote: I’m interested in this too. Can we pick up stuff from npm? Cheers Simon Please don’t. For starters, a more or less static registry would be awesome. Not databased. I'm curious how static really avoids the database problem. Are you saying it'd be better to just pull down a know good URL and that never changes? Should have elaborate on this more. For NPM, I’d like to see them move in a direction where I can mirror it on a static host or CDN vs. something that requires a database server. :-) CouchDB replication is amazing but correct me if I am wrong, but rsync is a great tool to mirror A to B. :-) CouchDB should still be the backend, but an in between step to be able to dump static files from it would be awesome. I totally see the dogfood appeal as well. ;-) Beyond that, I'm not sure we need to use CouchDB just like NPM does but it is pretty nice. Maybe fewer document mutations would help (splitting plugin releases into their own documents could be a good idea for those running local mirrors). Then minor nitpicks like: (…) - don’t allow people to re-upload releases Yes. We could avoid this partly by making releases more like immutable documents. Yup — that also requires a little more brainpower than a github crawler. - make it easy to mirror it Replication is a natural fit here. There might be an argument for allowing automated installation via plain-old-HTTP or filesystem mirrors as well for the cases where people don't want to have to have a separate database running just to setup their own CouchDB nodes with private plugins (chicken-egg like situations emerge). Yeah, see my response above. I can see the approach — my goal would be to enable people to host on Amazon S3 in the end. :-) E.g. local CouchDB on the LAN, dump/export to a bucket on Amazon S3/Cloudfiles/whatever. Then, all of a sudden — highly available infrastructure. ;-) Till
Re: Comments threads on Github
I think requiring the mailing list is counter intuitive. I know what the rules and regulations are, but it's often an advantage when comments and discussion happen where the related code is. Everything else (e.g. copy/pasting URL references in an additional email to satisfy maybe slightly out-dated rules and regulations) is too much work. ;-) Maybe I can try to help bridging comments to this mailing list if wanted. Till On Friday, March 15, 2013 at 1:24 PM, Noah Slater wrote: It's a minor point, and probably not worth me sending another email, but I guess the framing in my original email was wrong. It's not that we shouldn't be having discussions on PRs, or that activity shouldn't be happening on Github. That's not the problem, and I retract the parts where I imply that it is. :) The problem is that activity should be visible on the dev list. That's what we need to solve. My statements jumped the gun a little bit about what sort of solution was required. ;) Heh. On 15 March 2013 12:16, Noah Slater nsla...@apache.org (mailto:nsla...@apache.org) wrote: Hey folks, I'd like to bring two things to your attention: https://github.com/apache/couchdb/pull/43 https://github.com/cloudant-labs/couchdb/pull/18 These just happen to be two pull requests I looked at today, there are more. On the one hand, this is great. Obviously. Any sort of constructive activity happening around CouchDB is great. But on the other hand, this discussion is core development discussion, and should be happening on the dev list where everybody can see it. (This is foundational stuff for an Apache project. Community building should be focused around the mailing lists. I get that Github is useful for people, but we're not a Github project, so our activity should not be happening there.) I don't know what to suggest. Obviously, I think pull requests are great. And I think the forking model of Github is great, because it allows people to contribute more easily, and in a manner that suits them. But on the other hand, we shouldn't be having important development discussions in pull requests. The PR isn't even against the Apache CouchDB mirror. It's against a Cloudant fork! (So even less likely that folks are going to see it.) Perhaps one of the policies we could document is that discussion of pull requests must be brought to the list. That is, if a PR comes in to the Apache Github mirror, then we make a polite comment on the PR that points them to the mailing list thread and asks them to participate in that forum, so the maximum amount of devs can see and contribute. We could also say that if you have a fork of CouchDB, and you're planning to contribute the work back to Apache CouchDB (as is the case with the Cloudant fork) that you do the same with any PRs that are made to your repos. A sample template comment could be as follows: == Thank you for the pull request! This is a mirror of the Apache CouchDB project, so many of the committers do not monitor it for comments. Instead of discussing this pull request here, I have started a thread on the [developer mailing list] and I invite you to participate! [LINK TO MAILING LIST THREAD] == Additionally, the mailing list thread, or the first reply to it, should CC the original author. One alternative to this (which is a bit of a mess, I know) is to write an integration that copies Github comments to the mailing list thread, and mailing list posts to the PR. Not sure that would work with forks of the main mirror, however. Thoughts? Flames? Thanks, -- NS -- NS
Re: RHEL6 couchdb1.2 startup failed
If it's not the host it might be that what you think is CouchDB running, is really heart trying to (re)start it. The start script just calls another wrapper which in itself just tries to start CouchDB and reports that. It doesn't actually report if the launch procedure completes. I'd enable stderr and stdout logging – on Ubuntu, that is in /etc/default/couchdb – not sure where that is on Redhat. But these files usually give you a good idea on where it's stuck. I'm guessing a source install usually puts it in /usr/local/etc/default/couchdb. Till On Friday, June 22, 2012 at 11:10 AM, Daniel L wrote: By default it binds to 127.0.0.1, can you go into terminal on that server and try curl http://127.0.0.1:5984 Thanks. Daniel On 22/06/2012, at 8:49 AM, xp...@ucalgary.ca (mailto:xp...@ucalgary.ca) wrote: Hi, I built couchdb1.2 from source on RHEL6 because the available couchDB version from RHEL6 is old (1.0.xx). I installed all the latest version of pre-requisites: erlang, curl, spidermonkey, icu ./configure, make and make install -- all passed service start couched -- NO error message, it shows Starting database server couched ps -ef shows couched is running, but it never binds to 5984. service stop couched never stops couchdb either. Banged my head against the wall whole day today. Help please. Peter -- View this message in context: http://couchdb-development.1959287.n2.nabble.com/RHEL6-couchdb1-2-startup-failed-tp7580473.html Sent from the CouchDB Development mailing list archive at Nabble.com (http://Nabble.com).
Re: CouchDB packaging for Ubuntu
On Tuesday, June 12, 2012 at 1:55 AM, Randall Leeds wrote: On Mon, Jun 11, 2012 at 3:24 AM, Benoit Chesneau bchesn...@gmail.com (mailto:bchesn...@gmail.com) wrote: On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Hey, I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu distributions. It's a WIP but I was wondering the following: 1) It builds – but does it work? Is the best bet to run the test suite in futon, or is there something I could run on the command line when the package is installed? I'd prefer the command line to include it in some sort of continuous testing without a browser. 2) Who'd have some interest in testing this? Me! Knock yourself out: https://launchpad.net/~till-php/+archive/couchdb/+packages 3) Which distributions are wanted – I started with karmic and lucid and had planned to build all the way up to 12.10. Any active LTS makes sense, as well as the last release or two. So I think that's lucid, oneiric and precise? That's what I'd do. So far, I've build from karmic to precise. Till
Re: CouchDB packaging for Ubuntu
On Monday, June 11, 2012 at 6:57 PM, CGS wrote: Let us know if any test fail and give us the log of the tests. The tests themselves are pretty self explanatory. If not, at least some tests are using the CouchDB log. So, I think there will be enough info for debugging. CGS Ok, so I started a clean VM with lucid and apt-get install apache-couchdb. Then a couple tests produce erlang_crash.dump files and others fail with Dubious, test returned 1 (wstat 256, 0x100). Can't figure out what that means though? Googled it a bit but none of the errors seem to relate this. Till
Re: CouchDB packaging for Ubuntu
On Tuesday, June 12, 2012 at 2:09 PM, CGS wrote: Dubious, test returned 1 (wstat 256, 0x100) says that the permissions are not in place (therefore, files cannot be created/access, processes are not started/accessible and so on). Could you tell me where exactly you got that error? CGS E.g. icu_driver.t test – and a couple others. I am re-running it with sudo now. But that strikes me as odd. Till
Re: CouchDB packaging for Ubuntu
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote: Well, the default installation requires root permissions as many paths are accessible only as root (you did 'sudo make install', didn't you?). Also, you do sudo apt-get install, so, the tests will be run under root permissions. That's why I said in the README file that these tests should be run as root (a.k.a. sudo command). CGS Sorry, over read that before, but the failures are still happening with sudo: https://gist.github.com/2917336
Re: CouchDB packaging for Ubuntu
Yes, pretty much: https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg I haven't checked in detail, but – do those lib/etc paths get prefixed with COUCHDB_TEST_PATH? Till -- till Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote: Have you modified the parameters from test.cfg to point to your CouchDB installation? CGS On Tue, Jun 12, 2012 at 2:57 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote: Well, the default installation requires root permissions as many paths are accessible only as root (you did 'sudo make install', didn't you?). Also, you do sudo apt-get install, so, the tests will be run under root permissions. That's why I said in the README file that these tests should be run as root (a.k.a. sudo command). CGS Sorry, over read that before, but the failures are still happening with sudo: https://gist.github.com/2917336
Re: CouchDB packaging for Ubuntu
On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote: COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from configure options. The rest gets this variable in front (e.g., if PREFIX was set to / at the configuration stage, then COUCHDB_TEST_PATH should be set to ). E.g., few things from my installation, I have: - default.ini and local.ini in /usr/local/etc/coucdb/ and that requires: COUCHDB_TEST_PATH /usr/local COUCHDB_TEST_ETC_PATH etc/couchdb Ok, so basically I am trying to integrate as much as possible with Ubuntu – so I set my prefix to /usr (see github link). COUCHDB_TEST_PATH /usr - CouchDB .beam files path in /usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires: COUCHDB_TEST_PATH /usr/local COUCHDB_TEST_LIB_PATH lib/couchdb COUCHDB_TEST_EXTRA erlang/lib COUCHDB_TEST_VERSION -1.2.0 COUCHDB_TEST_EBIN ebin This is the path when I install my package: /usr/lib/couchdb/erlang/lib/couch-1.2.0/ The problem may be in COUCHDB_TEST_ETAP_PATH ./tests (preferable full path and not relative because the tests don't know too much about relative paths). Can you try to set it as a full path and execute the tests again? You don't need to clean anything from the previous executions. I just did that – tests fail the same way. I can't really tell what the cause is since the erl_crash.dump is kinda hard to read. Signal vs. noise. :) Till CGS On Tue, Jun 12, 2012 at 4:06 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Yes, pretty much: https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg I haven't checked in detail, but – do those lib/etc paths get prefixed with COUCHDB_TEST_PATH? Till -- till Sent with Sparrow (http://www.sparrowmailapp.com/?sig) On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote: Have you modified the parameters from test.cfg to point to your CouchDB installation? CGS On Tue, Jun 12, 2012 at 2:57 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) (mailto: klimp...@gmail.com (mailto:klimp...@gmail.com)) wrote: On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote: Well, the default installation requires root permissions as many paths are accessible only as root (you did 'sudo make install', didn't you?). Also, you do sudo apt-get install, so, the tests will be run under root permissions. That's why I said in the README file that these tests should be run as root (a.k.a. sudo command). CGS Sorry, over read that before, but the failures are still happening with sudo: https://gist.github.com/2917336
Re: CouchDB packaging for Ubuntu
3 test_util:config_files().
[/usr/etc/couchdb/default.ini,
/home/vagrant/buildbox/testsuite/tests/random_port.ini,
/usr/etc/couchdb/local.ini]
This is the problem – the prefix is not used for sysconfdir. The dir is in /etc
not in PREFIX/etc.
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
Can you do a test for me? Please, open an Erlang shell (erl) in tests/
directory (hopefully you will still have the test_util.beam file) and
copy-paste these lines (exit with CTRL+g and qEnter):
l(test_util).
test_util:init_code_path().
test_util:config_files().
l(couch_config).
couch_config:start_link(test_util:config_files()).
l(couch_drv).
couch_drv:start_link().
Your result should look like this:
1 l(test_util).
{module,test_util}
2 test_util:init_code_path().
ok
3 test_util:config_files().
[/usr/etc/couchdb/default.ini,
path_to_tests_dir/random_port.ini,
/usr/etc/couchdb/local.ini]
4 l(couch_config).
{module,couch_config}
5 couch_config:start_link(test_util:config_files()).
{ok,0.38.0}
6 l(couch_drv).
{module,couch_drv}
7 couch_drv:start_link().
{ok,0.41.0}
where path_to_local_dir should be the same set COUCHDB_TEST_ETAP_PATH and
the same with the result of pwd (considering you are still in tests
directory). Let me know the output, please.
CGS
On Tue, Jun 12, 2012 at 5:21 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) wrote:
On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
configure options. The rest gets this variable in front (e.g., if PREFIX
was set to / at the configuration stage, then COUCHDB_TEST_PATH should
be
set to ). E.g., few things from my installation, I have:
- default.ini and local.ini in /usr/local/etc/coucdb/ and that requires:
COUCHDB_TEST_PATH /usr/local
COUCHDB_TEST_ETC_PATH etc/couchdb
Ok, so basically I am trying to integrate as much as possible with Ubuntu
– so I set my prefix to /usr (see github link).
COUCHDB_TEST_PATH /usr
- CouchDB .beam files path in
/usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
COUCHDB_TEST_PATH /usr/local
COUCHDB_TEST_LIB_PATH lib/couchdb
COUCHDB_TEST_EXTRA erlang/lib
COUCHDB_TEST_VERSION -1.2.0
COUCHDB_TEST_EBIN ebin
This is the path when I install my package:
/usr/lib/couchdb/erlang/lib/couch-1.2.0/
The problem may be in COUCHDB_TEST_ETAP_PATH ./tests (preferable full
path and not relative because the tests don't know too much about
relative
paths). Can you try to set it as a full path and execute the tests again?
You don't need to clean anything from the previous executions.
I just did that – tests fail the same way.
I can't really tell what the cause is since the erl_crash.dump is kinda
hard to read. Signal vs. noise. :)
Till
CGS
On Tue, Jun 12, 2012 at 4:06 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)) wrote:
Yes, pretty much:
https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
I haven't checked in detail, but – do those lib/etc paths get prefixed
with COUCHDB_TEST_PATH?
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
Have you modified the parameters from test.cfg to point to your
CouchDB
installation?
CGS
On Tue, Jun 12, 2012 at 2:57 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)) wrote:
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
Well, the default installation requires root permissions as many
paths
are
accessible only as root (you did 'sudo make install', didn't
you?).
Also,
you do sudo apt-get install, so, the tests will be run under root
permissions. That's why I said in the README file that these
tests
should
be run as root (a.k.a. sudo command).
CGS
Sorry, over read that before, but the failures are still happening
with
sudo:
https://gist.github.com/2917336
Re: CouchDB packaging for Ubuntu
Attachment didn't make it through – can you a patch/file?
On Tuesday, June 12, 2012 at 6:22 PM, CGS wrote:
OK. I understand.
For the moment, replace test_util.erl from utils with the file attached here.
This should remove COUCHDB_TEST_PATH from the path. I will rewrite
test_util.erl to get the paths independently for your repo.
CGS
On Tue, Jun 12, 2012 at 6:06 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) wrote:
3 test_util:config_files().
[/usr/etc/couchdb/default.ini,
/home/vagrant/buildbox/testsuite/tests/random_port.ini,
/usr/etc/couchdb/local.ini]
This is the problem – the prefix is not used for sysconfdir. The dir is in
/etc not in PREFIX/etc.
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 5:52 PM, CGS wrote:
Can you do a test for me? Please, open an Erlang shell (erl) in tests/
directory (hopefully you will still have the test_util.beam file) and
copy-paste these lines (exit with CTRL+g and qEnter):
l(test_util).
test_util:init_code_path().
test_util:config_files().
l(couch_config).
couch_config:start_link(test_util:config_files()).
l(couch_drv).
couch_drv:start_link().
Your result should look like this:
1 l(test_util).
{module,test_util}
2 test_util:init_code_path().
ok
3 test_util:config_files().
[/usr/etc/couchdb/default.ini,
path_to_tests_dir/random_port.ini,
/usr/etc/couchdb/local.ini]
4 l(couch_config).
{module,couch_config}
5 couch_config:start_link(test_util:config_files()).
{ok,0.38.0}
6 l(couch_drv).
{module,couch_drv}
7 couch_drv:start_link().
{ok,0.41.0}
where path_to_local_dir should be the same set COUCHDB_TEST_ETAP_PATH
and
the same with the result of pwd (considering you are still in tests
directory). Let me know the output, please.
CGS
On Tue, Jun 12, 2012 at 5:21 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) (mailto:klimp...@gmail.com) wrote:
On Tuesday, June 12, 2012 at 4:30 PM, CGS wrote:
COUCHDB_TEST_PATH should be the same as PREFIX and/or EPREFIX from
configure options. The rest gets this variable in front (e.g., if
PREFIX
was set to / at the configuration stage, then COUCHDB_TEST_PATH
should
be
set to ). E.g., few things from my installation, I have:
- default.ini and local.ini in /usr/local/etc/coucdb/ and that
requires:
COUCHDB_TEST_PATH /usr/local
COUCHDB_TEST_ETC_PATH etc/couchdb
Ok, so basically I am trying to integrate as much as possible with
Ubuntu
– so I set my prefix to /usr (see github link).
COUCHDB_TEST_PATH /usr
- CouchDB .beam files path in
/usr/local/lib/couchdb/erlang/lib/couch-1.2.0/ebin and that requires:
COUCHDB_TEST_PATH /usr/local
COUCHDB_TEST_LIB_PATH lib/couchdb
COUCHDB_TEST_EXTRA erlang/lib
COUCHDB_TEST_VERSION -1.2.0
COUCHDB_TEST_EBIN ebin
This is the path when I install my package:
/usr/lib/couchdb/erlang/lib/couch-1.2.0/
The problem may be in COUCHDB_TEST_ETAP_PATH ./tests (preferable
full
path and not relative because the tests don't know too much about
relative
paths). Can you try to set it as a full path and execute the tests
again?
You don't need to clean anything from the previous executions.
I just did that – tests fail the same way.
I can't really tell what the cause is since the erl_crash.dump is kinda
hard to read. Signal vs. noise. :)
Till
CGS
On Tue, Jun 12, 2012 at 4:06 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) (mailto:klimp...@gmail.com) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)
(mailto:klimp...@gmail.com)) wrote:
Yes, pretty much:
https://github.com/till/couchdb-deb/blob/master/testsuite/test.cfg
I haven't checked in detail, but – do those lib/etc paths get
prefixed
with COUCHDB_TEST_PATH?
Till
--
till
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
On Tuesday, June 12, 2012 at 3:07 PM, CGS wrote:
Have you modified the parameters from test.cfg to point to your
CouchDB
installation?
CGS
On Tue, Jun 12, 2012 at 2:57 PM, till klimp...@gmail.com
(mailto:klimp...@gmail.com) (mailto:klimp...@gmail.com) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)
(mailto:klimp...@gmail.com)) (mailto:
klimp...@gmail.com (mailto:klimp...@gmail.com)
(mailto:klimp...@gmail.com)) wrote:
On Tuesday, June 12, 2012 at 2:36 PM, CGS wrote:
Well, the default installation
Re: CouchDB packaging for Ubuntu
I agree – I also don't have to maintain this alone. Once this is working as expected, I wanted to push the build stuff into a repo where more people have access to and we could also created a 'team' on launchpad to have more people contribute to this (or at least be able to). Till On Monday, June 11, 2012 at 3:06 PM, Jan Lehnardt wrote: A patch and/or a repo somewhere would be nice :) On Jun 11, 2012, at 09:08 , CGS wrote: Hi, I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive). CGS On Sun, Jun 10, 2012 at 8:46 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Hey, [ CC'd user@ to get more feedback. ] I made some progress. I have builds for the following more or less ready: * karmic * lucid * maverick * oneiric * natty * precise It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer. https://launchpad.net/~till-php/+archive/couchdb Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it. (Also, @Jan:) I'm trying to figure out how to setup more automated testing. make check always requires the source tree to be present, I'd like make check against my installed binaries. I saw the verify installation in Futon – something like that for the command line so I can iterate on these builds and trigger a test this in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm. Till On Saturday, June 9, 2012 at 11:13 PM, CGS wrote: Hi, I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running. Unfortunately, I've never built a deb package, so, I cannot provide such a package. Nevertheless, if you have any problem in building it, just let me know and I will try to help. About the mailing list, I suppose adding the CouchDB users (to get an idea which is the desired Ubuntu distro) and/or Debian (you may get support in testing and debugging) lists wouldn't be such a bad idea, but it's your call here. CGS On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Hey, I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu distributions. It's a WIP but I was wondering the following: 1) It builds – but does it work? Is the best bet to run the test suite in futon, or is there something I could run on the command line when the package is installed? I'd prefer the command line to include it in some sort of continuous testing without a browser. 2) Who'd have some interest in testing this? 3) Which distributions are wanted – I started with karmic and lucid and had planned to build all the way up to 12.10. 4) Is there a mailing list to discuss this, or is dev@ fine? Till couchdb_etap.tgz
Re: CouchDB packaging for Ubuntu
Ok, my working repo is here: https://github.com/till/couchdb-deb So does anyone have any idea how to debug failed test cases? They never failed for me before. :D Till On Monday, June 11, 2012 at 4:37 PM, CGS wrote: Not at all. After all, I do not do this for my personal interest, but for this community. I am glad if I can help. Cheers, CGS On Mon, Jun 11, 2012 at 3:58 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Hey, thanks, I'm gonna test this shortly. Do you mind if I push it one of my repo? Till On Monday, June 11, 2012 at 9:08 AM, CGS wrote: Hi, I isolated the tests which are started with make check and make them run over the default installation under Ubuntu 12.10. Please, let me know if it is what you need (there is a README file in the archive). CGS On Sun, Jun 10, 2012 at 8:46 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) (mailto: klimp...@gmail.com (mailto:klimp...@gmail.com)) wrote: Hey, [ CC'd user@ to get more feedback. ] I made some progress. I have builds for the following more or less ready: * karmic * lucid * maverick * oneiric * natty * precise It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer. https://launchpad.net/~till-php/+archive/couchdbhttps://launchpad.net/%7Etill-php/+archive/couchdb Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it. (Also, @Jan:) I'm trying to figure out how to setup more automated testing. make check always requires the source tree to be present, I'd like make check against my installed binaries. I saw the verify installation in Futon – something like that for the command line so I can iterate on these builds and trigger a test this in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm. Till On Saturday, June 9, 2012 at 11:13 PM, CGS wrote: Hi, I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running. Unfortunately, I've never built a deb package, so, I cannot provide such a package. Nevertheless, if you have any problem in building it, just let me know and I will try to help. About the mailing list, I suppose adding the CouchDB users (to get an idea which is the desired Ubuntu distro) and/or Debian (you may get support in testing and debugging) lists wouldn't be such a bad idea, but it's your call here. CGS On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) (mailto: klimp...@gmail.com) (mailto:klimp...@gmail.com) wrote: Hey, I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu distributions. It's a WIP but I was wondering the following: 1) It builds – but does it work? Is the best bet to run the test suite in futon, or is there something I could run on the command line when the package is installed? I'd prefer the command line to include it in some sort of continuous testing without a browser. 2) Who'd have some interest in testing this? 3) Which distributions are wanted – I started with karmic and lucid and had planned to build all the way up to 12.10. 4) Is there a mailing list to discuss this, or is dev@ fine? Till Attachments: - couchdb_etap.tgz
Re: CouchDB packaging for Ubuntu
I submitted a bunch of new builds to the launchpad farm. I tested Lucid (Ubuntu 10.04 LTS) so far (hit verify installation in futon). If anyone wants to give one of these builds a go and give me feedback – feel free to. ;-) Till
Re: CouchDB packaging for Ubuntu
Hey, [ CC'd user@ to get more feedback. ] I made some progress. I have builds for the following more or less ready: * karmic * lucid * maverick * oneiric * natty * precise It's building and I am trying to refine the process a bit. So it might break in between [aka WIP]. I'm just adding this as a disclaimer. https://launchpad.net/~till-php/+archive/couchdb Would you mind testing my builds? :) So far, I only tested lucid briefly (and ran into the xulrunner issue, which I think I have auto-fixed now). Besides I just started it up, created a DB and entered some docs into it. (Also, @Jan:) I'm trying to figure out how to setup more automated testing. make check always requires the source tree to be present, I'd like make check against my installed binaries. I saw the verify installation in Futon – something like that for the command line so I can iterate on these builds and trigger a test this in a continuous integration setup. Building is part of it, but since building a binary and installing it are two separate steps I want to ensure that the second step also works. I am still trying to wrap my head around a setup where I can maybe knife up a few instances in THE CLOUD, install my package, run its test-suite and confirm. Till On Saturday, June 9, 2012 at 11:13 PM, CGS wrote: Hi, I have CouchDB 1.2.0 with Erlang R15B01 on Ubuntu 12.10 up and running. Unfortunately, I've never built a deb package, so, I cannot provide such a package. Nevertheless, if you have any problem in building it, just let me know and I will try to help. About the mailing list, I suppose adding the CouchDB users (to get an idea which is the desired Ubuntu distro) and/or Debian (you may get support in testing and debugging) lists wouldn't be such a bad idea, but it's your call here. CGS On Sat, Jun 9, 2012 at 9:15 PM, till klimp...@gmail.com (mailto:klimp...@gmail.com) wrote: Hey, I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu distributions. It's a WIP but I was wondering the following: 1) It builds – but does it work? Is the best bet to run the test suite in futon, or is there something I could run on the command line when the package is installed? I'd prefer the command line to include it in some sort of continuous testing without a browser. 2) Who'd have some interest in testing this? 3) Which distributions are wanted – I started with karmic and lucid and had planned to build all the way up to 12.10. 4) Is there a mailing list to discuss this, or is dev@ fine? Till
CouchDB packaging for Ubuntu
Hey, I've been scratching my own itch and started building 1.2.0 for a couple Ubuntu distributions. It's a WIP but I was wondering the following: 1) It builds – but does it work? Is the best bet to run the test suite in futon, or is there something I could run on the command line when the package is installed? I'd prefer the command line to include it in some sort of continuous testing without a browser. 2) Who'd have some interest in testing this? 3) Which distributions are wanted – I started with karmic and lucid and had planned to build all the way up to 12.10. 4) Is there a mailing list to discuss this, or is dev@ fine? Till
Wiki markup (Re: Couchbase trademark issues)
Splitting off the thread – :D Can we use this wiki markup asap? What keeps us from getting this setup ASAP (vs. waiting for the website)? Till On Fri, Feb 24, 2012 at 4:26 PM, Noah Slater nsla...@tumbolia.org wrote: That's an interesting approach Christian, thanks! I'll revisit this method once we get around to doing the new site. On Fri, Feb 24, 2012 at 2:55 AM, Bob Dionne dio...@dionne-associates.com wrote: I like this look, crisper and easier to read. Nice work On Feb 23, 2012, at 9:20 PM, Christian Swinehart wrote: On Mon, Feb 20, 2012 at 7:12 AM, Robert Newson rnew...@apache.org wrote: coinciding with the 1.2 release would be awesome On 20 February 2012 12:09, Robert Newson rnew...@apache.org wrote: 1 for a revamped couchdb.apache.org. The most recent change, I think, was mine, which simply dropped the misleading diagram in the top-right. Long past time for an overhaul. Who has the time and skill to make this happen? as one potential drop in that bucket, i spent some time fiddling with the wiki's css to bring it more in line with the project's color scheme. i also took the liberty of tweaking the typography a bit. here's a demo (based on what i was able to wget of the site): http://samizdat.cc/couchdb/ all the modifications can be found in: http://samizdat.cc/moin_static188/modernized/css/screen.css except for the header image which lives at: http://samizdat.cc/moin_static188/modernized/img/couchdb-wiki-logo-small.png -christian
Re: backport of couchdb
I remember Randall had a launchpad repo to build CouchDB. (CC'd him, maybe he can weigh in how far he got) Launchpad is probably not a 100% compatible with Debian (since it targets Ubuntu distributions) but the 'basic formula' could be contributed to something like dotdeb? Anyone have thoughts? Till On Fri, Feb 3, 2012 at 11:42 AM, Jens Rantil jens.ran...@telavox.se wrote: Hi again everyone, I am happy to get a discussion going about this. I'd say Debian is a major platform for servers. Therefor, I believe CouchDB should exist there - with a reasonable modern version. Sure, you can install from source. However, with CouchDB and it's replication features it should be easy to roll it out to a multitude of Debian servers and kick off replication. Also, previously Couchbase was hosting a (sadly, buggy) Debian package. After the death of the Couchbase package[1] there is no modern Debian package alternative anymore. To keep this discussion going - what did you think of Jan's proposal to set up a Debian maintainer mailing list? As of the initial question, shall Debian stable installations be living with 0.11 for another ~6 months? I guess so. /J -Ursprungligt meddelande- Från: Jan Lehnardt [mailto:j...@apache.org] Skickat: den 31 januari 2012 21:42 Till: dev@couchdb.apache.org Kopia: Laszlo Boszormenyi Ämne: Re: backport of couchdb Hi Laszlo, On Jan 31, 2012, at 21:24 , Laszlo Boszormenyi wrote: Hi, First, I'm an official DD and the maintainer of CouchDB. Pleased to meet you and thanks for weighing in on this discussion :) As for the back porting, Debian doesn't directly manage any packages. Everything has a package maintainer who may or may not be part of the Debian staff, so it really does land on the maintainer. And I don't see how you could back port fixes from, say, 1.x.x to 0.x.x. Let me ask an other way. Is CouchDB expected to change a lot internally? I think it is. The question, I think, is how much end-users will be affected by these changes (upgrade trouble, incompatibilities etc.) We are doing our best to not break BC (according to semver.org) and make upgrades seamless and well documented. What about helping downstream with security fixes? We could start a new mailing list package-maintain...@couchdb.apache.org where downstream folks can subscribe and get notified about impeding releases as well as security notices. Would that be a good first step? What else could we do to help you downstream? When CouchDB 1.2.0 is expected to be released? We are expecting to call a vote in the next few days (pending release manager time). As per our process, it'll take 4-5 days after the initial call for voting to get the release out (if the votes don't go through and if issues are found, this process is reset). Let us know if you have any other questions and thanks again for helping out! Cheers Jan --
Re: RFC: Releasing 1.2.0
Can haz release? :) On Fri, Jan 6, 2012 at 11:34 PM, Randall Leeds randall.le...@gmail.comwrote: On Fri, Jan 6, 2012 at 13:22, Robert Newson rnew...@apache.org wrote: I'm checking it now. Jan did his JIRA dance, so I think we're clean on that end. I'm looking into whether all the fixes got backported, etc, and I'll also read over the full 1.1.x-1.2.x diff. Just checked over my commits and everything appropriate is back-ported. Good to go from my end. +1 on calling the vote. B. On 6 January 2012 21:19, Noah Slater nsla...@tumbolia.org wrote: Hey chaps, Let's pull our finger out and get 1.2.0 shipped. Do we have everything in trunk that we want in 1.2.0, or are there any patches y'all are sitting on? Also, can you all check NEWS and CHANGES to make sure they are up to date? Thanks all, N
Re: RFC: Releasing 1.2.0
Just looked at CHANGES, a few questions: 1) Can anyone go into detail on the replicator? (E.g. where are the configuration options.) 2) Can anyone mention how snappy/zlib impacts performance? Most of the stuff is a little vague for my taste – maybe the Jira issues explain the additions better. If so, should they be linked always? Till On Mon, Jan 9, 2012 at 10:34 PM, till t...@php.net wrote: Can haz release? :) On Fri, Jan 6, 2012 at 11:34 PM, Randall Leeds randall.le...@gmail.comwrote: On Fri, Jan 6, 2012 at 13:22, Robert Newson rnew...@apache.org wrote: I'm checking it now. Jan did his JIRA dance, so I think we're clean on that end. I'm looking into whether all the fixes got backported, etc, and I'll also read over the full 1.1.x-1.2.x diff. Just checked over my commits and everything appropriate is back-ported. Good to go from my end. +1 on calling the vote. B. On 6 January 2012 21:19, Noah Slater nsla...@tumbolia.org wrote: Hey chaps, Let's pull our finger out and get 1.2.0 shipped. Do we have everything in trunk that we want in 1.2.0, or are there any patches y'all are sitting on? Also, can you all check NEWS and CHANGES to make sure they are up to date? Thanks all, N
Re: couchDB with databases per user: continuous replications stop working, without errors
On Thu, Jan 5, 2012 at 10:18 AM, Gregor Martynus gre...@martynus.netwrote: I experience massive reliability issues with continuous replications in my app. Each user has an own profile db with a continuous replication to a central database. Numbers: ~1800 dbs ~2600 continuous replications (using _replicator db), ~200 did not get started. My hope is that others faced these issues before and found ways to fix or work around them. So if you are a developer or know developers that have a similar couchDB setup, would you mind to get me in touch? Thanks for your help! Tech info: couchDB 1.1.1 (iriscouch) max_dbs_open is set to 5000 no errors show up in _log _replicate does not accept POST requests anymore new replications from _replicator docs do not get picked up Is your loglevel at debug? It should def. report something – maybe do a simple cURL request and paste that along with a log entry somewhere ( friendpaste.com). You might also want to try stock Apache CouchDB – not sure how IrishCouch's version differs. Till
Re: Binary Downloads
On Thu, Nov 3, 2011 at 12:35 PM, Jan Lehnardt j...@apache.org wrote: Hi all, I think we should start considering providing binary downloads for our users. The whole topic is a bit of a mess (see below), so I'd propose to start small. 1. This first iteration are links from couchdb.apache.org that are clearly marked as unofficial 3rd party binary downloads that are not hosted on ASF infrastructure. 2. Start with popular platforms. 3. Use the build-couchdb* script to create a fully self-contained directory with CouchDB and all its dependencies in one place that can be rm -rf'd for uninstalling. * https://github.com/iriscouch/build-couchdb The above circumvents several things that I hope we can resolve later, but that I don't consider blocking us from getting the above started. A. Official ASF releases. Of course, ideally, we should provide official ASF binary releases, but I acknowledge that with a small community, we may have trouble getting votes and testing for all popular platforms together. The nice thing of the proposal above though is, that we can, at any time promote an unofficial build to an official one by voting on it and changing it's label on the downloads page. B. There's many target platforms our users work with and we can't possibly try to service them all at once. We can grow this operation as we get volunteers to help out with each platform. The nice thing here is that we can help a significant portion of users with relatively little effort. C. Using existing package managers. There are many advantages to use official package managers for system installation and they should in fact be the preferred way to set up a system, but they tend to be a little bit behind with current releases. I'd be super happy to also work with existing package managers to improve the situation there, but I consider this to be outside of the scope of this discussion. What do you think? Cheers Jan -- Yes and no. I'm not a fan of rogue binary installs which don't leverage anything distributions have to offer. It's never all self-contained, e.g. you want to register the service for a startup procedure and off you go into specifics of a system and outside a single directory. If anything it should be specific to the target: on Ubuntu/Debian there should be a launchpad project which contains updated releases of CouchDB for let's say the current Ubuntu/Debian releases. On Redhat/CentOS/Fedora a yum-mirror would be appropriate, etc. pp.. I'm sure each platform has a project to piggyback. Generally though, I'm not sure what the objective is. E.g. is it to please people on hackernews (SCNR)? :-D But for realz: is it to ensure more up-to-date CouchDB (binary) releases on different platforms? Because that might be something to work on. As far as binary is concerned, most platforms have something already (Ubuntu, Debian, *BSD, ...). And some just don't do binary at all (I think Archlinux and Gentoo would be examples). And then I am not sure if providing a binary to their users makes sense. Also to consider: team up with current package maintainers in order to have more frequent releases etc.. Or at least give that a try, before the CouchDB project goes off to do their own thing. Till
Re: Binary Downloads
On Thu, Nov 3, 2011 at 11:26 PM, Jan Lehnardt j...@apache.org wrote: Randall, Till, I had hoped I addressed this in my original mail, but let me try again :) I'm in favour of all the things your are saying, but I'm trying to address this scenario: $ wget $url $ tar xzf $archive $ ./$dir/couchdb Time to relax. All the other things we should also do, and please don't let me hold you back from doing them :) A lot of areas need improvement, and I'm attacking a small one without trying to boil the ocean. If you think the above is a bad idea, please let me know, we shouldn't do it. But if you think it is okay, then lets do it. And then get to the next thing. I don't think it's a bad idea per se. I just think this should be tackled with a different approach. If Randall is up for it that's awesome, Benoit apparently knows about these things as well and if required I can have a look as well. We maintain some launchpad things for 'work' as well. Truth to be told, if these things are already available they just need to be documented on the download page. Nothing else is required and adding that to the page (vs. setting up and testing a new binary installer) should be straight forward. More people can be added to these things to make it scale. ;-) So in generall I think there is not a huge demand for a custom binary thing. I'm not saying you shouldn't do it, but I'd only offer it for targets where it's necessary and point to other options where available. I don't know where a binary is required or currently not available. Do you know which platforms really lack binary support? Till
[jira] [Commented] (COUCHDB-1213) proxy with external api doesn't work
[
https://issues.apache.org/jira/browse/COUCHDB-1213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060098#comment-13060098
]
Till Klampaeckel commented on COUCHDB-1213:
---
I +1 this +1
proxy with external api doesn't work
Key: COUCHDB-1213
URL: https://issues.apache.org/jira/browse/COUCHDB-1213
Project: CouchDB
Issue Type: Bug
Affects Versions: 1.1
Reporter: Till Klampaeckel
Labels: patch, proxy
As discussed on IRC, I'm trying to use an external web API, but every request
to the handler produces an infinite loop.
This is most likely due to not passing on the correct Host header.
Here's an example:
_google = {couch_httpd_proxy, handle_proxy_req,
http://www.google.com/ig;}
Then request with:
curl -L -X GET
http://127.0.0.1:5984/_google/calculator?hl=enq=100EUR%3D%3FAUD
Paul Davis did a quick patch: http://friendpaste.com/62T88HOYw8QyaoIJoXEGXr
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [Couchdb Wiki] Update of CouchDB_in_the_wild by JohnDorion
On Mon, Jul 4, 2011 at 5:09 PM, Noah Slater nsla...@echolibre.com wrote: On 4 Jul 2011, at 15:46, Robert Newson wrote: (but, hey, wikis are new, bound to be bugs). LOL HAHA... Nice. I can't find find the other wiki thread. What's the idea documentation wise, is there anyone working on something else, or so. I'd like to either do something, or at least support an ongoing effort. Till
Re: [Couchdb Wiki] Update of CouchDB_in_the_wild by JohnDorion
Would that documentation be in 'any' VCS, or specifically in http://svn.apache.org/viewvc/couchdb/? Also, what format would it be in? Any thoughts yet? On Mon, Jul 4, 2011 at 5:40 PM, Robert Newson robert.new...@gmail.com wrote: till, The idea is essentially that we move docs into the source tree, which immediately protects them from spam at the cost of preventing edits from the public. These docs would include full API documentation as well as a tutorial or howto guide. It's long past time we had this kind of documentation under source control and not mixed in with the highly variable wiki. The presence of good documentation in the wiki gives the whole wiki an unwarranted stamp of approval. I would like to be able to point at definitive documentation at couchdb.apache.org rather than the wiki, which can then be freed to *only* include things that the documentation does not. B. On 4 July 2011 16:34, till t...@php.net wrote: On Mon, Jul 4, 2011 at 5:09 PM, Noah Slater nsla...@echolibre.com wrote: On 4 Jul 2011, at 15:46, Robert Newson wrote: (but, hey, wikis are new, bound to be bugs). LOL HAHA... Nice. I can't find find the other wiki thread. What's the idea documentation wise, is there anyone working on something else, or so. I'd like to either do something, or at least support an ongoing effort. Till
CouchDB documentation
On Mon, Jul 4, 2011 at 5:50 PM, Robert Newson robert.new...@gmail.com wrote: All good questions -- for a different thread Ok, done. :-) So anyone have any ideas or preferences? Here are some questions: Where will documentation 'live'? Will a CLA be required to contribute to it? Format? Anything ongoing? Till
Re: CouchDB documentation
Cool, that sounds all good to me. Has anyone started on this yet? Also, can you guys recommend any tools to edit docbook [Mac, Linux, Windows]? ;-) I don't care if they are commercial or 'free'. I've used docbook for pear/php but I've always used a text editor and editing etc. is pretty tedious since it comes with a learning wall. Till On Mon, Jul 4, 2011 at 7:42 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Mon, Jul 4, 2011 at 1:37 PM, Robert Newson robert.new...@gmail.com wrote: From the existing thread (which I can't find either!), we had several votes for DocBook, the source of those docs to live alongside the code in the same svn repository we all know and love (or keep at arms length with git-svn). I'm sure we'd need signoff for contributed docs like we do for code. No more signoff than the current JIRA. Not to be confused with CLA. Though its generally recommended that significant contributors have a CLA on file. So, enh. Also, yeah. docbook in the repo. Generated output to live at http://couchdb.apache.org/lookatmyfancydocs B. On 4 July 2011 17:56, till t...@php.net wrote: On Mon, Jul 4, 2011 at 5:50 PM, Robert Newson robert.new...@gmail.com wrote: All good questions -- for a different thread Ok, done. :-) So anyone have any ideas or preferences? Here are some questions: Where will documentation 'live'? Will a CLA be required to contribute to it? Format? Anything ongoing? Till
[jira] [Created] (COUCHDB-1213) proxy with external api doesn't work
proxy with external api doesn't work
Key: COUCHDB-1213
URL: https://issues.apache.org/jira/browse/COUCHDB-1213
Project: CouchDB
Issue Type: Bug
Affects Versions: 1.1
Reporter: Till Klampaeckel
As discussed on IRC, I'm trying to use an external web API, but every request
to the handler produces an infinite loop.
This is most likely due to not passing on the correct Host header.
Here's an example:
_google = {couch_httpd_proxy, handle_proxy_req, http://www.google.com/ig;}
Then request with:
curl -L -X GET http://127.0.0.1:5984/_google/calculator?hl=enq=100EUR%3D%3FAUD
Paul Davis did a quick patch: http://friendpaste.com/62T88HOYw8QyaoIJoXEGXr
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Apache CouchDB 1.0.3 Release
On Sat, Jun 25, 2011 at 1:54 AM, Paul Davis paul.joseph.da...@gmail.com wrote: This is the release vote for Apache CouchDB 1.0.3 Changes in this release: * Fixed compatibility issues with Erlang R14B02. * Fix bug that allows invalid UTF-8 after valid escapes. * The query parameter `include_docs` now honors the parameter `conflicts`. This applies to queries against map views, _all_docs and _changes. * Added support for inclusive_end with reduce views. * More performant queries against _changes and _all_docs when using the `include_docs` parameter. * Enabled replication over IPv6. * Fixed for crashes in continuous and filtered changes feeds. * Fixed error when restarting replications in OTP R14B02. * Upgrade ibrowse to version 2.2.0. * Fixed bug when using a filter and a limit of 1. * Fixed OAuth signature computation in OTP R14B02. * Handle passwords with : in them. * Made compatible with jQuery 1.5.x. * Etap tests no longer require use of port 5984. They now use a randomly selected port so they won't clash with a running CouchDB. * Windows builds now require ICU = 4.4.0 and Erlang = R14B03. See COUCHDB-1152, and COUCHDB-963 + OTP-9139 for more information. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~davisp/dist/1.0.3-rc1/ Instructions for validating the release tarball can be found here: http://people.apache.org/~davisp/dist/ Instructions for testing the build artefacts can be found here: http://wiki.apache.org/couchdb/Test_procedure These artifacts have been built from the 1.0.3 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/1.0.3/ At some point this weekend you will be bored with nothing to do for ten to fifteen minutes, this is when you should vote. Love the momentum! Thanks for calling this vote, Paul! Ubuntu 10.04 (R13B03) make check passes FreeBSD 6.x (R13B04) gmake check passes Ubuntu 9.10 (R13B01) make check passess +1
Re: Archiving old releases
On Mon, Jun 6, 2011 at 4:44 PM, Robert Newson rnew...@apache.org wrote: All, Now that 1.1.0 is released I want your opinions on which releases we should archive. For my part, I'd like Downloads to hold just 1.1.0 and 1.0.2 and archive everything else. B. Generally, +1 Does 'archiving' break download links? Till
Re: Archiving old releases
On Mon, Jun 6, 2011 at 4:50 PM, Noah Slater nsla...@apache.org wrote: On 6 Jun 2011, at 15:47, till wrote: Does 'archiving' break download links? Archiving involves removing the link from downloads.html, which points to a CGI script which automatically picks the closest mirror to your location. It also involved moving the release to an archive distribution directory on apache.org. I don't care so much about the CGI script, but I'm asking from a package maintainer perspective. So let's say I use a mirror to download CouchDB releases, etc. -- does archiving mean they are removed from mirrors? Till
Re: [VOTE] Apache CouchDB 1.1.0 release, round 3.
On Tue, May 31, 2011 at 12:25 AM, Robert Newson rnew...@apache.org wrote: Hello, I would like call a vote for the Apache CouchDB 1.1.0 release, round 3. Two further issues have been resolved since round 2; 1) Compatibility with erlang R14B03. 2) Release tarball now works on Windows (with Cygwin). We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~rnewson/dist/1.1.0/ These artifacts have been built from the 1.1.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/1.1.0 Please follow our test procedure: http://wiki.apache.org/couchdb/Test_procedure Happy voting, B. Ubuntu (10.04): All tests successful. Files=41, Tests=735, 73 wallclock secs ( 0.44 usr 0.11 sys + 18.82 cusr 2.52 csys = 21.89 CPU) Result: PASS FreeBSD: All tests successful. Files=41, Tests=735, 85 wallclock secs (20.09 cusr + 3.78 csys = 23.87 CPU) +1 @Robert: Thanks very, very much for pulling through on this release! This is really, really appreciated! Till
init.d/couchdb
Hey guys, I just re-ran some chef-recipes I had and noticed how CouchDB 1.0.1 didn't start (/etc/init.d/couchdb) return 1. So I updated the recipe to use 1.0.2 and found the same problem. After adding 'set -x' to the script, I discovered that the 'su' call failed. Has anyone else seen this? I replaced both (for start and stop) with sudo -u $COUCHDB_USER $command which makes it work, but I reckon sudo is not too portable across the different flavours of Linux. I think the most clean and consistent approach is start-stop-daemon, but I wanted to ask here first before I write a patch. Till
Re: init.d/couchdb
On Mon, May 23, 2011 at 6:22 PM, Noah Slater nsla...@echolibre.com wrote: On 23 May 2011, at 17:14, Noah Slater wrote: Let's figure out why su is failing for you first. Did you try the command manually by the way? What happens when you try to execute that su invocation yourself? I'm guessing it's a problem with your root or couchdb user not having a valid home directory. Yes, I did. I'm just booting my vm. Will have it for you shortly. Btw, the couchdb's home is its db dir. And yes, all permissions are correct. It wouldn't work otherwise when I used sudo -u.
Re: init.d/couchdb
On Mon, May 23, 2011 at 7:07 PM, Noah Slater nsla...@apache.org wrote: On 23 May 2011, at 17:47, till wrote: I think su -c foo etc. is fundamentally wrong. Why? In the end, it's why there's start-stop-daemon. This is one solution to the problem of starting and stopping daemons. There are many solutions. We have one already. One that has been working for a number of years. The system infrastructure has been one of the most stable parts of CouchDB since it was originally added. foo:~# su couchdb -c /usr/local/bin/couchdb -b -o /dev/null -e /dev/null -r 5 In the script, we have: su $COUCHDB_USER -c $command So your example will fail because it is not quoted. foo:~# su couchdb -c /usr/local/bin/couchdb -b -o /dev/null -e /dev/null -r 5 foo:~# echo $? 127 So there's an error starting CouchDB. What is it? I really copied everything that was output. ;-) You tell me what 127 is. I think it's an exit code from su. Try this instead, and report back what you see: su couchdb -c /usr/local/bin/couchdb -b -o couchdb.out -e couchdb.err -r 5 echo $? cat couchdb.out cat couchdb.err I think since the 127 comes from su, it doesn't even get to create .out and .err. I see them nowhere. Even after changing it to /tmp/couchdb.out (etc.). Googling says, 127 - a command could not be found, but I was unable to find a dedicated list of exit codes related to su. Til
Re: init.d/couchdb
On Mon, May 23, 2011 at 7:40 PM, till t...@php.net wrote: On Mon, May 23, 2011 at 7:07 PM, Noah Slater nsla...@apache.org wrote: On 23 May 2011, at 17:47, till wrote: I think su -c foo etc. is fundamentally wrong. Why? In the end, it's why there's start-stop-daemon. This is one solution to the problem of starting and stopping daemons. There are many solutions. We have one already. One that has been working for a number of years. The system infrastructure has been one of the most stable parts of CouchDB since it was originally added. foo:~# su couchdb -c /usr/local/bin/couchdb -b -o /dev/null -e /dev/null -r 5 In the script, we have: su $COUCHDB_USER -c $command So your example will fail because it is not quoted. foo:~# su couchdb -c /usr/local/bin/couchdb -b -o /dev/null -e /dev/null -r 5 foo:~# echo $? 127 So there's an error starting CouchDB. What is it? I really copied everything that was output. ;-) You tell me what 127 is. I think it's an exit code from su. Try this instead, and report back what you see: su couchdb -c /usr/local/bin/couchdb -b -o couchdb.out -e couchdb.err -r 5 echo $? cat couchdb.out cat couchdb.err I think since the 127 comes from su, it doesn't even get to create .out and .err. I see them nowhere. Even after changing it to /tmp/couchdb.out (etc.). Googling says, 127 - a command could not be found, but I was unable to find a dedicated list of exit codes related to su. Til Ran it through strace: http://friendpaste.com/3Y9YhKmf7pFTeiW6pGT6TY Till
Re: init.d/couchdb
On Mon, May 23, 2011 at 8:30 PM, Noah Slater nsla...@apache.org wrote: On 23 May 2011, at 19:05, till wrote: Great success: foo:~# su -c couchdb -c 'echo foo' foo How about: sudo -u couchdb /usr/local/bin/couchdb Seems to work: foo:~# su -c couchdb -c /usr/local/bin/couchdb Apache CouchDB 1.0.2 (LogLevel=error) is starting. Apache CouchDB has started. Time to relax.
Re: Helping out with releases
Just wanted to ask what the status of either release is? Are the two tests failing still failing, or can we move on to make dist? :-) Till On Thu, May 12, 2011 at 5:15 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Thu, May 12, 2011 at 4:31 AM, Randall Leeds randall.le...@gmail.com wrote: On Tue, May 10, 2011 at 06:54, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, May 10, 2011 at 9:49 AM, Jan Lehnardt j...@apache.org wrote: Putting 140 on an infinite loop (while(true); do ./test/etap/run test/etap/140-attachment-comp.t ; done) eventually gives me http://www.friendpaste.com/2JCA8dvre9orA3UysYYTCe on both SSD Mac OS X 10.6 and Ubuntu 10.04 on disk in a VMWare. That's the error that I was getting. I also got one instance of http://www.friendpaste.com/7EpB1eJGRoRFBvjXvmFG3V on the Ubuntu. Never seen this one which makes things more fun. The first one comes up reliably after half a minute or so and repeats itself, it may well be a socket ulimit or something. The second one I only ever saw once so far. Cheers Jan -- Just distchecked 1.0.x and 1.1.x no problem. Give it a shot, Paul? the same, osx (with without ssd) - benoît
Re: Welcome Randall Leeds and Robert Dionne as new Committers
On Fri, May 6, 2011 at 9:56 AM, Jan Lehnardt j...@apache.org wrote: Dear developers, users, Randall and Robert, the Apache CouchDB PMC voted both Randall Leeds and Robert Dionne into the team of CouchDB committers. Both have been long time contributors and are valuable members of the community and development team. Here's to Randall and Robert and many more contributions! Cheers Jan Congrats, Randall and Bob!
Re: Debian package 0.11.0 stable?
On Tue, Apr 26, 2011 at 7:44 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Apr 26, 2011 at 7:35 PM, Noah Slater nsla...@echolibre.com wrote: On 26 Apr 2011, at 18:34, Noah Slater wrote: On 26 Apr 2011, at 18:31, till wrote: Why not link all? You would like me to exhaustively link to every part of the Debian packaging infrastructure? Heh. That could take me hours to compile. It is distributed across loads of different sites. Depending on what you're packaging, with whom, and what you want to do, or know, about that effort. Having said that, this is a good place to start: http://packages.qa.debian.org/c/couchdb.html Or simply maintain a ppa on launchpad . - benoit Didn't know you can have a debian PPA on launchpad. In this case, I can try to help too. We just went through the setup for some other stuff 'in house'. Sort of related -- does Apache maintain an apt-mirror or would they support that? That would be extremely nice if this launchpad PPA could be mirrored by them to sail around downtimes and capacity issues. Till
Re: Development environment
On Fri, Apr 29, 2011 at 2:38 AM, Miles Fidelman mfidel...@meetinghouse.net wrote: Andrey Somov wrote: On Fri, Apr 29, 2011 at 1:01 AM, Paul Davispaul.joseph.da...@gmail.comwrote: On Thu, Apr 28, 2011 at 6:57 PM, Nathan Stottnrst...@gmail.com wrote: So couchdb is really developed without using step-by-step debugging at all? That seems quite odd. I never use step by step debugging on any project in any language. I've never found it that useful. step by step debugging of a unit test is one the most effective ways to find bugs. Until you start running highly concurrent software, distributed across multiple nodes. That takes debugging to a whole new level. A unit test doesn't run on multiple nodes.
Re: 1.1.0
On Wed, Apr 27, 2011 at 12:26 AM, Randall Leeds randall.le...@gmail.com wrote: On Tue, Apr 26, 2011 at 15:13, Paul Davis paul.joseph.da...@gmail.com wrote: 1141 reported today might be a good candidate to get in. It looked pretty simple and I think me and Rob and Adam narrowed down the fix on IRC earlier. We should just get in the habit of making bugfix releases not take forever. Ship it in two weeks as 1.1.1 with anything else we uncover in the meantime. There will always be problems and issues that no amount of test suite running will reveal and we'll find them faster if we get 1.1 out the door. On Tue, Apr 26, 2011 at 6:06 PM, Jan Lehnardt j...@apache.org wrote: Hey all http://s.apache.org/couchdb-open-issues-1.1.0 shows No matching issues found. First: Hooray and thanks everybody for helping :) Second: We should get this out. Is there anything else you'd like to see addressed before we kick off the release procedure? Cheers Jan -- +1 Ship 1.1.0 already. :-)
Re: Debian package 0.11.0 stable?
On Tue, Apr 26, 2011 at 7:17 PM, Sam Bisbee s...@sbisbee.com wrote: On Tue, Apr 26, 2011 at 12:37 PM, Noah Slater nsla...@apache.org wrote: On 26 Apr 2011, at 17:09, Jens Rantil wrote: I have noticed that there is very little activity on Debian packaging of Apache CouchDB. The latest version of is 0.11.0 for both Debian stable, unstable and testing. This is depressing. I thought some people had stepped up to maintain this package. What happened with that. Are you peeps still out there? Yup, I'm right here. :) What happened was Debian's release policies and technical committee flew in the face of everything we were trying to do. They weren't even supposed to release 0.11 into stable according to their guidelines because stepping to it from 0.8 was going to break code. They wanted me to back port security fixes from 0.11 and 1.x into 0.8. Then they got upset that 0.8 ever made it into stable. THEN the whole desktop-couch and Ubuntu initiative somehow took over. To summarize, I became disinterested in maintaining the package under Debian, but might be interested in maintaining a separate one. I believe I spoke with Sergei that I was stepping back, but that could be a faulty memory. I assume that Sergei hasn't been working on it and that Debian's release team auto-pushed 0.11 into stable. These days I just install from source. Like I said, I could be coerced into offering unofficial .deb's, but would be more interested in seeing either CouchDB or a supportive company picking up the fight with or without my help. Couchbase has a .deb. No idea if it works on Debian though. :-) Is there anything like launchpad for debian? Till
Re: Debian package 0.11.0 stable?
On Tue, Apr 26, 2011 at 7:30 PM, Noah Slater nsla...@apache.org wrote: On 26 Apr 2011, at 18:26, till wrote: Is there anything like launchpad for debian? Debian has lots of different sites that manage these things. I'd need to know what you wanted to do before I could link the correct one. Why not link all?
[jira] Created: (COUCHDB-1069) Init script report OK even when there's already another CouchDB process on the same port.
Init script report OK even when there's already another CouchDB process on the same port. --- Key: COUCHDB-1069 URL: https://issues.apache.org/jira/browse/COUCHDB-1069 Project: CouchDB Issue Type: Bug Affects Versions: 1.0.2 Environment: Ubuntu Reporter: Till Klampaeckel Priority: Minor I had another CouchDB installation running which I installed through aptitude. When I compiled couchdb from source and started it through the included init script, the processes were running and the start script reported OK. However, on port 5984 I had the other install running. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Trying to post to user list unsuccessful
I just checked and according to infra it's a known issue. Triggered by the word replication - together with HTML messages. ;-) Best is to use text/plain when sending messages. Till On Fri, Feb 18, 2011 at 2:14 AM, Ryan Ramage ryan.ram...@gmail.com wrote: I am trying to post to the user list, maybe someone wants to check the mail list owner? this is the response I get: Delivery to the following recipient failed permanently: u...@couchdb.apache.org Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 spam score (5.1) exceeded threshold (FREEMAIL_FROM,FS_REPLICA,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS (state 18). - Original message - MIME-Version: 1.0 Received: by 10.227.128.75 with SMTP id j11mr99273wbs.60.1297991366962; Thu, 17 Feb 2011 17:09:26 -0800 (PST) Received: by 10.227.8.101 with HTTP; Thu, 17 Feb 2011 17:09:26 -0800 (PST) Date: Thu, 17 Feb 2011 18:09:26 -0700 Message-ID: aanlktinlhpohmz_tbcct6g+offpoffnh6q0sl3wr-...@mail.gmail.com Subject: Replication behind firewalls From: Ryan Ramage ryan.ram...@gmail.com To: user u...@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016e6586528596e46049c842aa4
Re: roadmap
On Tue, Feb 8, 2011 at 10:33 AM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Tue, Feb 8, 2011 at 10:24, Benoit Chesneau bchesn...@gmail.com wrote: ... and you ? Most of all, I want a better schedule/insight into the release process. Even when reading the dev list, it's completely unclear when I might expect the next release or what the blockers are. Releases seem to just keep slipping, or maybe releasing isn't a very big priority, at least that's what it looks like from the outside. For the rest, I would like more documentation. The CouchOne API documentation is a step in the right direction, having good docs about the query server protocol would also be very helpful. Yes, I realize I can read the couchjs JS code, but that's not a substitute for good docs. The new Futon that Mikeal was working on would be nice to have. As for more pie-in-the-sky things, it would be nice to have more efficient view indexing (using multiple processes, for example -- map/reduce should enable that, right?) and an official way to do full-text search. Cheers, Dirkjan +1 to the above
Re: [VOTE] Apache CouchDB 1.0.2 Release, Round 3
On Thu, Jan 20, 2011 at 4:06 PM, Paul Davis paul.joseph.da...@gmail.com wrote: This is the third release vote for Apache CouchDB 1.0.2 Changes since the last round: * Fix raw view document link due to overlealous URI encoding in Futon. * Spell javascript correctly in loadScript(uri). * Preserve purge metadata during compaction to avoid spurious view regeneration. * Fix spurious conflicts during attachment uploads after a document has had a conflict. See COUCHDB-902 for details. * Fix multipart GET APIs to always send attachments in compressed form when they are compressed on disk. This fixes a bug for attachments created via local-local replication. See COUCHDB-1022 for details. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release. Please report your results and vote to this thread. We are voting on the following release artifacts: http://people.apache.org/~davisp/dist/1.0.2/ These artifacts have been built from the 1.0.2 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/1.0.2/ Happy voting! All tests successful. Files=34, Tests=528, 43 wallclock secs (14.97 cusr + 1.83 csys = 16.80 CPU) Ubuntu 9.10, R13B01, Spidermonkey 1.8.1 +1
Re: Preparing 1.0.2 release.
On Tue, Jan 4, 2011 at 1:30 AM, Paul Davis paul.joseph.da...@gmail.com wrote: Anyone have an objection to me calling a 1.0.2 vote? Now that COUCHDB-968 and COUCHDB-999 are fixed we have finished the blockers. Though I now see that there's an issue [1] listed under 1.0.2 but I'm inclined to just reassign it to 1.1.x. [1] https://issues.apache.org/jira/browse/COUCHDB-998 Just curious -- why is the patch attached not applied? Till
Re: Preparing 1.0.2 release.
On Tue, Jan 4, 2011 at 3:19 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Tue, Jan 4, 2011 at 2:51 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Tue, Jan 4, 2011 at 4:09 AM, till t...@php.net wrote: On Tue, Jan 4, 2011 at 1:30 AM, Paul Davis paul.joseph.da...@gmail.com wrote: Anyone have an objection to me calling a 1.0.2 vote? Now that COUCHDB-968 and COUCHDB-999 are fixed we have finished the blockers. Though I now see that there's an issue [1] listed under 1.0.2 but I'm inclined to just reassign it to 1.1.x. [1] https://issues.apache.org/jira/browse/COUCHDB-998 Just curious -- why is the patch attached not applied? Till I reckon it's because no one that knows JavaScript has reviewed it to decide if it should be applied. I answered to the ticket. If I read correctly the futon code, the patch is OK. Can't commit from this machine so I will let you do the final step :) - benoit Thanks, Benoit! Kind of related -- anyone remember the futon work Mikeal did. Whatever happened to it? Does it address those issues as well? I don't want to stall the release but is Mikeal's work more a 1.1.x feature? Till
Re: use view functions to emit changes
On Mon, Dec 6, 2010 at 7:04 PM, Benoit Chesneau bchesn...@gmail.com wrote: On Mon, Dec 6, 2010 at 6:57 PM, Mikeal Rogers mikeal.rog...@gmail.com wrote: But for the record, nobody except people who wish they were writing Python use 4 space indentation everywhere. It's the part of crockford's style guide that is most often ignored. except maybe BSD developers, Erlang developers,etc . sure 4 spaces is python thing - benoît Or PHP, Ruby...
Re: New Website Styles
On Tue, Nov 30, 2010 at 3:53 PM, Kristina Schneider krie...@couchone.com wrote: Hi everybody, I am the creative head at CouchOne, and Jan asked me to help out with the redesign of the Apache CouchDB Website. He pointed me to Klaus Trainer’s fork, and I took it from there. https://github.com/Kriesse/couchdb_web Hey, it really looks great with colors and all -- as do all things you design! :-) Here are my but's: IMHO, the frontpage has too much of a ecommerce landing page, what I mean is -- it is maybe a tiny bit too over-commercialiazed (if there is such a word). The 'quote' on top, etc.. Right now, it's just missing a PURCHASE NOW link. ;-) On 1024x768 all I only see the header -- I like the smaller version (on download.html) much better. Sidenote: It's nice that this looks similar to CouchOne, but the CouchDB project also consists of other people ;-) Till
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On Sun, Nov 28, 2010 at 8:58 PM, Robert Newson robert.new...@gmail.com wrote: I don't think we should make a release when we have a known and serious bug. +1
Re: [VOTE] Apache CouchDB 1.0.2 release, Round 1
On Fri, Nov 26, 2010 at 7:14 AM, Peter Lemenkov lemen...@gmail.com wrote: 2010/11/26 Robert Newson robert.new...@gmail.com: pretty sure ibrowse and mochiweb have important tweaks, using versions without them is broken. I'm not sure about mochiweb (since couchdb contains very old svn snapshot, and it's hard to check for the differences) but regarding ibrowse - couchdb is only 1 patch behind the 2.1.0. I'll plan to backport in into 2.1.0 shipped in Fedora. So a) These libraries are not so different from upstream ones (at least true for ibrowse) b) CouchDB in Fedora isn't so deadly broken as someone of you may think In fact I'm watching very closely the development of both ibrowse and mochiweb so I'm aware of the changes made or just proposed by CouchDB folks. Please correct me if am I wrong (actually... :D) but what Peter is doing is pretty common for packaging. And in the end, there is a test suite to make sure everything works. ;-) If it doesn't catch an issue, it might need an improvement, or two. Till
Re: [VOTE] Apache CouchDB 1.0.2 release, Round 1
On Thu, Nov 25, 2010 at 7:43 PM, Paul Davis paul.joseph.da...@gmail.com wrote: [ ... ] We are voting on the following release artifacts: http://people.apache.org/~davisp/dist/1.0.2/ [one of my older production servers] FreeBSD 6.x/i386 Erlang R13B04 Spidermonkey 1.7.x gmake check = great success [in a virtualbox] FreeBSD 8.1/i386 Erlang R14B Spidermonkey 1.7.x gmake check = great success +1
Re: tracking upstream dependencies
E.g. for packaging on distros like FreeBSD you usually download the the software in an unmodified state from an official mirror [of the software] and then patch it before building and registering the install. So e.g., I'd download CouchDB from an apache mirror and then patch whatever I need and then it runs ./configure, make, etc.. All configure by the port's Makefile. This of course relies on people not re-releasing a different version with the same ID, etc.. But of course validation of checksums of the archives are build in to avoid this sort of thing from happening. How often does it happen that CouchDB has to patch/modify software like Mochiweb? And what are the chances to push the patches to upstream prior to releasing CouchDB. I realize this could slow down the release process, but it would make a cleaner build. Till On Fri, Nov 26, 2010 at 9:44 PM, Noah Slater nsla...@apache.org wrote: The release artefact absolutely should not, ever, pull down files from the network. However, I can see a way forward by having the bootstrap script manage the bundling of external dependancies. The bootstrap script should only ever be run from a checkout of the code. Whatever it downloaded and prepared would be included as part of the release artefact. But assuming we got this working, we face the problem of not being able to apply our own patches. Also, the software it downloads might have some bug in it that was introduced a week, day, or hour before the release was made. How would we defend ourselves against this? On 26 Nov 2010, at 20:38, Adam Kocoloski wrote: Hi all, there's a discussion in the 1.0.2 voting thread about better tracking of upstream dependencies like mochiweb. One point that keeps getting brought up is that build systems should not need network access. Is that a rule which applies to building from an SCM repo, or only to builds of release artifacts? I think we might be able to make our lives easier if we only bundled upstream dependencies at release generation time, and otherwise relied on the build system to retrieve them. For a concrete example, BigCouch recently switched to using rebar for dependency resolution. The main repo at https://github.com/cloudant/bigcouch only has the couch OTP application in it, the other dependencies are pulled from forked git repositories containing CouchDB-specific branches and tags such as https://github.com/cloudant/ibrowse/tree/CouchDB-1.0.1 If the no-network-access rule does apply to SCM builds, we might consider bundling full git repos instead of doing the source code copy/paste dance. At least this would allow a clearer indication of where we stand w.r.t upstream. Best, Adam
Re: Releaseing 1.0.2 and 1.1.0
Woohoo! Thanks both of you! On Thu, Nov 18, 2010 at 2:43 PM, Filipe David Manana fdman...@apache.org wrote: Thanks Randall. On Thu, Nov 18, 2010 at 1:01 AM, Randall Leeds randall.le...@gmail.com wrote: On Wed, Nov 17, 2010 at 16:51, Filipe David Manana fdman...@apache.org wrote: COUCHDB-926 is now fixed. Woohoo! Thanks, Filipe :) As for at least 1.1.0, I would like to have COUCHDB-949 in it (and maybe 1.0.2 as well). Vote? Looks good to me. +1. On Wed, Nov 17, 2010 at 7:25 PM, Randall Leeds randall.le...@gmail.com wrote: +1 on making the branches. I'd be happy to look into 926. On Nov 17, 2010 6:55 AM, Jan Lehnardt j...@apache.org wrote: Heya, I spent some time trimming down the open issues for 1.0.2 and 1.1.0: http://s.apache.org/couchdb-open-issues-1.0.2 (1 open issue) http://s.apache.org/couchdb-open-issues-1.1.0 (3 open issues) To get things rolling, I propose creating the 1.1.x release branch now. The remaining patches can easily be backported and we can continue feature work on trunk. -- The issues are: 1.0.2: Compaction does not release file descriptors https://issues.apache.org/jira/browse/COUCHDB-926 1.1.0: out of memory crash when compacting document with lots of edit branches https://issues.apache.org/jira/browse/COUCHDB-888 refactor os process management https://issues.apache.org/jira/browse/COUCHDB-901 And 926 again. If anybody can help out with these, that'd be great :) Cheers Jan -- -- Filipe David Manana, fdman...@gmail.com, fdman...@apache.org Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men. -- Filipe David Manana, fdman...@gmail.com, fdman...@apache.org Reasonable men adapt themselves to the world. Unreasonable men adapt the world to themselves. That's why all progress depends on unreasonable men.
Re: Postgresql to couchdb NetBeans Plugins
Hey, and I was wondering what it means when you say, export tables. ;-) For example, do you export the data contained in those tables and build some views to find the data again, or what's the plan? Just curious. Till On Sun, Aug 22, 2010 at 7:20 PM, aristides villarreal avbr...@gmail.com wrote: in this moment is a basic plugins(alpha version) that export tables of postgresql. I want to expand the functionality to export mysq (tables), include views and support for interacting with CouchDB in the plugin. On Sun, Aug 22, 2010 at 11:52 AM, till t...@php.net wrote: Would you share in English what this does (exactly)? From the blog post - you analyze the structure and export them to CouchDB. Do you also create views or something? My Spanish is a bit rusty. :-) Till On Sun, Aug 22, 2010 at 5:24 PM, aristides villarreal avbr...@gmail.com wrote: I developed a basic plugin for netbeans to export tables from a PostgreSQL database CouchDB More information in my blog http://avbravo.blogspot.com/2010/08/p2cnb-postgresql-to-couchdb-netbeans.html -- - Member of NetBeans Dream Team http://www.netbeans.org/community/contribute/dreamteam.html http://dreamteam.netbeans.org/ http://wiki.netbeans.org/wiki/view/SpanishTranslation NetBeans Community Docs Evangelist http://nb-community-docs.blogspot.com/2008/09/welcome-community-docs-evangelists.html http://avbravo.blogspot.com -- - Member of NetBeans Dream Team http://www.netbeans.org/community/contribute/dreamteam.html http://dreamteam.netbeans.org/ http://wiki.netbeans.org/wiki/view/SpanishTranslation NetBeans Community Docs Evangelist http://nb-community-docs.blogspot.com/2008/09/welcome-community-docs-evangelists.html http://avbravo.blogspot.com
[jira] Created: (COUCHDB-865) More ./configure options
More ./configure options Key: COUCHDB-865 URL: https://issues.apache.org/jira/browse/COUCHDB-865 Project: CouchDB Issue Type: New Feature Affects Versions: 1.0.1, 0.11.2 Reporter: Till Klampaeckel So for example ob Linux, this defaults file is written when CouchDB is installed: COUCHDB_USER=couchdb COUCHDB_STDOUT_FILE=/dev/null COUCHDB_STDERR_FILE=/dev/null COUCHDB_RESPAWN_TIMEOUT=5 COUCHDB_OPTIONS= I'd like to be able to influence these things with ./configure. ./configure --couchdb-user=root --couchdb-respawn-timeout=10 --couchdb-port=80 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [VOTE] Apache CouchDB 0.11.2 release, first round
On Fri, Aug 6, 2010 at 1:36 PM, Noah Slater nsla...@apache.org wrote: Hello, I would like call a vote for the Apache CouchDB 0.11.2 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/0.11.2/ These artifacts have been built from the 0.11.2 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/0.11.2/ Happy voting, N +1, (g)make check and test suite complete :-) FreeBSD 6, 7, 8 Till
Re: [jira] Commented: (COUCHDB-837) Adding stale=partial
I think marking it as deprecated would be the way to go. Then clean it up in the next major (!) release (e.g. 2.0). Till On Wed, Jul 28, 2010 at 1:55 PM, Volker Mische volker.mis...@gmail.com wrote: I think deprecating parts of the API after 1.0 is alright, as long if it's still there till the next stable major release. We extend the API, and I don't see a difference between extending it with a new value for an existing key and extending it with a new key. Except that the latter is cleaner in this case IMHO. Though I could also live with stale=update_after. Cheers, Volker On 07/28/2010 01:40 PM, Filipe David Manana wrote: Do we have some JIRA allergy? I don't mind a new parameter, whatever its name might be. But it introduces a bigger change in the API, and abandoning stale in favour of this new parameter wouldn't be reasonable before at least one major release (2.0, 3.0 whatever, but definitely not 1.x). I would like to have this (independently of the naming we use) for 1.1. Raise your hands if you're against or in favour of stale=update_after (seems meaningful to me). On Wed, Jul 28, 2010 at 7:21 AM, Sebastian Cohnen sebastiancoh...@googlemail.com wrote: this is exactly what I tried to say with my comment :) add a new parameter and keep stale=ok (with its current behavior around for backward compatibility) On 27.07.2010, at 23:47, Volker Mische wrote: I prefer Roberts suggestion. Adding a new parameter that will replace stale in the long run, that has understandable values. stale=ok could be kept and deprecated and finally replaced in a 1.1/2.0. update=now|no|after sounds good (though now/no has a high chance of a typo). Cheers, Volker On 07/27/2010 11:40 PM, Robert Newson wrote: this could run forever so stale=update_after is as good as any suggestion so far. I say get it on trunk, if anyone feels strongly, there's time before it's in a release. ?update=now (default)|no|later/next/after might be better but breaks back compatibility. B. On Tue, Jul 27, 2010 at 10:36 PM, Klaus Trainerklaus.trai...@web.de wrote: +1 This one sounds good. It clearly makes obvious the update semantics. On Tue, 2010-07-27 at 17:27 -0400, Filipe Manana (JIRA) wrote: [ https://issues.apache.org/jira/browse/COUCHDB-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12892934#action_12892934 ] Filipe Manana commented on COUCHDB-837: --- So, having a: stale=update_after Anyone against? Adding stale=partial Key: COUCHDB-837 URL: https://issues.apache.org/jira/browse/COUCHDB-837 Project: CouchDB Issue Type: Improvement Environment: all released and unreleased versions Reporter: Filipe Manana Assignee: Filipe Manana Attachments: stale_partial.patch Inspired by Matthias' latest post, at http://www.paperplanes.de/2010/7/26/10_annoying_things_about_couchdb.html, section Views are updated on read access, I added a new value to the stale option named partial (possibly we need to find a better name). It behaves exactly like stale=ok but after replying to the client, it triggers a view update in the background. Patch attached. If no one disagrees this isn't a good feature, or suggest a better parameter value name, I'll commit.
Re: [VOTE] Apache CouchDB 1.0.0 release, first round
On Thu, Jul 8, 2010 at 5:25 PM, Jan Lehnardt j...@apache.org wrote: On 8 Jul 2010, at 17:22, till wrote: On Thu, Jul 8, 2010 at 1:38 AM, Noah Slater webmas...@nslater.org wrote: Hello, I would like call a vote for the Apache CouchDB 1.0.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/1.0.0/ These artifacts have been built from the 1.0.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/1.0.0/ Happy voting, N -1 Downloaded the tarball from Noah's space. OS: FreeBSD 6.x ./configured worked, make fails: extremely% make How about extremely% gmake? Har. I keep forgetting this. Sorry: +1 that mofo. ./configure, gmake, gmake check - Great success! ;-) All tests successful. Files=34, Tests=509, 47 wallclock secs (18.84 cusr + 3.20 csys = 22.03 CPU) Till
Re: [VOTE] Apache CouchDB 1.0.0 release, first round
On Thu, Jul 8, 2010 at 1:38 AM, Noah Slater webmas...@nslater.org wrote: Hello, I would like call a vote for the Apache CouchDB 1.0.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/1.0.0/ These artifacts have been built from the 1.0.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/1.0.0/ Happy voting, N Ubuntu 10.04: ./configure --with-js-lib=/usr/lib/xulrunner-devel-1.9.2.6/lib --with-js-include=/usr/lib/xulrunner-devel-1.9.2.6/include make export LD_LIBRARY_PATH=/usr/lib/xulrunner-devel-1.9.2.6/lib make check All tests successful. Files=34, Tests=509, 45 wallclock secs ( 0.18 usr 0.08 sys + 15.70 cusr 2.34 csys = 18.30 CPU) Result: PASS Ubuntu: Question - should the above be added to the readme file for Ubuntu? Also, I'm guessing the start script needs to do this on ubuntu as well. Should this be build in? CentOS: Also wondering if anyone had any luck building 1.0.0 on CentOS - it fails right now because of libcurl (7.15, but 7.18 is required). Even with the latest CentOS 5.5, there's no libcurl 7.18. Some people say that they backport a lot of fixes though, so could we instead assume that 7.15 on CentOS works with CouchDB? Is there any special reason to require libcurl 7.18 vs. 7.15? Till
Re: 1.0 Vote
On Tue, Jun 29, 2010 at 4:38 PM, Noah Slater nsla...@tumbolia.org wrote: On 29 Jun 2010, at 15:20, J Chris Anderson wrote: So I went through both trunk and 0.11.x looking for things that are out of place. I fixed one small thing in 0.11.x, and as far as I'm concerned it is ready for release. For trunk, I think there are a couple of small patches that Adam wants to hold back for 1.1. There is also the Windows stuff, which looks like we should wait for, before cutting 1.0. I am waiting for a go command, so just let me know. Please can everyone check that make distcheck is working for them. Let's try to avoid the test failures again for this release. What's the tag to use? trunk?
Re: Anything else for 1.0? (Was: Re: New code goes into trunk)
I'd like to second COUCHDB-780. :D On Tue, Jun 15, 2010 at 7:22 PM, Randall Leeds randall.le...@gmail.com wrote: https://issues.apache.org/jira/browse/COUCHDB-780 relates to windows file issues as well as fixing a source of surprising unresponsiveness with big databases (finishing compaction, deleting, etc). This patch is the only one I'd really like to wrap up for 1.0. On Jun 15, 2010 9:16 AM, Juhani Ränkimies juh...@juranki.com wrote: On Tue, Jun 15, 2010 at 6:22 PM, Jan Lehnardt j...@apache.org wrote: Which other issues or patches that are not in 0.11.x yet do you think need to be addressed befor... Windows file handling problems (https://issues.apache.org/jira/browse/COUCHDB-86 and https://issues.apache.org/jira/browse/COUCHDB-326) -juhani
Re: CouchDB Partitioning Proposal
Hey Rob, the rest of us is missing the earlier part of the discussion. :D Or maybe the reply is broken and I didn't get sorted to the original email... Btw, if interested in the partitioning, etc. - free free to subscribe to the lounge mailinglist: http://groups.google.com/group/couchdb-lounge Till On Wed, Jun 9, 2010 at 11:29 AM, Rob Stewart robstewar...@googlemail.com wrote: Hi Randall, With a response time like that, efficiency is your strong point. First of all, seeing as through there are a number of “solutions”, it's clear that there are positives to come from a fully distributed CouchDB database. So I am not put off by that. Next, you suggest potential like solution as Cassandra and Dynamo. I'd tend to agree, as these are stable distributed systems. On saying that, Cassandra doesn't use Erlang (as a Java implementation), though it adopted the flexible column layout from Google's BigTable. I've also had a look at MongoDB, which is a C++ implementation, but with similar goals as CouchDB (document-oriented database). They are currently working on database partitioning, though it's in its alpha stages, in version 1.5.3. I imagine that MongoDB could be a good design guide for CouchDB in the future should its sharding implementation matures. In a slightly unrelated note, can I point you to a paper published in February, 2010 - “Key/Value Datastores Comparison in AppScale”. Briefly, AppScale is a open source drop-in replacement for Google's App Engine, and provides API's to Cloud based web applications (typicall), and at the backend that have plugged in their app API's to the API's of 7 distributed databases (including Cassandra and MongoDB). What are the chances of attaching CouchDB to the AppScale API's ? My final point is Scalaris. (Google “Reliable Transactional P2P Key/Value Store”). Like CouchDB, it is a P2P datastore, implemented in Erlang. Appears to be similar in design and implementation to CouchDB, to me? It uses Chord# to storing and retreiving key/values in nodes. It seemingly has support for Heterogeneous hardware clusters, and it currently uses an in-memory disctionary for database stores, though using Mnesia has been suggested. Is that enough, to generate discussion, Randall ? Rob Stewart
[jira] Commented: (COUCHDB-782) Restarting replication
[
https://issues.apache.org/jira/browse/COUCHDB-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12875159#action_12875159
]
Till Klampaeckel commented on COUCHDB-782:
--
Until I find time for the wiki:
The mechanism does not just depend on the host per se, all the following URIs
are different to CouchDB even though they point to the same system:
http://foo:b...@localhost:5984/citations
http://localhost:5984/citations
@Randall
While you're at it doing UUIDs for databases, do you think it would be possible
to do a UUID for a server as well? It could be exposed with the version. It
would be very useful in large scale setups for monitoring etc.. E.g. to easily
tell shards apart, etc.. Vs. building external logic that revolves around
hostnames, port numbers or different something.
Restarting replication
---
Key: COUCHDB-782
URL: https://issues.apache.org/jira/browse/COUCHDB-782
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 0.10
Environment: Ubuntu, 9.10
Reporter: Till Klampaeckel
So we had to restart replication on a server and here's something I noticed.
At first I restarted the replication via the following command from localhost:
curl -X POST -d '{source:http://localhost:5984/foo;,
target:http://remote:5984/foo}' http://localhost:5984/_replicate
In response, futon stats:
W Processed source update #176841152
That part is great.
Last night I did not have immediate access to the shell so I restarted
replication from remote (through curl on my mobile):
curl -X POST -d '{source:http://user:p...@public.host:5984/foo;,
target:http://remote:5984/foo}'
http://user:p...@pubic.host:5984/_replicate
The response in futon this morning:
W Processed source update #1066
... and it kept sitting there like it was stalled and only continued in
smaller increments.
I restarted CouchDB and restarted from localhost - instant jump to 176
million.
I'm just wondering what might be different accept for that one is against the
public interface, vs. localhost. I'd assume that replication behaves the same
regardless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-782) Restarting replication
Restarting replication
---
Key: COUCHDB-782
URL: https://issues.apache.org/jira/browse/COUCHDB-782
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 0.10
Environment: Ubuntu, 9.10
Reporter: Till Klampaeckel
So we had to restart replication on a server and here's something I noticed.
At first I restarted the replication via the following command from localhost:
curl -X POST -d '{source:http://localhost:5984/foo;,
target:http://remote:5984/foo}' http://localhost:5984/_replicate
In response, futon stats:
W Processed source update #176841152
That part is great.
Last night I did not have immediate access to the shell so I restarted
replication from remote:
curl -X POST -d '{source:http://user:p...@public.host:5984/foo;,
target:http://remote:5984/foo}' http://user:p...@pubic.host:5984/_replicate
The response in futon this morning:
W Processed source update #1066
... and it kept sitting there like it was stalled and only continue in smaller
increments.
I restarted CouchDB and restarted from localhost - instant jump to 176 million.
I'm just wondering what might be different accept for that one is against the
public interface, vs. localhost. I'd assume that replication behaves the same
regardless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-782) Restarting replication
[
https://issues.apache.org/jira/browse/COUCHDB-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12874666#action_12874666
]
Till Klampaeckel commented on COUCHDB-782:
--
I guess I agree that it's important.
This is probably not an issue for installs on a smaller scale but gets annoying
when you're in for moar.
Restarting replication
---
Key: COUCHDB-782
URL: https://issues.apache.org/jira/browse/COUCHDB-782
Project: CouchDB
Issue Type: Bug
Components: Replication
Affects Versions: 0.10
Environment: Ubuntu, 9.10
Reporter: Till Klampaeckel
So we had to restart replication on a server and here's something I noticed.
At first I restarted the replication via the following command from localhost:
curl -X POST -d '{source:http://localhost:5984/foo;,
target:http://remote:5984/foo}' http://localhost:5984/_replicate
In response, futon stats:
W Processed source update #176841152
That part is great.
Last night I did not have immediate access to the shell so I restarted
replication from remote (through curl on my mobile):
curl -X POST -d '{source:http://user:p...@public.host:5984/foo;,
target:http://remote:5984/foo}'
http://user:p...@pubic.host:5984/_replicate
The response in futon this morning:
W Processed source update #1066
... and it kept sitting there like it was stalled and only continued in
smaller increments.
I restarted CouchDB and restarted from localhost - instant jump to 176
million.
I'm just wondering what might be different accept for that one is against the
public interface, vs. localhost. I'd assume that replication behaves the same
regardless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: scalability of couchdb
On Mon, May 24, 2010 at 9:25 AM, Matteo Redaelli matteo.redae...@gmail.com wrote: Hello I currectly use couchdb as repository for my the Ebot project ( http://www.redaelli.org/matteo-blog/projects/ebot/). My db is getting more and more bigger.. rw-r-r— 1 couchdb 81099821870 2010-05-23 ebot.couch rw-r-r— 1 couchdb 392589468 2010-05-23 .ebot_design For better scalability it would be better that 1) couchdb wrote data not only to one single file but to different files to DIFFERENT directories: in this way it would be easier to add new devices, file systems ... 2) couchdb distributed (non only replicated) data among several instances. like Riak and other NOSQL databases Do you think that these 2 features could be implemented in the next near future? or are they out of the scope of couchdb project? Thanks in advance Hi Matteo, you should try CouchDB-Lounge for your setup. It's not yet as smooth as riak or cassandra do partitioning (and auto-balancing, etc.) but it should get you started as well. Further reading: http://tilgovi.github.com/couchdb-lounge/ http://groups.google.com/group/couchdb-lounge http://till.klampaeckel.de/blog/archives/84-A-toolchain-for-CouchDB-Lounge.html CouchDB-Lounge is nginx, a twistd daemon and several CouchDB servers which can all run on the same server, of course. It'll help you utilize all the resources until you outgrow your current server and then it's trivial to move a couple of your shards to another one and spread it out. CouchDB-Lounge currently doesn't do auto-balancing which is useful if you want to add another server to your cluster. Instead the proposal is to overshard (run more CouchDB instances than you need on the same server) or add another lounge to the cluster and partition behind it. If you're running into space issues right now it helps to move the views (.ebot_*) to another disk and configure view_index_dir in your local.ini. Hope that helps! Cheers, Till
Re: Designer add-on for Futon
On Mon, May 17, 2010 at 3:30 PM, mickael.bai...@free.fr wrote: Hello Couchers, for 1 month now I'm coding a new futon page : the goal is to ease the developper of CouchDB views/lists/shows through Futon web interface. I called it futon designer because I really suck at finding supercool marketing names. The interface is an HTML5 application, in the sense that it uses the canvas html5 tag. I use the bespin embeded editor, that provides as-you-type syntax highlighting. I tried to mimic the existing futon code as much as possible. Now it's working good enough for my personnal use. Here are some screenshots : http://img10.hostingpics.net/pics/423266futon_designer_home.png http://img10.hostingpics.net/pics/949407futon_designer_list.png http://img708.imageshack.us/img708/673/futondesignershow.png http://img20.imageshack.us/img20/7909/futondesignerview.png I'm sending this email to get some constructive feedback on this add-on before any attempt of having it included in the CouchDB official tarball. To try it : download the zipfile @ http://www.megaupload.com/?d=TW954Q39 Move designer.html and the designer folder to [your couchdb install dir]/share/couchdb/www Point your browser to http://souch-server:5984/_utils/designer.html?[database name] , where [database name] is the name of an existing database (containing at least 1 design document). Any feedback welcome Mickael Pretty awesome! You need to open an issue on Jira so this gets included! :) Till
[jira] Commented: (COUCHDB-753) Add config option for view compact dir
[ https://issues.apache.org/jira/browse/COUCHDB-753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12867547#action_12867547 ] Till Klampaeckel commented on COUCHDB-753: -- I admit, I haven't really thought this through. My issue is that sometimes people run out of disk space with compaction. You (not necessarily you or CouchDB) could do something like block writes etc. when a compact is about to replace the database dir. Expose something from the server via JSON? Add config option for view compact dir -- Key: COUCHDB-753 URL: https://issues.apache.org/jira/browse/COUCHDB-753 Project: CouchDB Issue Type: Improvement Components: Database Core Reporter: Till Klampaeckel CouchDB creates a foo.view.compact file in the view directory (view_index_dir) when you run compact against a view. I'd really like to be able to specify another directory where this .compact file is created and worked on. This is especially helpful when it's difficult to run compaction because you run out of disk space on the same device. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Wiki (Re: _changes timeout has a max of 60 seconds?)
Just wanted to thank Sebastian for improving the wiki constantly! Till On May 7, 2010 8:31 PM, Sebastian Cohnen sebastiancoh...@googlemail.com wrote: I took the liberty to add this information to the wiki :) On 07.05.2010, at 18:51, Damien Katz wrote: This is the intent. The max timeout value is se...
[jira] Commented: (COUCHDB-164) Make error messages more verbose
[
https://issues.apache.org/jira/browse/COUCHDB-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12863837#action_12863837
]
Till Klampaeckel commented on COUCHDB-164:
--
I got another pretty one:
os_process_error {exit_status,2}
... this means that a path which is somewhere compiled into CouchDB does not
exist anymore. (The viewserver was broken after I moved an install to another
server).
Make error messages more verbose
--
Key: COUCHDB-164
URL: https://issues.apache.org/jira/browse/COUCHDB-164
Project: CouchDB
Issue Type: Improvement
Components: Database Core
Affects Versions: 0.9
Environment: Linux till-laptop 2.6.24-21-generic #1 SMP Tue Oct 21
23:09:30 UTC 2008 x86_64 GNU/Linux
Reporter: Till Klampaeckel
The following error designates that there is no space left on device, it
could say just that. :-)
[Tue, 18 Nov 2008 18:20:25 GMT] [error] [0.57.0] {error_report,
0.22.0,
{0.57.0,
std_error,
{mochiweb_socket_server,
235,
{child_error,
{{{badmatch,{{error,enospc},4414824448}},
[{couch_stream,write_data,2},
{couch_stream,write_data,2},
{couch_stream,handle_call,3},
{gen_server,handle_msg,6},
{proc_lib,init_p,5}]},
{gen_server,
call,
[0.11747.125,
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [VOTE] Apache CouchDB 0.11.0 release, first round
On Mon, Mar 22, 2010 at 4:54 PM, Noah Slater nsla...@me.com wrote: Hello, I would like call a vote for the Apache CouchDB 0.11.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/0.11.0/ These artifacts have been built from the 0.11.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/0.11.0/ Happy voting, N Ubuntu 9.10: Linux till-laptop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux All tests successful. Files=33, Tests=456, 46 wallclock secs (17.52 cusr + 2.29 csys = 19.81 CPU) On FreeBSD (6.3): Run `make sudo make install' to install. extremely# make check Making check in bin sed -e s|%ERL%|/usr/local/bin/erl|g -e s|%ICU_CONFIG%|/usr/local/bin/icu-config|g -e s|%bindir%|/usr/local/bin|g -e s|%localerlanglibdir%|/usr/local/lib/couchdb/erlang/lib|g -e s|%defaultini%|default.ini|g -e s|%localini%|local.ini|g -e s|%localconfdir%|/usr/local/etc/couchdb|g -e s|%localstatelogdir%|/usr/local/var/log/couchdb|g -e s|%localstatelibdir%|/usr/local/var/lib/couchdb|g -e s|%localstatedir%|/usr/local/var|g -e s|%bug_uri%|https://issues.apache.org/jira/browse/COUCHDB|g -e s|%package_author_address%|dev@couchdb.apache.org|g -e s|%package_author_name%|The Apache Software Foundation|g -e s|%package_name%|Apache CouchDB|g -e s|%version%|0.11.0|g -e s|%couchdb_command_name%|`echo couchdb | sed 's,x,x,'`|g couchdb Syntax error: end of file unexpected *** Error code 2 Stop in /root/couchdb-0.11.0/bin. *** Error code 1 Stop in /root/couchdb-0.11.0.
Re: [VOTE] Apache CouchDB 0.11.0 release, first round
On Mon, Mar 22, 2010 at 6:52 PM, Noah Slater nsla...@me.com wrote: What PREFIX did you use? We don't support spaces. No PREFIX sir. ;-) ./bootstrap ./configure make check Till What version of make are you using? We require GNU Make, so try again with gmake instead. On 22 Mar 2010, at 17:30, till wrote: On Mon, Mar 22, 2010 at 4:54 PM, Noah Slater nsla...@me.com wrote: Hello, I would like call a vote for the Apache CouchDB 0.11.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/0.11.0/ These artifacts have been built from the 0.11.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/0.11.0/ Happy voting, N Ubuntu 9.10: Linux till-laptop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux All tests successful. Files=33, Tests=456, 46 wallclock secs (17.52 cusr + 2.29 csys = 19.81 CPU) On FreeBSD (6.3): Run `make sudo make install' to install. extremely# make check Making check in bin sed -e s|%ERL%|/usr/local/bin/erl|g -e s|%ICU_CONFIG%|/usr/local/bin/icu-config|g -e s|%bindir%|/usr/local/bin|g -e s|%localerlanglibdir%|/usr/local/lib/couchdb/erlang/lib|g -e s|%defaultini%|default.ini|g -e s|%localini%|local.ini|g -e s|%localconfdir%|/usr/local/etc/couchdb|g -e s|%localstatelogdir%|/usr/local/var/log/couchdb|g -e s|%localstatelibdir%|/usr/local/var/lib/couchdb|g -e s|%localstatedir%|/usr/local/var|g -e s|%bug_uri%|https://issues.apache.org/jira/browse/COUCHDB|g -e s|%package_author_address%|dev@couchdb.apache.org|g -e s|%package_author_name%|The Apache Software Foundation|g -e s|%package_name%|Apache CouchDB|g -e s|%version%|0.11.0|g -e s|%couchdb_command_name%|`echo couchdb | sed 's,x,x,'`|g couchdb Syntax error: end of file unexpected *** Error code 2 Stop in /root/couchdb-0.11.0/bin. *** Error code 1 Stop in /root/couchdb-0.11.0.
Re: [VOTE] Apache CouchDB 0.11.0 release, first round
My gmake is fine, how is your's? =) But what are you referring to? On Mon, Mar 22, 2010 at 7:09 PM, Noah Slater nsla...@me.com wrote: What about gmake? On 22 Mar 2010, at 18:02, till wrote: On Mon, Mar 22, 2010 at 6:52 PM, Noah Slater nsla...@me.com wrote: What PREFIX did you use? We don't support spaces. No PREFIX sir. ;-) ./bootstrap ./configure make check Till What version of make are you using? We require GNU Make, so try again with gmake instead. On 22 Mar 2010, at 17:30, till wrote: On Mon, Mar 22, 2010 at 4:54 PM, Noah Slater nsla...@me.com wrote: Hello, I would like call a vote for the Apache CouchDB 0.11.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/0.11.0/ These artifacts have been built from the 0.11.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/0.11.0/ Happy voting, N Ubuntu 9.10: Linux till-laptop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux All tests successful. Files=33, Tests=456, 46 wallclock secs (17.52 cusr + 2.29 csys = 19.81 CPU) On FreeBSD (6.3): Run `make sudo make install' to install. extremely# make check Making check in bin sed -e s|%ERL%|/usr/local/bin/erl|g -e s|%ICU_CONFIG%|/usr/local/bin/icu-config|g -e s|%bindir%|/usr/local/bin|g -e s|%localerlanglibdir%|/usr/local/lib/couchdb/erlang/lib|g -e s|%defaultini%|default.ini|g -e s|%localini%|local.ini|g -e s|%localconfdir%|/usr/local/etc/couchdb|g -e s|%localstatelogdir%|/usr/local/var/log/couchdb|g -e s|%localstatelibdir%|/usr/local/var/lib/couchdb|g -e s|%localstatedir%|/usr/local/var|g -e s|%bug_uri%|https://issues.apache.org/jira/browse/COUCHDB|g -e s|%package_author_address%|dev@couchdb.apache.org|g -e s|%package_author_name%|The Apache Software Foundation|g -e s|%package_name%|Apache CouchDB|g -e s|%version%|0.11.0|g -e s|%couchdb_command_name%|`echo couchdb | sed 's,x,x,'`|g couchdb Syntax error: end of file unexpected *** Error code 2 Stop in /root/couchdb-0.11.0/bin. *** Error code 1 Stop in /root/couchdb-0.11.0.
Re: [VOTE] Apache CouchDB 0.11.0 release, first round
Ah, just figured! It helps to read _all_ the damn instructions. ;-) All tests successful. Files=33, Tests=456, 44 wallclock secs (20.15 cusr + 3.29 csys = 23.44 CPU) Btw, can I contribute a patch to INSTALL.Unix ? http://friendpaste.com/uwiNQyn5sIZkTcytegy3i On Mon, Mar 22, 2010 at 7:14 PM, Noah Slater nsla...@me.com wrote: What version of make are you using? We require GNU Make, so try again with gmake instead. On 22 Mar 2010, at 18:13, till wrote: My gmake is fine, how is your's? =) But what are you referring to? On Mon, Mar 22, 2010 at 7:09 PM, Noah Slater nsla...@me.com wrote: What about gmake? On 22 Mar 2010, at 18:02, till wrote: On Mon, Mar 22, 2010 at 6:52 PM, Noah Slater nsla...@me.com wrote: What PREFIX did you use? We don't support spaces. No PREFIX sir. ;-) ./bootstrap ./configure make check Till What version of make are you using? We require GNU Make, so try again with gmake instead. On 22 Mar 2010, at 17:30, till wrote: On Mon, Mar 22, 2010 at 4:54 PM, Noah Slater nsla...@me.com wrote: Hello, I would like call a vote for the Apache CouchDB 0.11.0 release, first round. We encourage the whole community to download and test these release artifacts so that any critical issues can be resolved before the release is made. Everyone is free to vote on this release, so get stuck in! We are voting on the following release artifacts: http://people.apache.org/~nslater/dist/0.11.0/ These artifacts have been built from the 0.11.0 tag in Subversion: http://svn.apache.org/repos/asf/couchdb/tags/0.11.0/ Happy voting, N Ubuntu 9.10: Linux till-laptop 2.6.31-20-generic #58-Ubuntu SMP Fri Mar 12 04:38:19 UTC 2010 x86_64 GNU/Linux All tests successful. Files=33, Tests=456, 46 wallclock secs (17.52 cusr + 2.29 csys = 19.81 CPU) On FreeBSD (6.3): Run `make sudo make install' to install. extremely# make check Making check in bin sed -e s|%ERL%|/usr/local/bin/erl|g -e s|%ICU_CONFIG%|/usr/local/bin/icu-config|g -e s|%bindir%|/usr/local/bin|g -e s|%localerlanglibdir%|/usr/local/lib/couchdb/erlang/lib|g -e s|%defaultini%|default.ini|g -e s|%localini%|local.ini|g -e s|%localconfdir%|/usr/local/etc/couchdb|g -e s|%localstatelogdir%|/usr/local/var/log/couchdb|g -e s|%localstatelibdir%|/usr/local/var/lib/couchdb|g -e s|%localstatedir%|/usr/local/var|g -e s|%bug_uri%|https://issues.apache.org/jira/browse/COUCHDB|g -e s|%package_author_address%|dev@couchdb.apache.org|g -e s|%package_author_name%|The Apache Software Foundation|g -e s|%package_name%|Apache CouchDB|g -e s|%version%|0.11.0|g -e s|%couchdb_command_name%|`echo couchdb | sed 's,x,x,'`|g couchdb Syntax error: end of file unexpected *** Error code 2 Stop in /root/couchdb-0.11.0/bin. *** Error code 1 Stop in /root/couchdb-0.11.0.
Re: [VOTE] Apache CouchDB 0.11.0 release, first round
On Mon, Mar 22, 2010 at 7:29 PM, Noah Slater nsla...@me.com wrote: On 22 Mar 2010, at 18:20, till wrote: Ah, just figured! It helps to read _all_ the damn instructions. ;-) All tests successful. Files=33, Tests=456, 44 wallclock secs (20.15 cusr + 3.29 csys = 23.44 CPU) What was the problem? gmake Btw, can I contribute a patch to INSTALL.Unix ? http://friendpaste.com/uwiNQyn5sIZkTcytegy3i Please create a ticket. Will do!
Re: CouchDB Wiki / Documentation
On Sat, Mar 6, 2010 at 4:54 PM, Sebastian Cohnen sebastiancoh...@googlemail.com wrote: On 05.03.2010, at 21:08, Noah Slater wrote: This should be on dev@ I think, so moving there. Please remove user@ from the address in your replies to this message. On 5 Mar 2010, at 19:36, Sebastian Cohnen wrote: but back to topic: MoinMoin sucks! It's unbelievably slow, throws 500s all the time and don't forget the syntax - pure hell when you seriously want to work with it. I've talked with Jan and he has been recently thinking of a replacement. From an old blog post: We were discussing Apache infrastructure, and I was joking about how much I hated JIRA. Robert Newson suggested that having to pick between JIRA and Bugzilla was Hobson's choice, but I countered with Sophie's choice, and his riposte was Morton's fork. When we were cautioned to avoid Buridan's ass, I commented that's what she said! As a first step we want to suggest using Markdown Just use HTML, it is way simpler. and git from now on - at least for documentation purposes Once we (or better I) have enough translated from MoinMoin to Markdown we could start linking from the wiki to Github (as it renders markdown nicely for you). Nice idea, but absolutely not. Official project documentation should be on couchdb.apache.org and the wiki must be on apache infrastructure. Unofficial stuff, like our O'Reilly book, is fine elsewhere, but that's all it can be - as far as I understand the situation. We think that this approach is likely to work best as an interim solution before we have a ass-kickin' couch-wiki solution. Once that's done, we can easily import the markdown stuff. or maybe markdown+git works so well, so that it stays the preferred way - who knows? ;) Avoid Markdown! It solves nothing and introduces problems. hmm, I personally like markdown. It's simple to read/write and easy to parse. Writing HTML is much more painful and without strict conventions you get very messy code. +1 This is only a suggestion and we really want your opinion. I think the rudimental requirements are quite clear: * a faster and more reliable system * very easy to contribute * easy and easy to learn syntax * being able to work offline (at least for me that would be awesome) * easy way to do some QA Whatever we choose must run on ASF infrastructure if it is to be considered official. I think you misunderstood me on this point. I didn't want to suggest making Github the new place for official documentation. I see git(hub) more like a working platform. Static HTML export could be placed on couchdb.apache.org/docs or where ever you like. +1 I think this sounds pretty good and as someone earlier said, if you want to create a toolchain and get people to contribute. That's awesome. I'd help out with content as well, if someone checks my gibberish Engrish. Generaly, I think another wiki would be nice. I'm missing structure right now and clarity. I don't know if we can get this going with moin-moin. But I don't know which other wiki would be better, as (no offense to the wiki overlords) all seem to suck in one way or another. Sometimes I'm thinking even docbook would be nice. :) All in all, I'd like CouchDB move into the direction of docs.php.net. The most awesome part are the comments and a nifty little switch (for admins/official contributors/developers) to transform a comment into a docbug to either fix an example/paragraph or extend it with valuable info provided through the comment system. Till
moving couchdb
Hey, so in the past I was able to move CouchDB, let's say from /foo to /bar - had to update a bunch of scripts (fgrep -r '/foo/' *) to reflect the new path, but that was it. Now, since we started using Erlang views, we can't do that anymore. We kept getting an os error and I ended up symlinking /foo to /bar to fix it. Should I open an issue on Jira for that? Crash: http://friendpaste.com/7ZvuosG2uZM7QZTKOMQ29A Till
Re: Releasing 0.11, Request for Comments
I always knew secretly open source worked like that. ;) Btw, I know it's not so subtle, but you need to include your paypal email... :D http://www.youtube.com/watch?v=Ui86peQZ74s On Fri, Feb 26, 2010 at 3:26 PM, Noah Slater nsla...@tumbolia.org wrote: For the list's benefit, Randall sent me $2 via PayPal, suggesting I buy a candy bar. Thanks Randall, I may unofficially call this the Randall release. Kinda got a ring to it, that. If anyone else wants to sponsor the release, you know what to do. On 25 Feb 2010, at 20:25, Noah Slater wrote: Send $1 to nsla...@tumbolia.org and I will cut it. On 25 Feb 2010, at 20:13, Randall Leeds wrote: +1 Cut it! On Feb 25, 2010 12:08 PM, Paul Davis paul.joseph.da...@gmail.com wrote: So really all of the patches brought up in the last few hours are good candidates for 1.0. +1
Re: CouchDB defaults
Ping? Just wondering what happened or what the consensus was. :D Till
CouchDB defaults
Hey guys, when I install couchdb e.g. on ubuntu, it creates a couple settings in /etc/default/couchdb. I was wondering what you guys think about adding ./configure switches for each one of them (COUCHDB_USER, COUCHDB_STDOUT_FILE, COUCHDB_STDERR_FILE, COUCHDB_RESPAWN_TIMEOUT)? =) It sure would make my life even easier. :D Thoughs? Till
Re: CouchDB defaults
On Thu, Feb 4, 2010 at 5:10 PM, Dirkjan Ochtman djc.ocht...@gmail.com wrote: On Thu, Feb 4, 2010 at 17:06, till klimp...@gmail.com wrote: when I install couchdb e.g. on ubuntu, it creates a couple settings in /etc/default/couchdb. I was wondering what you guys think about adding ./configure switches for each one of them (COUCHDB_USER, COUCHDB_STDOUT_FILE, COUCHDB_STDERR_FILE, COUCHDB_RESPAWN_TIMEOUT)? =) With my Gentoo packaging hat on, +1. Also, COUCHDB_PID_FILE. +1 to that. ;) Till Cheers, Dirkjan
Re: CouchDB defaults
On Thu, Feb 4, 2010 at 5:51 PM, Paul Davis paul.joseph.da...@gmail.com wrote: Thoughts Noah? I don't immediately see anything wrong with this, but I don't know if other packager people have different expectations. Can't speak for everyone, but even when I roll a new port on freebsd, this would come in handy. ;) My ubuntu stuff is primarily me automating stuff on ec2 instances where as little manual configuration is key. And if this means a couple switches allow me to skip on post-processing my installs through another script, I'm game. :D Till
Re: CouchDB defaults
Hey Noah, anything I can do to clear this up, or better explain what I (or well, we want)? Here's a rundown: ./configure --couchdb-user=root \ --couchdb-stdout-file=/my/log/file/for/stdout \ --couchdb-stderr-file=/my/log/file/for/stderr \ --couchdb-respawn-timeout=10 \ --couchdb-pidfile=/home/till/noah.pid ... essentially, this would populate /etc/defaults/couchdb. Till On Thu, Feb 4, 2010 at 7:30 PM, Noah Slater nsla...@tumbolia.org wrote: I'm unsure. Would he accept a patch for ./configure that set default values in local.ini too? On 4 Feb 2010, at 16:51, Paul Davis wrote: Thoughts Noah? I don't immediately see anything wrong with this, but I don't know if other packager people have different expectations. On Thu, Feb 4, 2010 at 11:06 AM, till klimp...@gmail.com wrote: Hey guys, when I install couchdb e.g. on ubuntu, it creates a couple settings in /etc/default/couchdb. I was wondering what you guys think about adding ./configure switches for each one of them (COUCHDB_USER, COUCHDB_STDOUT_FILE, COUCHDB_STDERR_FILE, COUCHDB_RESPAWN_TIMEOUT)? =) It sure would make my life even easier. :D Thoughs? Till
Re: CouchDB defaults
On Thu, Feb 4, 2010 at 9:03 PM, Noah Slater nsla...@tumbolia.org wrote: Nope, I understand what you want, I just don't know if it's a good idea. So my thought experiment was to wonder if we'd do the same for the other configuration files. As in, where is the line drawn? IMHO, there doesn't have to be a line drawn anywhere. If people request more options, why not provide them? Unless there's a good reason not to. These kind of switches make packing a lot easier and provide more flexibility to anyone who runs CouchDB from source. Take a look at ./configure --help from a MySQL source download, or Apache. Plenty of options to choose from. :) Till
Re: problem with two key ranges in couchdb
Hey Duane,
On Sun, Jan 3, 2010 at 2:57 PM, Duane Almond Sto. Tomas
dua...@gmail.com wrote:
Is there other way? because geocouch does not support PHP language and PHP
will be the language of my project.
There's a view server written in PHP, it's part of the Sopha (a
CouchDB access wrapper):
http://github.com/shevron/sopha
I haven't tried it yet, but it might give you something to play with/extend.
Till
On Sat, Jan 2, 2010 at 10:22 AM, Chris Anderson jch...@apache.org wrote:
On Sat, Jan 2, 2010 at 5:41 AM, Duane Almond Sto. Tomas
dua...@gmail.com wrote:
I'm having problem getting the right results in my coordinate system.
To explain my system, I have this simple database that have x_axis,
y_axis
and name columns. I don't need to get all the data, I just need to
display
some part of it.
The fundamental problem is that CouchDB indexes are 1-dimensional.
Essentially a sorted list. You can pull out every point between 2
lines of longitude. You can pull out every point between 2 lines of
latitude.
But when you need points within a bounding box, you have to pull out
all of the above, and intersect them in your application. (There are
some optimizations you do, but fundamentally, this is the issue.)
This general problem is addressed with geo indexers. You might want to
take a look at this one for Couch:
http://vmx.cx/cgi-bin/blog/index.cgi/geocouch-new-release-0.10.0:2009-09-19:en,CouchDB,Python,geo
Chris
For example, I have a coordinate system that have 10:10(meaning from
x_axis
-10 to 10 and from y_axis -10 to 10) and I want to display only 49
coordinates. In sql query I can do it something like this:
select * from coordinate where x_axis = -3 and x_axis = 3 and y_axis
=
-3 y_axis = 3
I tried this function but no success:
by_range: {
map: function(doc) { emit([doc.x_axis, doc.y_axis], doc) }
}
by_range?startkey=[-3,-3]endkey=[3,3]
I got a wrong results of:
-3x-3
-3x-2
-3x-1
-3x0
-3x1
-3x2
-3x3
-- should not display this part --
-3x4
-3x5
-3x6
-3x7
-3x8
-3x9
-3x10
-- end of should not display this part --
. up to 3x3
to give you a better understanding of my project here is the screenshot
of
that I want to be made:
http://img96.imageshack.us/img96/5382/coordinates.jpg
--
I wanted a perfect ending.
Now I've learned, the hard way, that some poems don't rhyme, and some
stories don't have a clear beginning, middle, and end.
Life is about not knowing, having to change, taking the moment and making
the best of it, without knowing what's going to happen next..Farewell
Team !
Duane Almond C. Sto. Tomas
09062772487
OOiP Manila
personal websites:
http://duasto.freehostia.com/
http://duanealmond.com/
--
Chris Anderson
http://jchrisa.net
http://couch.io
--
I wanted a perfect ending.
Now I've learned, the hard way, that some poems don't rhyme, and some
stories don't have a clear beginning, middle, and end.
Life is about not knowing, having to change, taking the moment and making
the best of it, without knowing what's going to happen next..Farewell
Team !
Duane Almond C. Sto. Tomas
09062772487
OOiP Manila
personal websites:
http://duasto.freehostia.com/
http://duanealmond.com/
View re-building from 0.9.1 to 0.10.0
Hey guys, I've tested this a couple times with smaller database and so far, I always had to rebuild my views when I updated a server from 0.9.x to 0.10.0. And I also had that confirmed (by some of you). ;-) Now my problem is the following -- last time I build the view on the database, it took a week to finish, literally 7.5 days. The view code itself is pretty simple, but the database contains a 160,000,000 documents and totals to ~200 GB in size. With a set of this magnitude, I'd like to avoid another week. I'd even like to avoid 3-4 days (even though I'm a fan, I don't think it's twice as fast). So my question is if there is *any* way to avoid view rebuilding and still updating to 0.10.x. Thanks for listening, Till
[jira] Commented: (COUCHDB-41) Differentiate between not existent database and not existant document in response on 404
[
https://issues.apache.org/jira/browse/COUCHDB-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12675450#action_12675450
]
Till Klampaeckel commented on COUCHDB-41:
-
I'd like more obvious error messages:
Document not found.
Database does not exist.
Differentiate between not existent database and not existant document in
response on 404
Key: COUCHDB-41
URL: https://issues.apache.org/jira/browse/COUCHDB-41
Project: CouchDB
Issue Type: Improvement
Components: HTTP Interface
Environment: CouchDB 0.7.2
Reporter: Kore Nordmann
Assignee: Jan Lehnardt
Priority: Minor
Currently it is not possible to know from a request on a not existent
document in the database, if the database does not exist, or if it is just
the document which is missing.
It would be nice to have this information in the response JSON structure, so
that the application using the CouchDB could handle such errors more
gracefully. An extract from a CouchDB interaction showing the problem:
== Ensure database is absent
DELETE /test HTTP/1.0
Host: localhost
HTTP/1.0 404 Object Not Found
Server: inets/develop
Date: Tue, 15 Apr 2008 20:54:20 GMT
Cache-Control: no-cache
Pragma: no-cache
Expires: Tue, 15 Apr 2008 20:54:20 GMT
Connection: close
Content-Type: text/plain;charset=utf-8
{error:not_found,reason:missing}
== Try GET on absent database
GET /test/not_existant HTTP/1.0
Host: localhost
HTTP/1.0 404 Object Not Found
Server: inets/develop
Date: Tue, 15 Apr 2008 20:54:20 GMT
Cache-Control: no-cache
Pragma: no-cache
Expires: Tue, 15 Apr 2008 20:54:20 GMT
Connection: close
Content-Type: text/plain;charset=utf-8
{error:not_found,reason:missing}
== Create database, but not the document
PUT /test HTTP/1.0
Host: localhost
HTTP/1.0 201 Created
Server: inets/develop
Date: Tue, 15 Apr 2008 20:54:20 GMT
Cache-Control: no-cache
Pragma: no-cache
Expires: Tue, 15 Apr 2008 20:54:20 GMT
Connection: close
Content-Type: text/plain;charset=utf-8
{ok:true}
== Try to fetch document again
GET /test/not_existant HTTP/1.0
Host: localhost
HTTP/1.0 404 Object Not Found
Server: inets/develop
Date: Tue, 15 Apr 2008 20:54:20 GMT
Cache-Control: no-cache
Pragma: no-cache
Expires: Tue, 15 Apr 2008 20:54:20 GMT
Connection: close
Content-Type: text/plain;charset=utf-8
{error:not_found,reason:missing}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
