On Apr 30, 2012, at 1:57 PM, Jan Lehnardt wrote:
>
> On Apr 30, 2012, at 18:54 , Jan Lehnardt wrote:
>
>> Paul pointed out on IRC that the branch I pushed has Brian as committer
>> *and* author, which we can't have. I'll look into it.
>
> please ignore this email.
Of course I defer to Paul on
On Aug 23, 2012, at 8:27 AM, Dave Cottlehuber wrote:
> Hi everybody,
>
> Due to the size of this welcome contribution, we need a bit more
> paperwork than usual, which Jan is handling, and also a vote accepting
> the contribution which can be done prior.
>
> I would like call a vote for includin
No objection from me, Jan. I don't see the need for a dedicated "develop"
branch at the moment, but then I've not worked intensively on a project which
had one.
Adam
On Oct 31, 2012, at 10:40 AM, Jan Lehnardt wrote:
>
> On Oct 31, 2012, at 13:21 , Robert Newson wrote:
>
>> For my part, I
A minor thing -- didn't we just propose earlier today to use a naming
convention like 431-feature-CORS for these topic branches?
Adam
On Oct 31, 2012, at 7:43 PM, beno...@apache.org wrote:
> Updated Branches:
> refs/heads/COUCHDB-431_cors [created] 0777262fa
>
>
> handle CORS. fix #COUCHDB-4
M, Benoit Chesneau wrote:
> hr i thought it was ticketnumber_shortdescr I didn't read last
> update of the wiki though ..
>
> - benoît
>
>
> On Thu, Nov 1, 2012 at 12:50 AM, Adam Kocoloski wrote:
>
>> A minor thing -- didn't we just propose ea
Hi, I mentioned in IRC earlier today that I'd really like to see us organize
our source code so that OTP applications are wholly contained in their own
subdirectories and are organized according to the standard OTP application
layout. In a world where we've refactored the monolithic 'couch' app
30 AM, Benoit Chesneau wrote:
> The branch have been renamed to 431_cors. I'm not sure it will be renamed
> on github too.
>
> - benoit
>
>
> On Thu, Nov 1, 2012 at 5:34 AM, Paul Davis wrote:
>
>> On Wed, Oct 31, 2012 at 8:14 PM, Adam Kocoloski
>> wro
On Nov 1, 2012, at 1:41 AM, Benoit Chesneau wrote:
> ok I will stop for now pushed 431_feature_cors (the removing of caps is
> wanted here and I will be happy to just update the jira title if someone
> really care) .
Sure, I only used caps because CORS is an acronym. It doesn't matter at all.
reall standalone Erlang applications that could be embedded in others
>> projects.
>>
>>
>> @davisp about the use of rebar vs autotools, I discussed it on a previous
>> mail but we could probably have the following scenatio:
>>
>> a bootstrap script building:
Wow, nice work Jan.
On Nov 1, 2012, at 8:16 AM, Jan Lehnardt wrote:
> Hey all,
>
> we had a request on the erlang@c.a.o list to explain top to bottom what it
> means to write a document.
>
> I gave it a shot. I thought the non-core dev readers here would enjoy the
> tour:
>
>
> http://m
Hi Eli, Benoit linked to a variant of it in the beginning of this thread.
There's a lot to like about it, and most of it is very similar to the workflow
we're converging on in this project. The big difference is that in git-flow
the HEAD of "master" is always the latest tagged release, and tha
On Nov 1, 2012, at 11:29 PM, Eli Stevens (Gmail) wrote:
> On Thu, Nov 1, 2012 at 9:28 PM, Adam Kocoloski wrote:
>> Hi Eli, Benoit linked to a variant of it in the beginning of this thread.
>> There's a lot to like about it, and most of it is very similar to the
>>
On Nov 2, 2012, at 2:47 PM, Randall Leeds wrote:
> On Fri, Nov 2, 2012 at 6:50 AM, Robert Newson wrote:
>
>> Sure, and it couldn't hurt to clarify how we should use git in these
>> circumstances. The principal rule is that each commit should be
>> self-contained and, further, that it should at
+1
On Nov 30, 2012, at 11:05 AM, Jan Lehnardt wrote:
> Hey all,
>
> The SpiderMonkey folks are slowly retiring* E4X. Since it is
> an advertised feature of CouchDB, we should be proactive
> about this. I’d like the 1.3.0 release notes to include a
> note about E4X support being deprecated an
Certainly fine for me.
On Dec 4, 2012, at 2:01 PM, Dave Cottlehuber wrote:
> Hi everybody,
>
> We'll have another meeting on IRC tomorrow.
>
> Re timings: would alternating a couple of times a month with
> http://everytimezone.com/#2012-12-4,150,6be i.e. afternoon for Europe,
> morning for Eas
+1
On Feb 6, 2013, at 5:00 PM, Paul Davis wrote:
> +1
>
> On Wed, Feb 6, 2013 at 4:00 PM, Robert Newson wrote:
>> +1
>>
>> On 6 February 2013 21:58, Norman Barker wrote:
>>> +1
>>>
>>> On Wed, Feb 6, 2013 at 2:55 PM, Michael Wallace
>>> wrote:
+1
On Wed, Feb 6, 2013 a
+1
On Feb 6, 2013, at 5:00 PM, Paul Davis wrote:
> +1
>
> On Wed, Feb 6, 2013 at 4:00 PM, Robert Newson wrote:
>> +1
>>
>> On 6 February 2013 21:58, Norman Barker wrote:
>>> +1
>>>
>>> On Wed, Feb 6, 2013 at 2:55 PM, Michael Wallace
>>> wrote:
+1
On Wed, Feb 6, 2013 a
Wow, thanks for the detailed report and patch Ben. Cheers,
Adam
On Mar 12, 2013, at 8:11 PM, Ben Reser wrote:
> Friend of mine was trying to build couchdb today and ran into a problem.
>
> [[[
> checking jsapi.h usability... no
> checking jsapi.h presence... no
> checking for jsapi.h... no
>
On Mar 15, 2013, at 7:16 PM, Noah Slater wrote:
> You do not have to respond if you think this is a good idea. In 72 hours I
> will assume lazy consensus.
Hope you don't mind if I respond anyway.
+1
I'd prefer to keep a 72 hour window for lazy consensus.
Adam
On May 7, 2013, at 3:23 PM, Robert Newson wrote:
> I'm not sure I fully agree. All the lazy consensus's of late have had
> a 72 hour window on them which is the same duration we use for couchdb
> releases.
>
> However, we can discuss
Cool!
It's heavy on the taxonomy of tags for my tastes, but that's ok. I definitely
like the walkthrough of user -> developer -> committer and beyond, and the list
of teams is a good nudge to encourage contributions.
I'm not sure there's much of a point to a [GENERAL] team/tag, and the
descri
On May 22, 2013, at 2:51 PM, Dave Cottlehuber wrote:
> On 22 May 2013 18:11, Noah Slater wrote:
>> +1 on moving RPM/DEB meta data into the main source tree. (Jan, these tools
>> expect specific top level dirs/files, but they're usually self-contained.
>> As you say, we can change things if it ge
On May 24, 2013, at 9:20 AM, Denny Trebbin wrote:
> Hi,
>
> I try to step out of the dark and turn from silent into speaker mode ;-)
Awesome.
> Recently http://elixir-lang.org/ has gotten some love and support by Dave
> Thomas via his book http://pragprog.com/book/elixir/programming-elixir and
On May 27, 2013, at 11:42 AM, Robert Newson wrote:
> 1) That we adopt the git commit message guidelines above.
+1. Consistent, well-written, thorough commit messages are one of the better
gifts we can give to future developers of CouchDB.
> 2) That we delete NEWS/CHANGES from master before th
On May 27, 2013, at 12:18 PM, Dirkjan Ochtman wrote:
> 4abe8cd9 - Merge remote-tracking branch
> 'ocasta/1799-rewrite-session-cookie-fix'
> Adam, does it make sense to merge it? Can you?
Done (well, I cherry-picked ocasta's commit onto 1.3.x).
Adam
Hi Pavan!
In my opinion COUCHDB-1735 is superseded by COUCHDB-1736. If we have an
aliasing system then a rename can be something like an alias creation and
deletion.
In the description on COUCHDB-1735 Dave mentions that the BigCouch code may
complicate this feature addition. I'm biased, but
; is very difficult to implement.
>
> Also, your thoughts on https://issues.apache.org/jira/browse/COUCHDB-1751 ?
>
> I believe giving some stats to third party application like Graphite etc,.?
>
>
> On Wed, May 29, 2013 at 9:05 PM, Adam Kocoloski wrote:
>
>> Hi Pava
l go forward with this
> implementation as Dave suggested.
>
> I will send the proposal to the group by tomorrow or day after max. Do take
> a look and suggest changes :)
>
> I'm very excited about contributing.
>
> Thanks Adam :)
>
>
> On Wed, May 29, 2013 at 9:48 P
On May 29, 2013, at 12:31 PM, Pavan Sudheendra wrote:
> Any idea on what metrics should be collected? The phrase 'Measure All the
> Things.' given in the descriptions section of the bug is pretty vague i
> feel.
The existing couch_stats system collects a number of metrics already. I think
the
As the author of one of those replicator UA-sniffing compatibility hacks I
definitely think a system for advertising capabilities is a Good Idea :)
Adam
On Jun 4, 2013, at 6:40 PM, Joan Touzet wrote:
> Today, if I GET http://localhost:5984/ , I get:
>
>
> {"couchdb":"Welcome","uuid":"b1b1db
On Jun 21, 2013, at 7:58 AM, Jan Lehnardt wrote:
>> Step two is build out a proper interface around the _replicator
>> database, allowing you to create new persistent replications,
>> introspect existing replications, look at historic replications, and
>> also to visually expose the powerful adva
On Jun 21, 2013, at 10:07 AM, Jan Lehnardt wrote:
>
> On Jun 21, 2013, at 15:35 , Jan Lehnardt wrote:
>
>>
>> On Jun 21, 2013, at 14:16 , Adam Kocoloski wrote:
>>
>>> On Jun 21, 2013, at 7:58 AM, Jan Lehnardt wrote:
>>>
>>>
+1, nice writeup Benoit.
On Jun 25, 2013, at 4:24 PM, Noah Slater wrote:
> +1!
>
>
> On 25 June 2013 17:43, Benoit Chesneau wrote:
>
>> Hi All,
>>
>> I propose to merge rcouch (http://rcouch,org) in the official Apache
>> CouchDB repository to a new branch (i.e, *not* master). Once there, t
Agreed. Thanks a bunch Alexander,
Adam
On Jul 2, 2013, at 3:39 PM, Joan Touzet wrote:
> Still a job well done! \o/
>
> On Tue, Jul 02, 2013 at 07:29:17PM +0400, Alexander Shorin wrote:
>> Hey! Thanks (:
>>
>> But cleanup procedure isn't finished on these reports: there is still
>> need to de
I'm interested. My travel schedule in early December is pretty open at the
moment.
Adam
On Sep 27, 2013, at 12:51 PM, Dave Cottlehuber wrote:
> Hi everybody,
>
> Is there interest in having a hackathon again in late November or early
> December?
>
> Ideally we'd focus this on something spe
Ah, I've been sitting on a fairly significant fix for retries of attachment
transfers during replication. Would love to see if I can sneak that in. I'll
make it a priority as soon as I have a couple of minutes today.
Adam
On Oct 2, 2013, at 5:03 AM, Dirkjan Ochtman wrote:
> Hi all,
>
> I'm
https://issues.apache.org/jira/browse/COUCHDB-1901
Adam
On Oct 2, 2013, at 9:14 AM, Dirkjan Ochtman wrote:
> On Wed, Oct 2, 2013 at 3:11 PM, Adam Kocoloski
> wrote:
>> Ah, I've been sitting on a fairly significant fix for retries of attachment
>> transfers during rep
I'm fairly happy with the state of this branch, but I realize it's a
last-second thing so wanted to solicit some feedback.
The PR description and commit messages contain most of the details. The gist
is that the replicator needs to treat streaming multipart requests+responses
specially when it
I'm with Jason on this one, but won't stand in the way if others want to move
forward on the proposal.
Adam
On Dec 4, 2013, at 11:24 AM, Jason Smith wrote:
> -1
>
> We do this at Nodejitsu and I find it tedious and unhelpful. It's a bit of
> ceremony with little benefit. For me at least, I ne
On Dec 10, 2013, at 12:30 PM, Jan Lehnardt wrote:
> Heya Adam,
>
> I found this on IRC:
>
> [Thu 23:43] dch: yeah i recommend a small worker_batch_size for
> docs with attachments for other reasons
>
> Could you elaborate on the other reasons? :)
>
> Best
> Jan
> --
Sure:
* The entire b
I would love to see a smarter solution here that avoids the need for Cloudant
to fork {rexi, fabric, mem3} just to add instrumentation.
Adam
> On Dec 19, 2013, at 1:21 PM, rnew...@apache.org wrote:
>
> Updated Branches:
> refs/heads/1843-feature-bigcouch fee7cbfc4 -> d260381c1
>
>
> Remove r
ks to the point where databases can
>> be created, but doc creation crashes. I’m sure it’s simple but I’ve not had
>> time to fix it.
>>
>> B.
>>
>>> On 20 Dec 2013, at 22:02, Adam Kocoloski wrote:
>>>
>>> I would love to see a
On Jan 14, 2014, at 3:22 PM, Paul Davis wrote:
> I'd like to propose that we move to having a repository for each
> application/dependency that we use to build CouchDB. Each repository would be
> hosted on ASF infra and mirrored to GitHub as expected.
Good idea. It's going to be an annoyance
Thanks Paul! Good call on starting with the import branch rather than master.
Adam
On Jan 17, 2014, at 8:10 PM, Paul Davis wrote:
> I've spent most of the day initializing all of our new repositories
> with the source code for each Erlang application. I've taken special
> care to make sure tha
Where do you want comments? Is there a JIRA for the refactor?
Adam
On Jan 20, 2014, at 10:44 AM, Garren Smith wrote:
> Hi All,
>
> For Fauxton, I've been working on separating out the JS framework we have
> built on top of Backbone from Fauxton the web UI for CouchDB. Its sitting in
> the br
On Jan 21, 2014, at 9:00 AM, Dave Cottlehuber wrote:
>> On 21. Jänner 2014 at 10:20:58, Paul Davis (paul.joseph.da...@gmail.com)
>> wrote:
>> ...
>> As to bigcouch/rcouch conflicts its something we'll need to
>> figure out
>> for sure. I don't really see much point in trying to create
>> bigco
Agree, great discussion here. I will say that I think the INI configuration
system is quite nice, and that I'd love to see couch_config / config gain wider
adoption as an alternative to using OTP application environments (of course we
should still make the INI file itself optional by embedding
On Jan 22, 2014, at 8:13 AM, Dave Cottlehuber wrote:
> On 22. Jänner 2014 at 12:42:03, Robert Samuel Newson (rnew...@apache.org)
> wrote:
>>
>> Benoit,
>>
>> Cloudant requires R14 support, it would mean our contribution
>> to couchdb becomes useless to us and we could not contribute further.
Heya Dirkjan, that's a fair assessment. The unfortunate reality is that many
of us who have experience with the Erlang core _have_ continued to make
improvements (often open source) to the codebase -- we've just done it outside
of Apache. We're committed to changing that going forward; it's be
On Jan 22, 2014, at 6:47 AM, Noah Slater wrote:
> My first comment is: if we want more reviews, let's have more committers.
>
> We double our committer base in 2013, and the results look like this:
>
>https://www.ohloh.net/p/couchdb/analyses/latest/languages_summary
>
> And I see comments
On Jan 22, 2014, at 9:13 AM, Benoit Chesneau wrote:
> On Wed, Jan 22, 2014 at 3:55 AM, Adam Kocoloski wrote:
>
>> Agree, great discussion here. I will say that I think the INI
>> configuration system is quite nice, and that I'd love to see couch_config /
>> con
btly into erlang in order to
> use couch and it's readily parse-able by other languages.
>
>
>
>
>
>
> On 1/22/14 6:27 AM, "Adam Kocoloski" wrote:
>
>> On Jan 22, 2014, at 9:13 AM, Benoit Chesneau wrote:
>>
>>> On Wed, Jan 22, 2014 at 3:5
Sweet, thanks Daniel!
Adam
On Jan 24, 2014, at 8:49 AM, Garren Smith wrote:
>
> Hi All,
>
> Thanks to the great work from Daniel aka Humbedooh, we now will receive pull
> request comments on the mailing list. We can also reply to the comments and
> they will be logged on the pull request.
Correct, the CouchDB replicator fails on a 404 there. There are relatively few
occasions where the replicator will skip data and run to completion -- explicit
validate_doc_update rejections and MD5 mismatches on attachments are two that
come to mind.
We could / should have the discussion about
ments that can
> result in a 404, and/or handle the fact that CouchDB (pre-fix) bails on that
> or (post-fix) returns a sensible error.
>
>
>
> On 30 Jan 2014, at 14:47 , Adam Kocoloski wrote:
>
>> Correct, the CouchDB replicator fails on a 404 there. There are rela
Tricky. I'm fine with trying it out, but I do wonder how many casual followers
of dev@ would miss the really interesting technical conversations that sometime
happen on code reviews and (especially) JIRA tickets. Not an easy thing to
measure.
Adam
On Feb 4, 2014, at 3:53 AM, Noah Slater wro
What's the rationale for this option? When would I want to avoid using the
index?
Adam
On Feb 7, 2014, at 10:00 AM, beno...@apache.org wrote:
> Updated Branches:
> refs/heads/1994-merge-rcouch 38a18abbc -> 2bf88e3ff
>
>
> add the option use_index={no,yes} (yes by default)
>
> If use_index=
On Feb 12, 2014, at 8:11 AM, Benoit Chesneau wrote:
> Hi all,
>
> Sorry for this late status. I have been busy with a cold and needed work
> on the code.
>
> Anyway here is a quick status of what have been done since the last
> status:
>
> 1) The view changes has been merged. It includes some
On Feb 12, 2014, at 1:31 AM, Paul Davis wrote:
> For those of you following along at home I've just gone through and
> renamed all of the branches in the new external repositories so that
> we have a sane order to things. When I first did those extractions I
> was silly and just named the branche
I was about to suggest the same ... who beat me to it?
Adam
On Feb 12, 2014, at 6:22 PM, rnew...@apache.org wrote:
> Updated Branches:
> refs/heads/1843-feature-bigcouch 927a8d11b -> faaf44e98
>
>
> Change API to function per level
>
>
> Project: http://git-wip-us.apache.org/repos/asf/couch
Congrats Alexander, a well-deserved appointment!
Adam
On Feb 21, 2014, at 3:08 PM, Noah Slater wrote:
> Dear community,
>
> I am delighted to announce that Alexander Shorin joins the Apache
> CouchDB Project Management Committee today.
>
> Alexander has made outstanding, sustained contributio
Congratulations Andy, thanks for everything you've done so far!
Adam
On Feb 21, 2014, at 3:09 PM, Noah Slater wrote:
> Dear community,
>
> I am delighted to announce that Andy Wenk joins the Apache CouchDB
> Project Management Committee today.
>
> Andy has made outstanding, sustained contribu
timing is right — in the market and for the community — to take the
next big step forward. With your help, that is exactly what we will do.
Truly, the future of CouchDB is CouchDB.
Adam Kocoloski
Co-Founder & CTO, Cloudant
On Feb 28, 2014, at 4:31 AM, Benoit Chesneau wrote:
> Looking at the code of mem3 it seems that all databases are oblgatory
> fragmented (sharded). I understand that you can have only 1 shard /
> database but then it will be still stored at
> `/shard/`.
>
> Is there any plan of having non fragme
until
after the first release that includes clustering capabilities.
Adam
On Mar 2, 2014, at 11:30 PM, Benoit Chesneau wrote:
> On Mon, Mar 3, 2014 at 3:26 AM, Adam Kocoloski wrote:
>> On Feb 28, 2014, at 4:31 AM, Benoit Chesneau wrote:
>>
>>> Looking at the code of
I hope we can all agree that CouchDB should inform the user when it is unable
to satisfy the requested read "quorum".
Adam
> On Mar 31, 2015, at 3:20 PM, Paul Davis wrote:
>
> Sounds like there's a bit of confusion here.
>
> What Nathan is asking for is the ability to have Couch respond with
hardware to the ASF CI system as a stepping stone there
:) Cheers,
—
Adam Kocoloski
IBM Distinguished Engineer
CTO, Cloud Data Services
> On Jun 29, 2015, at 5:21 PM, Jan Lehnardt wrote:
>
> Hey all,
>
> last week I did a bit of outreach on Twitter, trying to grow our CI team.
> On Jul 2, 2015, at 6:23 AM, Jan Lehnardt wrote:
>
>
>> On 02 Jul 2015, at 12:19, Hermann Norpois wrote:
>>
>> Hello,
>>
>> how does couchdb parse the json-documents? Which tool is used? Is it a
>> known library or is it a couchdb built in function?
>
> We use https://github.com/apache/couc
Excellent, very well thought through. I think I understand that the
`X.Y.Z-couchdb.N` tag is incremented for every new *release* generated as a
descendant of the nearest reachable upstream X.Y.Z version, as opposed to every
new *commit*. That is, if we introduce 3 commits after merging with 2.12
There’s a comment in the code where we declare make_hash2() which states
> // There's a pending patch to expose this in the NIF API in newer Erlangs.
Did that patch ever land?
Adam
> On Jul 11, 2015, at 8:54 PM, Joan Touzet wrote:
>
> Alex says:
>> On Sun, Jul 12, 2015 at 3:14 AM, Joan Touzet
Hi all,
CouchDB uses the chunked transfer-encoding capability of HTTP/1.1 to stream
_all_docs, _changes, _view and similar responses to clients. We have always
sent each row of these responses in a dedicated chunk. Coalescing multiple rows
into a single chunk is more efficient and yields throug
.0.0 betas come out, I’d like to work with all the major CouchDB
>> clients to ensure compatibility, we should find out then, the latest,
>> whether we need to reverse our stance to, say, 2.
>>
>>
>> This will require some extra work to allow either behaviour and
Hiya Gil,
I think a few contributors use that setup. Note that the http://erlide.org
plugin does not yet support rebar-based projects like CouchDB, so you may not
get all the features out of the box.
In general Emacs is the editor of choice for the majority of Erlang developers,
but within the
> On Jul 27, 2015, at 11:33 AM, Jan Lehnardt wrote:
>
>>
>> On 27 Jul 2015, at 13:46, Jan Lehnardt wrote:
>>
>>
>>> On 26 Jul 2015, at 19:03, Jan Lehnardt wrote:
>>>
>>>
On 26 Jul 2015, at 14:47, Jan Lehnardt wrote:
Hey all,
I’m trying to upgrade a database from
Hi Constantin, this is definitely the right list :)
Have you seen the work on the new “Mango” query processor? The README on the
repo is probably the best resource:
https://github.com/apache/couchdb-mango
If the elements of your key array are pulled directly from fields of the
document then it
> On Mar 10, 2016, at 3:18 AM, Jan Lehnardt wrote:
>
>>
>> On 09 Mar 2016, at 21:29, Nick Wood wrote:
>>
>> Hello,
>>
>> I'm looking to back up a CouchDB server with multiple databases. Currently
>> 1,400, but it fluctuates up and down throughout the day as new databases
>> are added and old
> On Mar 14, 2016, at 2:11 AM, jav...@candeira.com wrote:
>
> On 2016-03-14 13:40, Adam Kocoloski wrote:
>
>>>> My current solution watches the global _changes feed and fires up a
>>>> continuous replication to an off-site server whenever it sees a change. If
Hi Bob, comments inline:
> On Mar 19, 2016, at 2:36 PM, Robert Samuel Newson wrote:
>
> Hi,
>
> The problem is that _db_updates is not guaranteed to see every update, so I
> think it falls at the first hurdle.
Do you mean to say that a listener of _db_updates is not guaranteed to see
every u
I modify my reply style here?
>>>>>
>>>>> On 19 Mar 2016, at 21:42, Benjamin Bastian wrote:
>>>>>>
>>>>>> When a shard is updated, it'll trigger a "database updated" event.
>>>>>> CouchDB
&
Hi all, we’ve seen a number of applications now where a user needs to count the
number of unique keys in a view. Currently the recommended approach is to add a
trivial reduce function and then count the number of rows in a _list function
or client-side application code, but of course that doesn’
Hi Bob, instead of trying to anticipate all popular options what about enabling
Mango selectors as filters? I’d hope that over time the performance of a
selector is comparable to a builtin.
Adam
> On Mar 20, 2016, at 12:34 PM, Alexander Shorin wrote:
>
> On Sun, Mar 20, 2016 at 7:30 PM, Const
Wow, does this mean that a CouchDB server running R16 and another running R17
will compute different revision IDs for the same document? We should certainly
bump to minor_version=1 across the board; we did this for on-disk
representations of document bodies quite a long time ago I think.
Adam
HI Michael, in the Mango world I think your intersection example would be
satisfied by
{ “_readers”: { “$in”: user.authTokens } }
Cheers, Adam
> On Mar 22, 2016, at 5:37 PM, Michael Fair wrote:
>
> What about some list operation functions?
> like "[one of the things in this list] is a member
> On Mar 23, 2016, at 2:31 PM, Michael Fair wrote:
>
> On Mar 23, 2016 9:41 AM, "Jan Lehnardt" wrote:
>>
>> Great sleuthing Michael!
>>
>> In addition to the recommendation to upgrade to {minor_version: 1}, which
> could
>> be a good first step,
>
> So should I just go ahead and make a pull
Neat stuff. Years ago I actually committed this feature to the codebase using a
table scan and then Damien backed it out because of the scalability concern.
Glad to see we’re approaching it in a more considered fashion this time around
:)
One thing we might consider is to maintain a *count* of
> On Mar 30, 2016, at 6:26 AM, Jan Lehnardt wrote:
>
>>
>> On 29 Mar 2016, at 20:14, Adam Kocoloski > <mailto:kocol...@apache.org>> wrote:
>>
>> Neat stuff. Years ago I actually committed this feature to the codebase
>> using a table s
Cool. I’m a little confused about the MD5 for regular docs discussion. What’s
the driving force behind switching away from revisions as ETags. Is it
1) Users can break this by setting their own revisions
2) Documents with identical bodies but different revisions should be cacheable
In case #1 a
> On Apr 13, 2016, at 12:30 PM, Alexander Shorin wrote:
>
> Hi Paul!
>
> Thanks for great input!
>
> On Wed, Apr 13, 2016 at 7:11 PM, Paul Davis
> wrote:
>> If anyone has a strong objection to a monolithic Erlang repo I'd like
>> to hear it. Otherwise I may work up a lengthier and more thoro
> On Apr 13, 2016, at 2:08 PM, Alexander Shorin wrote:
>
> On Wed, Apr 13, 2016 at 8:39 PM, Robert Newson wrote:
>> It's a thread derail but this notion that we're being "fairly rude" needs
>> resolving. It might be lost to history now but we got here, I think, with
>> the best intentions of
gt; - Original Message -
>> From: "Jan Lehnardt"
>> To: "dev@couchdb.apache.org Developers"
>> Sent: Friday, April 15, 2016 4:50:10 AM
>> Subject: Adam Kocoloski is now an IBM Fellow
>>
>> Hey all,
>>
>> our own Adam
AM, Michael Fair wrote:
>
> Looks like it.
>
> Though I was thinking these functions could operate over a list of lists,
> not just two lists.
>
>
> On Tue, Mar 22, 2016 at 8:12 PM, Adam Kocoloski wrote:
>
>> HI Michael, in the Mango world I think your inters
Hi all,
I’ve doing a bit of poking around the container orchestration space lately and
looking at how we might best deploy a CouchDB 2.0 cluster in a container
environment. In general I’ve been pretty impressed with the design point of the
Kubernetes project, and I wanted to see how hard it wou
configurable in the YAML file as the number of Pod replicas in the Deployment.
There’s still plenty to do here but I think these results are promising. Cheers,
Adam
> On Apr 29, 2016, at 10:55 PM, Adam Kocoloski wrote:
>
> Hi all,
>
> I’ve doing a bit of poking aroun
atabases are at which nodes makes sense me.
>
> It seems like each "database" being its own thing separate and apart from
> the node it executes on is a cleaner model all around.
>
> Great idea!
>
> Mike
> On Apr 29, 2016 7:55 PM, "Adam Kocoloski" <m
ocs/user-guide/petset.md>
Adam
> On May 3, 2016, at 6:09 PM, Adam Kocoloski wrote:
>
> :)
>
> 2.0 will maintain a list of which database shards are hosted on which cluster
> nodes in the _dbs database. The trouble is that there’s a 1:1 fixed
> correspondence between a
Hi Ben,
I'm not 100% certain I understand what you're looking for. Are you looking to
demonstrate the HA capabilities of a CouchDB 2.0 cluster? What sort of
"replacement" do you have in mind? One where the data previously hosted on that
node was lost and needs to be replicated back into the rep
> Auto configure couchdb to sync up and be part of cluster.
>
> Just not sure about data lost?
>
> Or if people are setting up all nodes to run off the same data set on a
> shared drive vs each node having their own copy of part of the data set.
>
> Thanks
>
> Ben
Wow, thanks for kicking this off Jan. Lots of good ideas in that list. I have a
few additional ideas:
# Containers and Package Management
Deploying an Erlang-based system can still be an unfriendly exercise. Rather
than redouble our efforts to play nice with all variants of distro-specific
pac
Cool. I think we can merge this topic with the “Tombstone Curation” topic I
posted.
Adam
> On Sep 28, 2016, at 1:04 PM, Paul Davis wrote:
>
> Thanks for the write up, Jan! I've only got one major change to add
> and its a bit of a doozy.
>
> # Update our revision model from a tree to a graph
t; On Jul 7, 2016, at 12:01 PM, Adam Kocoloski wrote:
>
> Kubernetes 1.3 adds a new concept called “PetSets” (yes, as in “Cattle vs.
> Pets”) geared towards our use case. Documentation is here:
>
> https://github.com/kubernetes/kubernetes.github.io/blob/master/docs/user-guid
1 - 100 of 1416 matches
Mail list logo
