Mayya Sharipova | 23 Jun 18:59 2016
Picon

Re: Pluggable Storage Engine API

Hi Paul,
continuing our discussion here. You said that I need to configure the engine I open in the tests:
{ok, Db} = couch_db:open_int(DbName, []),
#db{    
     engine = {Engine, St}
} = Db,

What do you mean by configuration?  Is it the initialization you did in your tests:
{ok, Engine, St1} = test_engine_util:init_engine(),
https://github.com/cloudant/couchdb-couch/blob/45918-pluggable-storage-engines/src/test_engine_purge_docs.erl#L22

If by configuration we mean initialization, I guess the engine gets initialized while we are opening a db:
couch_db:open_int(DbName, []),   
in couch_db_updater:
{ok, EngineState} = couch_db_engine:init(Engine, FilePath, Options).
https://github.com/cloudant/couchdb-couch/blob/45918-pluggable-storage-engines/src/couch_db_updater.erl#L29

Jenn Turner | 23 Jun 16:54 2016

[NEWS] The CouchDB weekly news for June 23 is out!

Happy Thursday!

The CouchDB weekly news is now live at: https://blog.couchdb.org/2016/06/23
/couchdb-weekly-news-june-23-2016/

Highlights include CouchDB being the news today, progress for PouchDB, and
some oddly soothing internet moments just for you!

Thanks to Joan for submitting content for this week :D

