Hi all,
I noticed that the docs for 1.6.1 seem to be missing. If I visit
http://docs.couchdb.org/ I get redirected to
http://docs.couchdb.org/en/1.6.1/ which seems to be the WIP 2.0 docs.
Is this intentional (I assume not)?
Will
Assuming nothing's changed in the last few weeks, there are 2 issues
which cause the PouchDB tests to fail against master: COUCHDB-3017 and
COUCHDB-3034.
Both could be addressed in the test suite by using different database
names for each test, but that's quite a disruptive change.
On 2 September
>
> - Original Message -
>> From: "Will Holley"
>> To: dev@couchdb.apache.org, "Joan Touzet"
>> Sent: Friday, September 2, 2016 4:43:48 AM
>> Subject: Re: Getting libraries to test RCs
>>
>> Assuming nothing's changed in t
t;>
>>>> Hi Will,
>>>>
>>>> Neither of these are currently tagged as blocking issues for CouchDB
>>>> 2.0, only major priority. If you want to flag them as such, this is
>>>> your last chance, and even still, there's no guarantee
Ah. 2.1.1 has a bug in /_explain when a sort is specified
(https://github.com/apache/couchdb/pull/1025).
That said, the 2.1.0 output looks broken - it's not using an index on
"test" so can't be sorting. Were the results actually sorted?
On 9 May 2018 at 09:27, GitBox wrote:
> glonco commented on
Thanks for kicking this off Garren! I have a few questions / thoughts:
1. Will these indexes continue to have associated design documents? I
assume this aspect wouldn't change, but it would be good to be explicit.
Aside from being required for replication, it's useful to be able to query
the /db/_
Thanks Garren,
As usual, a few questions :)
1. The data model suggests the idea of view groups gets carried over to
fdb. Are there API / behaviour reasons to keep them? Would an index update
transaction scope to a view group rather than a single view?
2. Regarding emitting doc as the value in a v
>From an operational pov, the compaction daemon was removed in favour of
smoosh [1]. We owe some documentation around these new subsystems (smoosh,
ioq, ken) and some guides covering common cases (only compact during quiet
periods, disable compaction, etc) to aid migration.
[1] https://github.com/
I defer to those with more operational experience of ken and smoosh but
wouldn't those new subsystems radically impact performance if IOQ is
completely bypassed (assuming ken/smoosh are enabled by default)?
On Wed, 11 Sep 2019 at 22:04, Adam Kocoloski wrote:
> A few months ago a bunch of code la
Hi all,
CouchDB has a mature Helm chart at
https://github.com/helm/charts/tree/master/stable/couchdb to facilitate
deploying CouchDB clusters to Kubernetes. Historically, Helm charts have
been curated by the Helm team alongside a list of chart-specific
maintainers (@kocolosk in this case).
The He
nders if ASF would want to host a repository to which all
> projects could contribute but I don’t personally feel like spending the
> cycles to find out :) I’m quite ok with CouchDB hosting its own.
>
> Adam
>
> > On Sep 26, 2019, at 12:18 PM, Will Holley wrote:
> >
&
>Hi all,
>
>CouchDB has a mature Helm chart at
https://github.com/helm/charts/tree/master/stable/couchdb >to facilitate
deploying CouchDB clusters to Kubernetes. Historically, Helm charts have
been >curated by the Helm team alongside a list of chart-specific
maintainers (@kocolosk in this case).
>
+1: 5
+0: 0
-1: 0
Thanks all - vote passes. I'll aim to start the migration this week.
Cheers,
Will
On Tue, 8 Oct 2019 at 18:25, Adam Kocoloski wrote:
> +1 thanks Will
>
> > On Oct 8, 2019, at 9:31 AM, Will Holley wrote:
> >
> >
> >>
> >> Hi
Thanks Joan for highlighting the problem; the image has been removed from
DockerHub.
On Mon, 3 Feb 2020 at 17:46, Joan Touzet wrote:
> On 2020-02-03 12:34, Jan Lehnardt wrote:
> > Thanks Joan for raising this,
> >
> > I’m throwing in an extra “this is bad” because of the version number.
> 3.0 is
+1 make check passing on Centos 7, tested both amd64 and ppc64le. I'm going
to try on Centos 8 next...
One thing I noticed is that the Unix install instructions look outdated
with respect to Erlang / Node / Python dependencies though I'm not 100%
sure what the supported options are now.
On Thu,
also verified make check passes on CentOS 8 with SM60 using the standard
mozjs60/mozjs60-devel packages. Tested amd64 and ppc64le.
I also ran some basic clouseau tests which ran fine.
On Thu, 13 Feb 2020 at 10:47, Will Holley wrote:
> +1 make check passing on Centos 7, tested both amd64
Some of our internal teams reported that the cluster seedlist function is
broken in RC1. I was able to reproduce and filed
https://github.com/apache/couchdb/issues/2559 to track.
On Sat, 15 Feb 2020 at 01:23, Joan Touzet wrote:
> On 2020-02-14 5:49 p.m., Dave Cottlehuber wrote:
> > On Fri, 14 Fe
For running in a container, you could also try using the Red Hat UBI
instead of CentOS. There is a ubi-init variant which runs systemd (see
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/building_running_and_managing_containers/index#using_init_red_hat_base_ima
Broadly, I think it's a big step forward if we can prevent Mango from
automatically selecting extremely stale indexes.
I've been going back and forth on whether step 3 could lead to some
difficult-to-predict behaviour. If we assume that requests have a short
timeout - e.g. we can't return any resu
11:04 AM Will Holley wrote:
>
> > Broadly, I think it's a big step forward if we can prevent Mango from
> > automatically selecting extremely stale indexes.
> >
> > I've been going back and forth on whether step 3 could lead to some
> > difficult-to-predict
Congrats Glynn!
On Mon, 14 Sep 2020 at 17:29, Joshua Mintz wrote:
> Congrats, Glynn!
>
> On Mon, Sep 14, 2020 at 12:23 PM Jan Lehnardt wrote:
>
> > Congratulations Glynn! :)
> >
> > > On 14. Sep 2020, at 18:22, Michelle P wrote:
> > >
> > >
> > > Dear community,
> > >
> > > I am delighted to a
Environment:
RHEL 8
Elixir: 1.9.1
Erlang: 20.3.8.25
CPU Architectures: amd64, ppc64le, s390x
Sig: ok
Checksums: ok
Configure, make & make check: ok
Build release, add admin & start: ok
Used Fauxton to:
- configure cluster: ok
- verify install: ok
- create dbs: ok
- create docs: ok
Thanks Peng Hui, Garren. I can definitely see value in having metrics
exposed in Prometheus format.
One aspect I'm unclear about is what _active_tasks metrics would represent.
My expectation is that /_metrics would be scoped to a node (and then leave
the aggregation across nodes to Prometheus or s
It's a good point about querying every node for cluster-wide data such as
_active_tasks (assuming a direct translation of the current endpoint),
though I think it's better to lean on the monitoring tool to aggregate data
across nodes rather than deduplicate. Possibly the simplest thing for a v1
wou
It's probably easier to configure the cluster with n=1 rather than change
write quorum on a per-request basis. This was the approach we took with the
PouchDB tests and it worked well (as a first step, at least).
Will
On 8 Apr 2015 20:26, "Sebastian Rothbucher" <
sebastianrothbuc...@googlemail.com>
on costs dramatically,
> thanks.
>
> > I've gotten the +1 from Will Holley that our implementation is consistent
>> with the proposed CouchDB version
>
> Does Cloudant already has this endpoint onboard? I‘ve tried to, but failed
> – although not sure I did all the things
[
https://issues.apache.org/jira/browse/COUCHDB-1935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13825160#comment-13825160
]
Will Holley commented on COUCHDB-1935:
--
There is already a collapsable &quo
[
https://issues.apache.org/jira/browse/COUCHDB-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922671#comment-13922671
]
Will Holley commented on COUCHDB-2188:
--
This sounds like it is not fixable u
Will Holley created COUCHDB-2249:
Summary: Fauxton generates incorrect parameters when complex keys
are specified
Key: COUCHDB-2249
URL: https://issues.apache.org/jira/browse/COUCHDB-2249
Project
[
https://issues.apache.org/jira/browse/COUCHDB-2249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley resolved COUCHDB-2249.
--
Resolution: Fixed
> Fauxton generates incorrect parameters when complex keys are specif
Will Holley created COUCHDB-2518:
Summary: CouchDB 2.0 does not support conflicts=true on /_changes
Key: COUCHDB-2518
URL: https://issues.apache.org/jira/browse/COUCHDB-2518
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2518:
-
Description:
CouchDB 1.X supports the conflicts=true query parameter for all API endpints
[
https://issues.apache.org/jira/browse/COUCHDB-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2518:
-
Description:
CouchDB 1.X supports the conflicts=true query parameter for all API endpints
Will Holley created COUCHDB-2519:
Summary: CouchDB 2.0 does not support attachments=true on /_changes
Key: COUCHDB-2519
URL: https://issues.apache.org/jira/browse/COUCHDB-2519
Project: CouchDB
Will Holley created COUCHDB-2523:
Summary: CouchDB 2.0: Specifying startkey/endkey parameters
alongside a keys parameter when querying /_all_docs should be invalid
Key: COUCHDB-2523
URL: https://issues.apache.org
Will Holley created COUCHDB-2530:
Summary: CouchDB 2.0 does not support POST requests to _changes
Key: COUCHDB-2530
URL: https://issues.apache.org/jira/browse/COUCHDB-2530
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2530:
-
Description:
In CouchDB 1.6, the _changes feed accepts a POST request (e.g. to submit a
large
Will Holley created COUCHDB-2531:
Summary: CouchDB 2.0: POST to /_revs_diff with no revisions times
out
Key: COUCHDB-2531
URL: https://issues.apache.org/jira/browse/COUCHDB-2531
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-2537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14303676#comment-14303676
]
Will Holley commented on COUCHDB-2537:
--
I'm happy to be shot down but I
Will Holley created COUCHDB-2568:
Summary: CouchDB 2.0 /_all_docs does not return full attachment
data with attachments=true
Key: COUCHDB-2568
URL: https://issues.apache.org/jira/browse/COUCHDB-2568
[
https://issues.apache.org/jira/browse/COUCHDB-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2568:
-
Summary: CouchDB 2.0 /_all_docs does not return full attachment data with
keys=["so
[
https://issues.apache.org/jira/browse/COUCHDB-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2568:
-
Description: Similar to case COUCHDB-2522, in CouchDB 1.6,
'/_all_docs'?keys
[
https://issues.apache.org/jira/browse/COUCHDB-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Holley updated COUCHDB-2568:
-
Description:
Similar to case COUCHDB-2522, in CouchDB 1.6,
'/_all_docs'?keys
Will Holley created COUCHDB-2674:
Summary: Inconsistent handling of URL encoded design doc name
between clustered and non-clustered interfaces
Key: COUCHDB-2674
URL: https://issues.apache.org/jira/browse/COUCHDB
44 matches
Mail list logo