[
https://issues.apache.org/jira/browse/COUCHDB-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468376#comment-13468376
]
Stephane Alnet commented on COUCHDB-1155:
-
This issue could probably be renamed
[
https://issues.apache.org/jira/browse/COUCHDB-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13468406#comment-13468406
]
Stéphane Alnet commented on COUCHDB-1155:
-
Although you can't currently override
On Tue, Oct 2, 2012 at 3:18 PM, Benoit Chesneau bchesn...@gmail.com wrote:
I could do a jira review of outstanding tickets, if that's going to help.
Couldn't hurt. I would take up blockers if we have any. Dustin, if you
have any debug info to provide, or issues open for the replication
problems
Fwiw, I took a swing at resolving critical issues for a 1.3 release a
few weeks ago. Fixed a few things. I'd definitely encourage others to
dig in again.
imo, 1.3 should be bug fixes, docs and CORS, the latter being the most at-risk.
I'd really like 1.3 to be a solid release that we can use as
On Wed, Oct 3, 2012 at 7:42 PM, Robert Newson robert.new...@gmail.com wrote:
imo, 1.3 should be bug fixes, docs and CORS, the latter being the most
at-risk.
There's also a bunch of other stuff already in the tree, right? I
think there was a new view processor or something, and EventSource
On Wed, Oct 3, 2012 at 1:31 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Oct 3, 2012 at 7:42 PM, Robert Newson robert.new...@gmail.com wrote:
imo, 1.3 should be bug fixes, docs and CORS, the latter being the most
at-risk.
There's also a bunch of other stuff already in the tree,
On 9/25/2012 10:02 AM, Dale Harvey wrote:
On 25 September 2012 14:39, Benoit Chesneau bchesn...@gmail.com wrote:
On Tue, Sep 25, 2012 at 3:29 PM, Dale Harvey d...@arandomurl.com wrote:
Just wanted to chime in on a few points
I think Couch should definitely ship with a tool to upload a
On Wed, Oct 3, 2012 at 10:31 PM, Benjamin Young byo...@bigbluehat.com wrote:
If a Design Doc is what's expected as output, then I think the current
couchapp.py format has what's needed. couchapp.py itself needs further
extension to support multiple docs and attach these files to this couchdb
On 3 October 2012 20:31, Dirkjan Ochtman dirk...@ochtman.nl wrote:
On Wed, Oct 3, 2012 at 7:42 PM, Robert Newson robert.new...@gmail.com wrote:
imo, 1.3 should be bug fixes, docs and CORS, the latter being the most
at-risk.
There's also a bunch of other stuff already in the tree, right? I
On 3 October 2012 21:41, Paul Davis paul.joseph.da...@gmail.com wrote:
Only other thing I'd add is that we talked about importing Jiffy.
Good, I'd be up for that. Um did you find (in cloudant land) that it
handled parsing large docs better? The current ejson struggles
sometimes I think. Better
On Wed, Oct 3, 2012 at 3:47 PM, Dave Cottlehuber d...@jsonified.com wrote:
On 3 October 2012 21:41, Paul Davis paul.joseph.da...@gmail.com wrote:
Only other thing I'd add is that we talked about importing Jiffy.
Good, I'd be up for that. Um did you find (in cloudant land) that it
handled
I'm bringing this back up as requested. I'm currently simultaneously
in the not replicating interesting things and has duplicate replicates
state. I think the stuff below shows the not replicating stuff.
Active tasks shows the other (these are based on replicator DB
On Oct 3, 2012 10:48 PM, Dave Cottlehuber d...@jsonified.com wrote:
On 3 October 2012 21:41, Paul Davis paul.joseph.da...@gmail.com wrote:
Only other thing I'd add is that we talked about importing Jiffy.
Good, I'd be up for that. Um did you find (in cloudant land) that it
handled parsing
13 matches
Mail list logo