You can help us spread the news by sharing on Twitter
(https://twitter.com/CouchDB/status/745992333926240257) and other social
networks.

Also if you have news for next week, just REPLY to this thread!

Cheers!  

Jenn Turner

The Neighbourhoodie Software GmbH  
Adalbertstr. 7-8, 10999 Berlin  
[neighbourhood.ie](https://link.nylas.com/link/c4yg26doe3du1m7gpdgdrj1jp
/local-fa1a903a-
aeef/0?redirect=http%3A%2F%2Fneighbourhood.ie%2F&r=ZGV2QGNvdWNoZGIuYXBhY2hlLm9yZw==
"http://neighbourhood.ie/" )  

Handelsregister HRB 157851 B Amtsgericht Charlottenburg  
Geschäftsführung: Jan Lehnardt

(Continue reading)

Paul Hammant | 23 Jun 15:31 2016

154 million voter records

It's in the news today. Multiple news sites incl. slashdot.

Someone deployed couchdb on its default port - 5984 or w/o a strong ssl & auth design.  Maybe.

Sent from my iPhone
Ilya Khlopotov | 18 Jun 01:07 2016
Picon

Extra reference in a commit message


Hello,

We at Cloudant using our own bug tracker. Quite often we have two tickets
opened for the same problem.
One ticket is in ASF JIRA and another one in our internal bug tracker.
We have some automation, which compiles the issues we worked on in a
current release cycle.
However, it is extremely challenging to get it working right. Since it
needs to consult two independent trackers with no link between them.
We are considering adding a second reference in a commit message.

Does anyone have a strong opinion against it?
Would these unrelated references be too annoying for the community?

Best regards,
ILYA Khlopotov
Joan Touzet | 17 Jun 22:48 2016
Picon

2.0 & Windows: status update

Hello everyone,

I'd like to update the community on the status of the 2.0 port to Microsoft Windows. There are three parts to
this email: the build tools/chain themselves, support in CouchDB for the Windows build process, and
testing results. I'll cover them in that order.

-Joan

Build Tools/Chain
=================
** TL;DR: New glazier repo to join couchdb, contains scripts and README to build CouchDB 2.0 on Windows.

Our work to date has been going on in Dave Cottlehuber's glazier repository at 

  https://github.com/dch/glazier/tree/release/couchdb_2.0

The reason for the extra repository is that the Windows build process is *very* ugly, involving 3 distinct
build chains (Visual Studio, Cygwin and the Mozilla Build system) to build all of the necessary
prerequisites. The repository includes a number of support scripts to set up that environment, a README
with a detailed walkthrough, and some patches necessary to the prerequisites to get them to build under
the modern Windows b uild system.

Parenthetically, it _is_ possible to use binary installs for the prerequisites (OpenSSL, libcurl,
Erlang, SM 1.8.5), but Dave, Nick North and I have evolved the glazier system over a number of years and it's
proven quite effective. Plus, we don't have to worry about the provenance of any of the binaries since we
build everything from source directly, and that's important when we put up an unofficial Windows build
for download at https://couchdb.apache.org/ .

Good news: as of today I've requested and Infra has created a new apache couchdb-glazier repo, and it's my
intent to mirror dch/glazier over into the ASF's repo once things have stabilized a bit more (PR and merge
(Continue reading)

Robert Samuel Newson | 17 Jun 01:24 2016
Picon
Gravatar

[ANNOUNCE] Nick Vatamaniuc elected as CouchDB committer

Dear community,

I am pleased to announce that the CouchDB Project Management Committee has elected Nick Vatamaniuc as a
CouchDB committer.

    Apache ID: vatamane

    IRC nick: vatamane

Committers are given a binding vote in certain project decisions, as well as write access to public project infrastructure.

This election was made in recognition of Nick's commitment to the project. We mean this in the sense of being
loyal to the project and its interests.

Please join me in extending a warm welcome to Nick!

On behalf of the CouchDB PMC,

Robert Samuel Newson

Jenn Turner | 16 Jun 18:14 2016

[NEWS] The CouchDB weekly news for June 16 is out!

Happy Thursday!

The CouchDB weekly news is now live at: https://blog.couchdb.org/2016/06/16
/couchdb-weekly-news-june-16-2016/

Highlights include a hot-off the presses PouchDB release, Nolan Lawson on a
recent podcast, plus relaxing with trees!

You can help us spread the news by sharing on Twitter
([https://twitter.com/CouchDB/status/743475772212584448](https://link.nylas.com/link/c4yg26doe3du1m7gpdgdrj1jp
/local-2c3de2bb-
ac13/0?redirect=https%3A%2F%2Ftwitter.com%2FCouchDB%2Fstatus%2F738457387787522048&r=ZGV2QGNvdWNoZGIuYXBhY2hlLm9yZw==
"https://twitter.com/CouchDB/status/738457387787522048" )) and other social
networks.  

Also **if you have news for next week**, just REPLY to this thread!

Cheers!  

Jenn Turner

The Neighbourhoodie Software GmbH  
Adalbertstr. 7-8, 10999 Berlin  
[neighbourhood.ie](https://link.nylas.com/link/c4yg26doe3du1m7gpdgdrj1jp
/local-2c3de2bb-
ac13/1?redirect=http%3A%2F%2Fneighbourhood.ie%2F&r=ZGV2QGNvdWNoZGIuYXBhY2hlLm9yZw==
"http://neighbourhood.ie/" )  

Handelsregister HRB 157851 B Amtsgericht Charlottenburg  
Geschäftsführung: Jan Lehnardt
(Continue reading)

Jenn Turner | 9 Jun 18:01 2016

[NEWS] The CouchDB weekly news for June 9 is out!

Happy Thursday!

The CouchDB weekly news is now live at: <https://blog.couchdb.org/2016/06/09
/couchdb-weekly-news-june-9-2016/>

Highlights include a metric tonne of new releases for PouchDB, some great use
cases, and squeaky pizza!

You can help us spread the news by sharing on Twitter ([https://twitter.com/Co
uchDB/status/740936151675076608](https://twitter.com/CouchDB/status/7384573877
87522048 "https://twitter.com/CouchDB/status/738457387787522048" )) and other
social networks.  

Also if you have news for next week, just REPLY to this thread!

Cheers!  

Jenn Turner

The Neighbourhoodie Software GmbH  
Adalbertstr. 7-8, 10999 Berlin  
[neighbourhood.ie](http://neighbourhood.ie/ "http://neighbourhood.ie/" )  

Handelsregister HRB 157851 B Amtsgericht Charlottenburg  
Geschäftsführung: Jan Lehnardt

Paul Davis | 7 Jun 23:43 2016
Picon

Pluggable Storage Engine API

Hi everyone!

So I've been working on designing and implementing a pluggable storage
engine API for CouchDB and I've finally gotten things far enough along
that I can start asking for feedback on the design.

The motivation for this work is two fold. First, the obvious benefit
is that developers can start working on using alternative storage
technologies to try and improve overall performance (ie, Riak's
pluggable storage backends [1]). Secondly, adding an internal storage
engine API should hopefully give us a better ability to separate
testing at functional levels (more on this below).

The majority of this work is on a branch [2] of the couchdb-couch
repository. There are four major commits related to this work:

   1. Define the API [3]
   2. Implement the legacy engine using this API [4]
   3. Add the implementation to use the API [5]
   4. Adding a reusable test suite [6]

I ended up taking this approach so that I could hopefully split up the
major tasks involved so that others would be able to review the
changes more easily. However it does result in a lot of copying of
code between the second and third commit as it involves moving a lot
of the legacy storage engine code around between commits so nothing is
broken after each commit. Hopefully that makes sense.

There are also branches on the main couchdb repo [7] (mostly for
pointing at the storage engine branches) as well as chttpd [8],
(Continue reading)

rnewson | 6 Jun 23:12 2016
Picon
Gravatar

admin commit: updated refs/heads/master to 01ce448

Repository: couchdb-admin
Updated Branches:
  refs/heads/master c641ad202 -> 01ce44893

fix typo

Project: http://git-wip-us.apache.org/repos/asf/couchdb-admin/repo
Commit: http://git-wip-us.apache.org/repos/asf/couchdb-admin/commit/01ce4489
Tree: http://git-wip-us.apache.org/repos/asf/couchdb-admin/tree/01ce4489
Diff: http://git-wip-us.apache.org/repos/asf/couchdb-admin/diff/01ce4489

Branch: refs/heads/master
Commit: 01ce44893b574913d4736e8c27c20e6cbef8affc
Parents: c641ad2
Author: Robert Newson <rnewson@...>
Authored: Mon Jun 6 22:10:54 2016 +0100
Committer: Robert Newson <rnewson@...>
Committed: Mon Jun 6 22:10:54 2016 +0100

----------------------------------------------------------------------
 email/vote_committer.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------

http://git-wip-us.apache.org/repos/asf/couchdb-admin/blob/01ce4489/email/vote_committer.txt
----------------------------------------------------------------------
diff --git a/email/vote_committer.txt b/email/vote_committer.txt
index b2523a0..786ee56 100644
--- a/email/vote_committer.txt
+++ b/email/vote_committer.txt
(Continue reading)

Ben Keen | 3 Jun 16:11 2016
Picon
Gravatar

_replicate vs. _replicator

Hey!

Wonder if I could get some advice here. I’ve been working on refactoring
the replication feature in Fauxton to POST to the /_replicator database
rather than using /_replicate.

Having all replications (continuous/one-offs) logged in one place (the
_replicator database) leaves a nice paper trail of replication history.
[N.B. I’ve been speaking to Markus Fischboeck, who’s doing work on adding
some advanced replication features - we’re working in parallel].

I’ve been able to get replications working, but it requires passing both
basic headers in the POSTed JSON content, and the creds in the actual
endpoint URL, like so:

http://bob:bobspassword-ly82jI7wicnYFliJT8bUbw <at> public.gmane.org:8000/_replicator

It’s the latter that particularly worries me. I don’t believe this is
secure over http (correct?), and since Fauxton could be run anywhere, I
 wanted to know if I should stop heading down this road and stick with
_replicate.

Thanks!

Ben

Gmane