Dear community,
Being a volunteer organisation, we rely on you to help us promote releases.
Here is the official blog post:
https://blogs.apache.org/couchdb/entry/apache_couchdb_1_6_0
Here is the official tweet:
https://twitter.com/CouchDB/status/476414924412178432
We also have a
n Wed, Jun 11, 2014 at 1:00 PM, Benoit Chesneau bchesn...@gmail.com wrote:
quickcheck made quickcheck-ci available for free for open-sources projects:
http://quickcheck-ci.com/
It would be interresting to use it for couchdb imo. Thoughts?
If we still use Travis, we already have 2 CI
On Wed, Jun 11, 2014 at 7:39 PM, Russell Branca chewbra...@apache.org wrote:
To clarify the questions about another CI server, I believe the reason
for this being released as a CI server is as a way to use the full version
of QuickCheck without them having to distribute it.
Given all this
On Thu, Jul 3, 2014 at 9:30 AM, Alexander Shorin kxe...@gmail.com wrote:
From today's IRC:
[11:25:03]warren:
https://bugzilla.redhat.com/show_bug.cgi?id=709251 any comment from
couchdb developers if this is necessary?
Do we have any?
Not sure if this would qualify as necessary, but it
On Mon, Jul 7, 2014 at 9:11 PM, Robert Samuel Newson rnew...@apache.org wrote:
The merge of bigcouch has reached a stage now where I think it’s time to
merge to master.
Exciting stuff!
I stress that after the merge to master there is still some work ahead of us
before a 2.0 release can be
On Mon, Jul 7, 2014 at 10:31 PM, Robert Samuel Newson
rnew...@apache.org wrote:
Is there more to do on master for that release? If so, what? If not, branch
now?
Since we do time-based releases, the default answer to that question
should be no. It would be fine by me to just branch the new
On Wed, Jul 9, 2014 at 8:56 AM, Andy Wenk a...@nms.de wrote:
WTF? Do we need a lawyer for every sentence we, or someone from the
community is writing somewhere in conjunction with CouchDB? I mean it's
just a name. An example name. This is nonsense imho. A short explanation to
texinwien is good
On Tue, Jul 8, 2014 at 6:21 PM, Noah Slater nsla...@apache.org wrote:
It's come to my attention that some of the release housekeeping is being
missed.
Yup, sorry for that. I always get a bit tired by the end of the
release process and postpone the housekeeping process. Also, the old
wiki feels
On Wed, Jul 9, 2014 at 10:46 AM, Andy Wenk a...@nms.de wrote:
I can imagine that :). Do you have a time slot to cleanup the dist dir?
I just removed the 1.3.0, 1.3.1, 1.4.0 versions from dist/release.
Cheers,
Dirkjan
On Thu, Jul 31, 2014 at 6:12 PM, Noah Slater nsla...@apache.org wrote:
Holler if you wanna discuss this.
Can we convert the site/docs to git at some point? Or is that
problematic from an infra POV?
Cheers,
Dirkjan
On Wed, Aug 6, 2014 at 7:52 AM, Dave Cottlehuber d...@jsonified.com wrote:
This is the `hash admin passwords on startup when list` fix again, which will
catch more more people as time goes on. I’m wondering if we should do a
1.6.1
specifically due to this?
Sounds sane.
Do we not have tests
On Fri, Aug 15, 2014 at 3:26 PM, Alexander Shorin kxe...@gmail.com wrote:
On Fri, Aug 15, 2014 at 6:21 PM, Paul Davis paul.joseph.da...@gmail.com
wrote:
Here's a first pass at things. I'm not entirely sure where this sort
of thing should go in the source tree, suggestions welcome.
On Wed, Sep 24, 2014 at 12:35 PM, Jan Lehnardt j...@apache.org wrote:
That’s it so far, what do you think? :)
It sucks that/if Admin Party has to go. Firewalls or only listening on
127.0.0.1 are a perfectly fine solution, IMO.
I would really like to be able to do simple forms of setup from the
On Mon, Jan 26, 2015 at 8:18 PM, Jan Lehnardt j...@apache.org wrote:
I’m also in favour of getting Nano into the Apache CouchDB fold.
I'm curious; would you like to bring more CouchDB libraries into the
Apache project proper? Why do you think that would be an improvement?
What are the advantages
Hi all,
Although I'd previously dropped hints about this in other email
threads, I wanted to make it explicit that I have stopped spending as
much time on CouchDB as I did in previous years. This means that I
won't spend time on the documentation or on release management
anymore. However, I'll
Hi Francis,
On Sat, Apr 11, 2015 at 3:24 PM, Francis Ridder
francis.rid...@gmail.com wrote:
Hi, I contacted Dirkjan on twitter about some ideas regarding the python
lib. I was wondering if the community is open to switching the underlying
http stuff with the Requests library?
Thanks for
On Fri, May 15, 2015 at 8:13 PM, Jan Lehnardt j...@apache.org wrote:
- Accepted the Nano project (a Node.js library for CouchDB) into
Apache CouchDB. This took a while because IP-clearance for a
GitHub project is, well, interesting.
How are the feelings about the result, so far? Has
On Tue, Jul 21, 2015 at 5:42 PM, Adam Kocoloski kocol...@apache.org wrote:
So — do any of you knowingly rely on this behavior? How difficult would it be
to accommodate this change?
I spent a little time looking at the CouchDB-Python code to see how it
would be impacted. From what I'm seeing,
All,
A few weeks ago I put out a call for new maintainers on the couchdb-python
mailing list; after being the main maintainer for 8 years, I'd like to
spend my time on other things.
However, there have been no responses so far on the list. I remember that
the Apache CouchDB project at some point
: Dirkjan Ochtman
It should be possible to build CouchDB with the system snappy instead of the
bundled one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure
[
https://issues.apache.org/jira/browse/COUCHDB-1458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1458:
-
Summary: Provide an option to build with the system snappy (was:
--with-system-snappy
System
Affects Versions: 1.2
Reporter: Dirkjan Ochtman
It should be possible to build with the system yajl instead of the bundled one
through a --with-system-yajl configure option.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please
Affects Versions: 1.2
Reporter: Dirkjan Ochtman
With this task:
[{pid:0.586.0,changes_done:69133,database:mail-djc,progress:35,started_on:1333976136,total_changes:192216,type:database_compaction,updated_on:1333976265}]
I see this in my browser's console:
[14:55:46.702] $(trth
[
https://issues.apache.org/jira/browse/COUCHDB-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13466767#comment-13466767
]
Dirkjan Ochtman commented on COUCHDB-1536:
--
It's mostly the commit hook trick
[
https://issues.apache.org/jira/browse/COUCHDB-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13472240#comment-13472240
]
Dirkjan Ochtman commented on COUCHDB-71:
Since the new docs have Futon screenshots
Dirkjan Ochtman created COUCHDB-1571:
Summary: Error when using _replicate from CouchDB-python tests
Key: COUCHDB-1571
URL: https://issues.apache.org/jira/browse/COUCHDB-1571
Project: CouchDB
[
https://issues.apache.org/jira/browse/COUCHDB-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1571:
-
Description:
This code:
aname, a = self.temp_db()
bname, b
[
https://issues.apache.org/jira/browse/COUCHDB-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483521#comment-13483521
]
Dirkjan Ochtman commented on COUCHDB-1571:
--
By during the process, you really
[
https://issues.apache.org/jira/browse/COUCHDB-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13483539#comment-13483539
]
Dirkjan Ochtman commented on COUCHDB-1571:
--
Reinstalling CouchDB worked, thanks
Reporter: Dirkjan Ochtman
Priority: Minor
Fix For: 0.10
It would be great if CouchDB came with a built-in db/_conflicts view. It could
have code like the current test/view_conflicts.js.
--
This message is automatically generated by JIRA.
-
You can reply to this email
: 0.9
Reporter: Dirkjan Ochtman
Priority: Minor
I'd love to be able to make a quick jump to a document for which I know the ID,
from the database page in Futon.
When doing admin tasks on a larger database, browsing documents to find a
needed document becomes tedious. We
[
https://issues.apache.org/jira/browse/COUCHDB-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-301:
Attachment: futon-jump-to.diff
Here's my patch for this. Seems to work in Firefox and IE7
Components: Build System
Affects Versions: 0.9
Environment: Happens in Gentoo, custom-made ebuild (see earlier ones
in http://hg.xavamedia.nl/portage/).
Reporter: Dirkjan Ochtman
Fix For: 0.9
It works with r755866, fails with r757406 (from the snapshots off
Versions: 0.9
Environment: Gentoo, bash 3.2.39.
Reporter: Dirkjan Ochtman
Priority: Minor
Fix For: 0.9
When starting CouchDB, I get the following warnings:
/usr/bin/couchdb: line 143: 0: command not found
/usr/bin/couchdb: line 147: 0: command not found
Issue Type: Improvement
Components: HTTP Interface
Affects Versions: 0.9
Reporter: Dirkjan Ochtman
Priority: Trivial
Fix For: 0.10
Attachments: server-links.diff
It would be nice if the HTTP interface made it easy to find other relevant
[
https://issues.apache.org/jira/browse/COUCHDB-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-308:
Attachment: server-links.diff
Here's a patch to do this for the / info page.
Server
[
https://issues.apache.org/jira/browse/COUCHDB-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12744965#action_12744965
]
Dirkjan Ochtman commented on COUCHDB-476:
-
I think we already keep a cookie
[
https://issues.apache.org/jira/browse/COUCHDB-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791296#action_12791296
]
Dirkjan Ochtman commented on COUCHDB-348:
-
It should probably parse the qvalues
: Improvement
Components: Database Core
Affects Versions: 0.10.1
Reporter: Dirkjan Ochtman
Fix For: 0.11
When I delete a single view from the ddoc but the others are unchanged, it
shouldn't re-index.
--
This message is automatically generated by JIRA.
-
You can reply
[
https://issues.apache.org/jira/browse/COUCHDB-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006618#comment-13006618
]
Dirkjan Ochtman commented on COUCHDB-841:
-
I agree that the time to do
Versions: 1.1
Reporter: Dirkjan Ochtman
In CouchDB 1.1, it appears that /_config, despite being in JSON, is sent as
text/plain. This is bad.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[
https://issues.apache.org/jira/browse/COUCHDB-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13103040#comment-13103040
]
Dirkjan Ochtman commented on COUCHDB-986:
-
+1 this would be awesome to have
[
https://issues.apache.org/jira/browse/COUCHDB-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145522#comment-13145522
]
Dirkjan Ochtman commented on COUCHDB-1335:
--
You're right... the daemon
[
https://issues.apache.org/jira/browse/COUCHDB-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13145537#comment-13145537
]
Dirkjan Ochtman commented on COUCHDB-1335:
--
Yup, should be all good
[
https://issues.apache.org/jira/browse/COUCHDB-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13196629#comment-13196629
]
Dirkjan Ochtman commented on COUCHDB-841:
-
+1. IMO we should probably close
[
https://issues.apache.org/jira/browse/COUCHDB-1399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13199705#comment-13199705
]
Dirkjan Ochtman commented on COUCHDB-1399:
--
This seems like exceedingly limited
[
https://issues.apache.org/jira/browse/COUCHDB-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669653#comment-13669653
]
Dirkjan Ochtman commented on COUCHDB-721:
-
As far as I recall it might have been
[
https://issues.apache.org/jira/browse/COUCHDB-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1572:
-
Fix Version/s: (was: 1.4)
1.5
Remove support
[
https://issues.apache.org/jira/browse/COUCHDB-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1581:
-
Fix Version/s: (was: 1.4)
1.5
Update bundled dependencies
[
https://issues.apache.org/jira/browse/COUCHDB-1691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1691:
-
Fix Version/s: (was: 1.4)
Topbar Addon
Key
[
https://issues.apache.org/jira/browse/COUCHDB-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1218:
-
Fix Version/s: (was: 1.4)
1.5
Better logger performance
[
https://issues.apache.org/jira/browse/COUCHDB-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13715326#comment-13715326
]
Dirkjan Ochtman commented on COUCHDB-1377:
--
Anyone want to unbitrot
[
https://issues.apache.org/jira/browse/COUCHDB-1857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1857:
-
Summary: _changes API reference doesn't mention the eventsource feed (was:
_changes
[
https://issues.apache.org/jira/browse/COUCHDB-1573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1573:
-
Fix Version/s: (was: 1.4)
Use JSON.stringify
[
https://issues.apache.org/jira/browse/COUCHDB-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13749936#comment-13749936
]
Dirkjan Ochtman commented on COUCHDB-906:
-
+1, I think it would be valuable
[
https://issues.apache.org/jira/browse/COUCHDB-1894?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777435#comment-13777435
]
Dirkjan Ochtman commented on COUCHDB-1894:
--
Looking at the diff, can we make
[
https://issues.apache.org/jira/browse/COUCHDB-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1837:
-
Fix Version/s: (was: 1.4.0)
1.5.0
Incorrect HTTP response
[
https://issues.apache.org/jira/browse/COUCHDB-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1566:
-
Fix Version/s: (was: 1.4.0)
1.5.0
JSpec test page broken
[
https://issues.apache.org/jira/browse/COUCHDB-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1379:
-
Fix Version/s: (was: 1.4.0)
1.5.0
Extend attachment etag
[
https://issues.apache.org/jira/browse/COUCHDB-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1838:
-
Fix Version/s: (was: 1.4.0)
1.5.0
Specifying public_fields
[
https://issues.apache.org/jira/browse/COUCHDB-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1334:
-
Fix Version/s: (was: 1.4.0)
1.5.0
Indexer speedup (for non
[
https://issues.apache.org/jira/browse/COUCHDB-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman resolved COUCHDB-1493.
--
Resolution: Fixed
Fix Version/s: (was: 1.5.0)
1.4.0
[
https://issues.apache.org/jira/browse/COUCHDB-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777605#comment-13777605
]
Dirkjan Ochtman commented on COUCHDB-1334:
--
Since we're getting close to 1.5.0
[
https://issues.apache.org/jira/browse/COUCHDB-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777608#comment-13777608
]
Dirkjan Ochtman commented on COUCHDB-1379:
--
Ping?
Extend
[
https://issues.apache.org/jira/browse/COUCHDB-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777609#comment-13777609
]
Dirkjan Ochtman commented on COUCHDB-1838:
--
Is there anything we will be doing
[
https://issues.apache.org/jira/browse/COUCHDB-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13777610#comment-13777610
]
Dirkjan Ochtman commented on COUCHDB-1837:
--
So, what do we do here
[
https://issues.apache.org/jira/browse/COUCHDB-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1566:
-
Fix Version/s: (was: 1.5.0)
1.3.1
Assuming this got fixed
[
https://issues.apache.org/jira/browse/COUCHDB-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1838:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Specifying public_fields
[
https://issues.apache.org/jira/browse/COUCHDB-1824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1824:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Official documentation
[
https://issues.apache.org/jira/browse/COUCHDB-1218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1218:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Better logger performance
[
https://issues.apache.org/jira/browse/COUCHDB-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1334:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Indexer speedup (for non
[
https://issues.apache.org/jira/browse/COUCHDB-1377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1377:
-
Fix Version/s: (was: 1.5.0)
1.6.0
support X-Forwarded
[
https://issues.apache.org/jira/browse/COUCHDB-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1837:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Incorrect HTTP response
[
https://issues.apache.org/jira/browse/COUCHDB-1572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-1572:
-
Fix Version/s: (was: 1.5.0)
1.6.0
Remove support
[
https://issues.apache.org/jira/browse/COUCHDB-1928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13818773#comment-13818773
]
Dirkjan Ochtman commented on COUCHDB-1928:
--
https://svn.apache.org/repos/asf
[
https://issues.apache.org/jira/browse/COUCHDB-1934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826425#comment-13826425
]
Dirkjan Ochtman commented on COUCHDB-1934:
--
Deprecating it sounds good to me. I
[
https://issues.apache.org/jira/browse/COUCHDB-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13853278#comment-13853278
]
Dirkjan Ochtman commented on COUCHDB-2007:
--
LGTM!
Building docs under CI
[
https://issues.apache.org/jira/browse/COUCHDB-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12806314#action_12806314
]
Dirkjan Ochtman commented on COUCHDB-604:
-
For me, the non-valid-JSON (e.g. object
Affects Versions: 0.10.1
Reporter: Dirkjan Ochtman
Fix For: 0.12
It would be nice to have an option for changes feeds that would let me get the
full documents along with the update seq. For example, in my application using
a continuous feed, I request the updated document
Reporter: Dirkjan Ochtman
Priority: Minor
Fix For: 0.12
Currently, (continuous) replication almost preserves the ordering of the
updates. It would be nice if this could be fixed so that the order of outgoing
updates fully corresponds to the order inside
[
https://issues.apache.org/jira/browse/COUCHDB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman closed COUCHDB-685.
---
Resolution: Fixed
Fix Version/s: (was: 0.12)
0.11
[
https://issues.apache.org/jira/browse/COUCHDB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843017#action_12843017
]
Dirkjan Ochtman commented on COUCHDB-685:
-
Oh, nice. Just to prefer further
[
https://issues.apache.org/jira/browse/COUCHDB-686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12843502#action_12843502
]
Dirkjan Ochtman commented on COUCHDB-686:
-
Hmm, so I read somewhere
[
https://issues.apache.org/jira/browse/COUCHDB-719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851312#action_12851312
]
Dirkjan Ochtman commented on COUCHDB-719:
-
Also, I'm pretty sure
: 0.11
Reporter: Dirkjan Ochtman
Priority: Minor
Fix For: 0.12
I have a database where document ID's include '' and ''. When I browse the
database, Futon shows 'lt;' for the key (double-escaping the actual value). On
the other hand, for the ID just below
[
https://issues.apache.org/jira/browse/COUCHDB-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dirkjan Ochtman updated COUCHDB-719:
Fix Version/s: (was: 0.12)
0.11.1
Bad escaping in Futon view
[
https://issues.apache.org/jira/browse/COUCHDB-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12851924#action_12851924
]
Dirkjan Ochtman commented on COUCHDB-721:
-
Thanks, I was going to file myself
[
https://issues.apache.org/jira/browse/COUCHDB-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12860158#action_12860158
]
Dirkjan Ochtman commented on COUCHDB-721:
-
Do we have an update on this? I'd like
Interface
Affects Versions: 1.0
Reporter: Dirkjan Ochtman
Just wanted to put this on the roadmap: it would be nice if continuous changes
feeds (and maybe some other things in CouchDB, not sure) could support
WebSockets. WebSockets are an emerging standard (there's no final spec yet
Components: HTTP Interface
Affects Versions: 0.11.1
Reporter: Dirkjan Ochtman
Priority: Trivial
Currently, when passing continuous=false to _replicate, CouchDB throws a
generic badmatch error, which isn't very friendly. It would be nice to either
get a better error
[
https://issues.apache.org/jira/browse/COUCHDB-841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906237#action_12906237
]
Dirkjan Ochtman commented on COUCHDB-841:
-
I should note here, I asked Bob
Versions: 1.0.1
Reporter: Dirkjan Ochtman
Fix For: 1.0.2
I have a reducing view which has date-based keys ([2010] or [2010, 09] or
[2010, 09, 07]).
reduce=truegroup_level=2startkey=[2010,09]limit=1 gives me
{rows:[{key:[2010,09],value:{...}]}.
reduce=truegroup_level
[
https://issues.apache.org/jira/browse/COUCHDB-880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12906804#action_12906804
]
Dirkjan Ochtman commented on COUCHDB-880:
-
damjan in IRC pointed out
401 - 493 of 493 matches
Mail list logo
