Lena Reinhard | 27 Jan 20:21 2015
Jan Lehnardt (JIRA | 27 Jan 14:00 2015
Picon

[jira] [Commented] (COUCHDB-2310) Add a bulk API for revs & open_revs


    [
https://issues.apache.org/jira/browse/COUCHDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293463#comment-14293463
] 

Jan Lehnardt commented on COUCHDB-2310:
---------------------------------------

Cool, thanks, no worries :) — Also feel free to post incomplete stuff, happy to pick it up.

> Add a bulk API for revs & open_revs
> -----------------------------------
>
>                 Key: COUCHDB-2310
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2310
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>
> CouchDB replication is too slow.
> And what makes it so slow is that it's just so unnecessarily chatty. During replication, you have to do a
separate GET for each individual document, in order to get the full {{_revisions}} object for that
document (using the {{revs}} and {{open_revs}} parameters – refer to [the TouchDB
writeup|https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithm] or
[Benoit's writeup|http://dataprotocols.org/couchdb-replication/] if you need a refresher).
> So for example, let's say you've got a database full of 10,000 documents, and you replicate using a batch
size of 500 (batch sizes are configurable in PouchDB). The conversation for a single batch basically
looks like this:
(Continue reading)

Benoit Chesneau (JIRA | 27 Jan 13:58 2015
Picon

[jira] [Commented] (COUCHDB-2310) Add a bulk API for revs & open_revs


    [
https://issues.apache.org/jira/browse/COUCHDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293459#comment-14293459
] 

Benoit Chesneau commented on COUCHDB-2310:
------------------------------------------

sorry i have been horribly busy last week. But I will make sure to make the patch available until friday :)

> Add a bulk API for revs & open_revs
> -----------------------------------
>
>                 Key: COUCHDB-2310
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2310
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>
> CouchDB replication is too slow.
> And what makes it so slow is that it's just so unnecessarily chatty. During replication, you have to do a
separate GET for each individual document, in order to get the full {{_revisions}} object for that
document (using the {{revs}} and {{open_revs}} parameters – refer to [the TouchDB
writeup|https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithm] or
[Benoit's writeup|http://dataprotocols.org/couchdb-replication/] if you need a refresher).
> So for example, let's say you've got a database full of 10,000 documents, and you replicate using a batch
size of 500 (batch sizes are configurable in PouchDB). The conversation for a single batch basically
looks like this:
(Continue reading)

Jan Lehnardt (JIRA | 27 Jan 13:54 2015
Picon

[jira] [Commented] (COUCHDB-2310) Add a bulk API for revs & open_revs


    [
https://issues.apache.org/jira/browse/COUCHDB-2310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293450#comment-14293450
] 

Jan Lehnardt commented on COUCHDB-2310:
---------------------------------------

[~benoitc] any news? :)

> Add a bulk API for revs & open_revs
> -----------------------------------
>
>                 Key: COUCHDB-2310
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2310
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>
> CouchDB replication is too slow.
> And what makes it so slow is that it's just so unnecessarily chatty. During replication, you have to do a
separate GET for each individual document, in order to get the full {{_revisions}} object for that
document (using the {{revs}} and {{open_revs}} parameters – refer to [the TouchDB
writeup|https://github.com/couchbaselabs/TouchDB-iOS/wiki/Replication-Algorithm] or
[Benoit's writeup|http://dataprotocols.org/couchdb-replication/] if you need a refresher).
> So for example, let's say you've got a database full of 10,000 documents, and you replicate using a batch
size of 500 (batch sizes are configurable in PouchDB). The conversation for a single batch basically
looks like this:
(Continue reading)

garrensmith | 27 Jan 12:06 2015
Picon

[GitHub] couchdb-fauxton pull request: CORS configuration

GitHub user garrensmith opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/250

    CORS configuration

    CORS configuration in the config section. I've kept it to the simplest settings required for a user to
enable and use CORS.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/garrensmith/couchdb-fauxton CORS

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/250.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #250

----
commit 29f371f85e15d7a9721e68bf8e6aa789b37804d3
Author: Christian Hogan <github@...>
Date:   2014-11-28T18:19:13Z

    Initial add CORS to Fauxton

commit aee2e8fd16df433f6258c262543bb740c5929580
(Continue reading)

Michelle Phung (JIRA | 26 Jan 22:42 2015
Picon

[jira] [Closed] (COUCHDB-2521) Can't scroll on side bar


     [
https://issues.apache.org/jira/browse/COUCHDB-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Phung closed COUCHDB-2521.
-----------------------------------
    Resolution: Fixed

this has been fixed

> Can't scroll on side bar
> ------------------------
>
>                 Key: COUCHDB-2521
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2521
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michelle Phung
>         Attachments: Screen Shot 2014-12-18 at 11.48.36 PM.png
>
>
> Can't scroll down side bar if you have a long list of views. 

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

(Continue reading)

Michelle Phung (JIRA | 26 Jan 22:41 2015
Picon

[jira] [Updated] (COUCHDB-2559) Disabled Page Navigation Instead of No Page Navigation, on one page


     [
https://issues.apache.org/jira/browse/COUCHDB-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michelle Phung updated COUCHDB-2559:
------------------------------------
    Priority: Minor  (was: Major)

> Disabled Page Navigation Instead of No Page Navigation, on one page
> -------------------------------------------------------------------
>
>                 Key: COUCHDB-2559
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2559
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Fauxton
>            Reporter: Michelle Phung
>            Priority: Minor
>
> When a user only has a handful of databases, and there is no pagination is required, the pagination footer
still shows up, but disabled. It probably shouldn't show up at all when there aren't more pages to navigate.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Michelle Phung (JIRA | 26 Jan 22:39 2015
Picon

[jira] [Created] (COUCHDB-2559) Disabled Page Navigation Instead of No Page Navigation, on one page

Michelle Phung created COUCHDB-2559:
---------------------------------------

             Summary: Disabled Page Navigation Instead of No Page Navigation, on one page
                 Key: COUCHDB-2559
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2559
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Fauxton
            Reporter: Michelle Phung

When a user only has a handful of databases, and there is no pagination is required, the pagination footer
still shows up, but disabled. It probably shouldn't show up at all when there aren't more pages to navigate.

--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jan Lehnardt | 26 Jan 20:13 2015
Picon

[QUESTION] Importing a project from GitHub

Dear Incubator,

(if this isn’t the right list to ask this, please direct be to the correct place).

The CouchDB community was approached by the lead developer of https://github.com/dscape/nano to have
the project become apart of Apache CouchDB. The community has voiced some interest in pursuing this.
There has not been a vote on this yet, though, this is just to clear any preliminary concerns.

Is there a precedent for importing GitHub projects to the ASF?

In particular, how do we handle the GitHub-usual main-dev-team + lots of drive-by-contrbutors without a
clear copyright assignment step in place?

While the lead developer and copyright holder as per the projects README.md has made the most significant
contributions (412 commits / 41,036++ / 39,540--), some of the other contributors have
not-insignificant (double negative alert!) contributions (17 commits / 613++ / 53--, e.g., see
https://github.com/dscape/nano/graphs/contributors for details).

As per ASF requirements, is the lead developer in a position to donate the project as a whole to the ASF?

Which, if any, of the other contributors will have to co-sign the donation? Or put their contributions
under an ICLA of their own? Or what other things need to be done?

FWIW, the second most prolific contributor expressed interest in moving to the ASF with the project, all
legalities covered. The rest are pretty much inactive at this point, or have only made insignificant
contributions, that were clearly meant to be included in the main project.

* * *

My understanding is that getting the main contributors / active maintainers to do a software grant and/or
(Continue reading)

robertkowalski | 26 Jan 16:54 2015
Picon

[GitHub] couchdb-fauxton pull request: changes: always remove filter tab

GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/249

    changes: always remove filter tab

    remove filtertab when switching from changes to "All Documents"

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton filter-control

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/249.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #249

----
commit a2a57b1deb06c7977ba0ee6aaa442f95dc69912f
Author: Robert Kowalski <robertkowalski@...>
Date:   2015-01-26T14:57:17Z

    changes: always remove filter tab

    remove filtertab when switching from changes to "All Documents"

(Continue reading)

robertkowalski | 26 Jan 15:39 2015
Picon

[GitHub] couchdb-fauxton pull request: db-list: display last element on pag...

GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/248

    db-list: display last element on page

    it got hidden on firefox & ie, now it works on all browsers

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton db-list-hidden-firefox

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/248.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #248

----
commit 9b749d4e395e658fd5d83fe2a77c17432255103a
Author: Robert Kowalski <robertkowalski@...>
Date:   2015-01-26T14:16:41Z

    db-list: display last element on page

    it got hidden on firefox & ie, now it works on all browsers

(Continue reading)


Gmane