Joan Touzet created COUCHDB-3415:
Summary: EUnit: should_accept_live_as_an_alias_for_continuous
invalid_trailing_data
Key: COUCHDB-3415
URL: https://issues.apache.org/jira/browse/COUCHDB-3415
[
https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001952#comment-16001952
]
Joan Touzet commented on COUCHDB-1946:
--
I know it's a bit late, but since this issue still seems to
wohali commented on issue #510: Hibernate couch_stream after each write
URL: https://github.com/apache/couchdb/pull/510#issuecomment-300045928
Reminder to myself that if we agree to do this in 2.x, we might want to do
it in the 1.6.x branch as well.
wohali opened a new pull request #510: Hibernate couch_stream after each write
URL: https://github.com/apache/couchdb/pull/510
In COUCHDB-1946 Adam Kocoloski investigated a memory explosion resulting
from replication of databases with large attachments (npm fullfat). He
was able to
nickva commented on issue #509: Handle non-default _replicator dbs in
_scheduler/docs endpoint
URL: https://github.com/apache/couchdb/pull/509#issuecomment-27999
@wohali
Argh! You're right.
Hmm, what if user wants to query a particular document they have to always
[
https://issues.apache.org/jira/browse/COUCHDB-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001766#comment-16001766
]
ASF subversion and git services commented on COUCHDB-3298:
--
Commit
[
https://issues.apache.org/jira/browse/COUCHDB-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001765#comment-16001765
]
ASF subversion and git services commented on COUCHDB-3389:
--
Commit
nickva commented on issue #509: Handle non-default _replicator dbs in
_scheduler/docs endpoint
URL: https://github.com/apache/couchdb/pull/509#issuecomment-27999
@wohali
Argh! You're right.
Hmm, what if user wants to query a particular document they have to always
nickva commented on issue #506: Custom replication DBs never get
/_scheduler/docs entries
URL: https://github.com/apache/couchdb/issues/506#issuecomment-299903832
1. Can be done relatively straightforward. Also it looks like we could even
allow un-escaped dbname and then rebuild the db
driglou commented on issue #508: Apache CouchDB Windows Service Paused
URL: https://github.com/apache/couchdb/issues/508#issuecomment-299970364
The problem still remains exactly as it was.
Is there anything more I can do?
Also before when I installed CouchDB for the first time
[
https://issues.apache.org/jira/browse/COUCHDB-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16001406#comment-16001406
]
Wilhelm Uschtrin commented on COUCHDB-3369:
---
Still wondering about this...
> Using Fauxton
wohali commented on issue #508: Apache CouchDB Windows Service Paused
URL: https://github.com/apache/couchdb/issues/508#issuecomment-299951757
Try adding the "LOCAL SERVICE" account and give it full control. Users
shouldn't have it.
wohali commented on issue #509: Handle non-default _replicator dbs in
_scheduler/docs endpoint
URL: https://github.com/apache/couchdb/pull/509#issuecomment-299951233
What about a document in `_replicator` named `other%2f_replicator` ?
wohali commented on issue #509: Handle non-default _replicator dbs in
_scheduler/docs endpoint
URL: https://github.com/apache/couchdb/pull/509#issuecomment-299951233
What about a document in `_replicator` name `other%2f_replicator` ?
nickva commented on issue #504: Opimize writing KV node append writes
URL: https://github.com/apache/couchdb/pull/504#issuecomment-299930506
After another update to script to make random keys the same size as
sequential ones, I see that patched version wins most of the time.
Script
nickva opened a new pull request #509: Handle non-default _replicator dbs in
_scheduler/docs endpoint
URL: https://github.com/apache/couchdb/pull/509
## Overview
Previously _scheduler/docs assumed only the default _replicator db.
Now these kinds of paths are accepted after
nickva commented on issue #506: Custom replication DBs never get
/_scheduler/docs entries
URL: https://github.com/apache/couchdb/issues/506#issuecomment-299903832
1. Can be done relatively straightforward. Also it looks like we could even
allow un-escaped dbname and then rebuild the db
driglou commented on issue #508: Apache CouchDB Windows Service Paused
URL: https://github.com/apache/couchdb/issues/508#issuecomment-299844250
Thank you for quick response.
I did what you said, however the problem still remains.
I added full access the the C:\CouchDB and its
Alexander F Rødseth created COUCHDB-3414:
Summary: Support Erlang 20.0
Key: COUCHDB-3414
URL: https://issues.apache.org/jira/browse/COUCHDB-3414
Project: CouchDB
Issue Type: New
jaydoane commented on a change in pull request #492: Test changes_listener dies
on mem3_shards shutdown
URL: https://github.com/apache/couchdb/pull/492#discussion_r115177527
##
File path: src/mem3/src/mem3_shards.erl
##
@@ -726,4 +726,50 @@ wait_writer_result(WRef) ->
jaydoane commented on a change in pull request #492: Test changes_listener dies
on mem3_shards shutdown
URL: https://github.com/apache/couchdb/pull/492#discussion_r115177516
##
File path: src/mem3/src/mem3_shards.erl
##
@@ -726,4 +726,50 @@ wait_writer_result(WRef) ->
21 matches
Mail list logo
