[jira] [Commented] (COUCHDB-2067) Not all rows in a non-reduced view are displayed
[ https://issues.apache.org/jira/browse/COUCHDB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1394#comment-1394 ] ASF subversion and git services commented on COUCHDB-2067: -- Commit 4e60f0b7a7b26662dde0ebc0a73c70df54e0f309 in couchdb's branch refs/heads/master from [~garren] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=4e60f0b ] Fauxton: Improved pagination This is an improvement and fix on the current pagination. This fixes pagination so that it works with all query options. Pagination in Couchdb is quite complex and there are plenty of situations to cater for. This new pagination works quite differently to the previous way we had it working for a user. A user can set the number of documents they want to view on a page. This is not related to limit options in the query options - the limit option is an overall cap of how many documents to paginate too. A limit of none is possible and is the default. If the limit option is set to 50 and a user wants 10 docs per page, the would then be able to paginate 3 pages before hitting the end. Another change is that the api url and browser url does not change when we paginate. That happens internally and hence the new addition of urlParams and docParams. This allows Fauxton to keep track of the parameters that the user sees and the parameters that the document needs to paginate. Fixes COUCHDB-2067 Not all rows in a non-reduced view are displayed Key: COUCHDB-2067 URL: https://issues.apache.org/jira/browse/COUCHDB-2067 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: James Blachly Assignee: Garren Smith When designing a view using a map function that emits multiple items, Fauxton shows only a subset of the rows from the view. I think, but have not confirmed, that it is only showing as many rows as there were source documents that emitted the rows in the view. For example, I have THREE documents of type A, each document having a list of alternate IDs, variable in length. The map function emits one or more alternate IDs per document. In my example, I have 8 rows returned from 3 documents. When looking at the view, Fauxton only shows 3 rows, but it correctly reports the total # of rows: Showing 1-3 of 8 rows.. The Next button takes you to: http://localhost:5984/_utils/fauxton/# which is putatively the list of databases, but for some reason is empty at that time (refreshing or clicking the database link to the left correctly displays the database list). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (COUCHDB-2067) Not all rows in a non-reduced view are displayed
[ https://issues.apache.org/jira/browse/COUCHDB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Garren Smith resolved COUCHDB-2067. --- Resolution: Fixed The new pagination has landed in master. This will fix this issue. Not all rows in a non-reduced view are displayed Key: COUCHDB-2067 URL: https://issues.apache.org/jira/browse/COUCHDB-2067 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: James Blachly Assignee: Garren Smith When designing a view using a map function that emits multiple items, Fauxton shows only a subset of the rows from the view. I think, but have not confirmed, that it is only showing as many rows as there were source documents that emitted the rows in the view. For example, I have THREE documents of type A, each document having a list of alternate IDs, variable in length. The map function emits one or more alternate IDs per document. In my example, I have 8 rows returned from 3 documents. When looking at the view, Fauxton only shows 3 rows, but it correctly reports the total # of rows: Showing 1-3 of 8 rows.. The Next button takes you to: http://localhost:5984/_utils/fauxton/# which is putatively the list of databases, but for some reason is empty at that time (refreshing or clicking the database link to the left correctly displays the database list). -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Fix placeholder for Username
Github user andywenk commented on the pull request: https://github.com/apache/couchdb/pull/166#issuecomment-36846369 +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-1946) Trying to replicate NPM grinds to a halt after 40GB
[ https://issues.apache.org/jira/browse/COUCHDB-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922481#comment-13922481 ] Adam Cooper commented on COUCHDB-1946: -- After hours of frustration trying to setup an npm registry with CouchDB 1.5.0, I'm glad to have found this thread to know it isn't just me. The only way I was able to replicate https://fullfatdb.npmjs.com/registry was by installing CouchDB 1.2.0. Is this the current recommendation until this bug is resolved? Thanks! Trying to replicate NPM grinds to a halt after 40GB --- Key: COUCHDB-1946 URL: https://issues.apache.org/jira/browse/COUCHDB-1946 Project: CouchDB Issue Type: Bug Components: Database Core Reporter: Marc Trudel Priority: Critical Attachments: couch.log I have been able to replicate the Node.js NPM database until 40G or so, then I get this: https://gist.github.com/stelcheck/7723362 I one case I have gotten a flat-out OOM error, but I didn't take a dump of the log output at the time. CentOS6.4 with CouchDB 1.5 (also tried 1.3.1, but to no avail). Also tried to restart replication from scratch - twice - bot cases stalling at 40GB. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2186) Views pagination implicitly applies reduce function
Alexander Shorin created COUCHDB-2186: - Summary: Views pagination implicitly applies reduce function Key: COUCHDB-2186 URL: https://issues.apache.org/jira/browse/COUCHDB-2186 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Alexander Shorin 1. Open any database 2. Click on any secondary index which has reduce function 3. Note that result isn't reduced 4. Change page size 5. Note that result now is reduced Fauxton @ [4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2187) Page size doesn't changes if view is limited with lower value
Alexander Shorin created COUCHDB-2187: - Summary: Page size doesn't changes if view is limited with lower value Key: COUCHDB-2187 URL: https://issues.apache.org/jira/browse/COUCHDB-2187 Project: CouchDB Issue Type: Bug Security Level: public (Regular issues) Components: Fauxton Reporter: Alexander Shorin 1. Open any database 2. Click Query options 3. Set limit as, say, 20 3.1 or add ?limit=20 to URL and hit Enter 4. Set page size 10 - note changes. 5. Set page size 30 - nothing changes. Try 50 and 100 too and notice that nothing changes. 6. Get back to 20 - page size now is changed. Fauxton @ [4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2187) Page size doesn't changes if view is limited with lower value
[ https://issues.apache.org/jira/browse/COUCHDB-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922542#comment-13922542 ] Alexander Shorin commented on COUCHDB-2187: --- Before close this as Wont Fix @ RTFCM note that regular users wouldn't try to figure out about reasons of such behaviour. All what they have is Fauxton interface and the situation when their lovely Page size 50 works perfectly, but one day they found it broken and no logical explanation around why so. Page size doesn't changes if view is limited with lower value - Key: COUCHDB-2187 URL: https://issues.apache.org/jira/browse/COUCHDB-2187 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin 1. Open any database 2. Click Query options 3. Set limit as, say, 20 3.1 or add ?limit=20 to URL and hit Enter 4. Set page size 10 - note changes. 5. Set page size 30 - nothing changes. Try 50 and 100 too and notice that nothing changes. 6. Get back to 20 - page size now is changed. Fauxton @ [4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b] -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2041) upgrade ibrowse to next tag
[ https://issues.apache.org/jira/browse/COUCHDB-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922580#comment-13922580 ] ASF subversion and git services commented on COUCHDB-2041: -- Commit fbb4491dd2195ad3397a457e1cee96dff9a24c88 in couchdb's branch refs/heads/2041-update-ibrowse from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=fbb4491 ] ibrowse: update to 4.0.3 - for COUCHDB-2041 - should be re-pushed with amended VSN when upstream tags a release - ibrowse sha#108c131d at 20140306 upgrade ibrowse to next tag --- Key: COUCHDB-2041 URL: https://issues.apache.org/jira/browse/COUCHDB-2041 Project: CouchDB Issue Type: Improvement Components: HTTP Interface Reporter: Dave Cottlehuber ibrowse 4.0.3 pre (as it hasn't been released yet) has a couple of useful fixes for us. This branch passes distcheck and I've asked upstream for a tagged release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Gruntfile fix more path.existsSync
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/165#issuecomment-36896992 + 1 and merged in --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Fix status messages in Active Tasks
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/164#issuecomment-36897545 I like it. +1 I think that progress will be depreciated in replication active tasks when big couch gets merged in. But I guess I'll just patch that later. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Fix status messages in Active Tasks
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/164#issuecomment-36897855 Merged in! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2123) Incorrect status message for active tasks
[ https://issues.apache.org/jira/browse/COUCHDB-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922635#comment-13922635 ] ASF subversion and git services commented on COUCHDB-2123: -- Commit abe96eb2c8f2a6fc2d8c6aec91af0676854ea598 in couchdb's branch refs/heads/master from Robert Kowalski [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=abe96eb ] Fauxton: Fix status messages in Active Tasks Show Progress, current Sequence and Changes. Fix the display of `undefined` if value is undefined. Fixes #COUCHDB-2123 Incorrect status message for active tasks - Key: COUCHDB-2123 URL: https://issues.apache.org/jira/browse/COUCHDB-2123 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Fauxton doesn't show any compaction progress like Futon does. Also it shows messages like 678 docs written. undefined pending changes. for replications while Futon is more verbose on this case: Checkpointed source sequence 3178, current source sequence 16065, progress 22% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (COUCHDB-2188) Pagination is broken if map fun emits more rows than page size is
Alexander Shorin created COUCHDB-2188:
-
Summary: Pagination is broken if map fun emits more rows than page
size is
Key: COUCHDB-2188
URL: https://issues.apache.org/jira/browse/COUCHDB-2188
Project: CouchDB
Issue Type: Bug
Security Level: public (Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
1. Create new database with single doc - his content doesn't matters
2. Create the view that emits multiple rows for single doc, like:
{code}
function(doc){
for(var i=0; i 20; i++){
emit(doc._id, i);
}
}
{code}
Yes, too synthetic, but you got the idea.
3. Try to navigate thought results with page size 5 and 10 - you'll always
browse the same content
Fauxton @
[4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (COUCHDB-2189) Request ddoc _info on demand
Alexander Shorin created COUCHDB-2189:
-
Summary: Request ddoc _info on demand
Key: COUCHDB-2189
URL: https://issues.apache.org/jira/browse/COUCHDB-2189
Project: CouchDB
Issue Type: Improvement
Security Level: public (Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
Currently if you're browsing some secondary index Fauxton polling the {{_info}}
resource every 5 seconds without significant reason for.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Assigned] (COUCHDB-2189) Request ddoc _info on demand
[
https://issues.apache.org/jira/browse/COUCHDB-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sue Lockwood reassigned COUCHDB-2189:
-
Assignee: Sue Lockwood
Request ddoc _info on demand
Key: COUCHDB-2189
URL: https://issues.apache.org/jira/browse/COUCHDB-2189
Project: CouchDB
Issue Type: Improvement
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
Assignee: Sue Lockwood
Currently if you're browsing some secondary index Fauxton polling the
{{_info}} resource every 5 seconds without significant reason for.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (COUCHDB-2188) Pagination is broken if map fun emits more rows than page size is
[
https://issues.apache.org/jira/browse/COUCHDB-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922671#comment-13922671
]
Will Holley commented on COUCHDB-2188:
--
This sounds like it is not fixable using the pagination algorithm that uses
startkey / startkey_docid to iterate through the result set. I can only think
that in this case we'd have to use skip as a fallback in the case where the
returned results are exactly the same as the current page?
Pagination is broken if map fun emits more rows than page size is
-
Key: COUCHDB-2188
URL: https://issues.apache.org/jira/browse/COUCHDB-2188
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
1. Create new database with single doc - his content doesn't matters
2. Create the view that emits multiple rows for single doc, like:
{code}
function(doc){
for(var i=0; i 20; i++){
emit(doc._id, i);
}
}
{code}
Yes, too synthetic, but you got the idea.
3. Try to navigate thought results with page size 5 and 10 - you'll always
browse the same content
Fauxton @
[4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (COUCHDB-2188) Pagination is broken if map fun emits more rows than page size is
[
https://issues.apache.org/jira/browse/COUCHDB-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922676#comment-13922676
]
Garren Smith commented on COUCHDB-2188:
---
I think we will have to have a fallback to check the pagination results. We
could even just check the first and the last and see if they the same as the
current page. If so do a skip=perPage
Pagination is broken if map fun emits more rows than page size is
-
Key: COUCHDB-2188
URL: https://issues.apache.org/jira/browse/COUCHDB-2188
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
1. Create new database with single doc - his content doesn't matters
2. Create the view that emits multiple rows for single doc, like:
{code}
function(doc){
for(var i=0; i 20; i++){
emit(doc._id, i);
}
}
{code}
Yes, too synthetic, but you got the idea.
3. Try to navigate thought results with page size 5 and 10 - you'll always
browse the same content
Fauxton @
[4e60f0b|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=4e60f0b]
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Fix placeholder for Username
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/166 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Gruntfile fix more path.existsSync
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/165 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Fix status messages in Active Tasks
Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/164 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2123) Incorrect status message for active tasks
[ https://issues.apache.org/jira/browse/COUCHDB-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922699#comment-13922699 ] ASF GitHub Bot commented on COUCHDB-2123: - Github user robertkowalski closed the pull request at: https://github.com/apache/couchdb/pull/164 Incorrect status message for active tasks - Key: COUCHDB-2123 URL: https://issues.apache.org/jira/browse/COUCHDB-2123 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Fauxton doesn't show any compaction progress like Futon does. Also it shows messages like 678 docs written. undefined pending changes. for replications while Futon is more verbose on this case: Checkpointed source sequence 3178, current source sequence 16065, progress 22% -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Fix error if anon. user tries to cr...
GitHub user robertkowalski opened a pull request: https://github.com/apache/couchdb/pull/167 Fauxton: Fix error if anon. user tries to create Admins This fixes the error message if people try to create an admin without being an admin. I also DRY'd up the code a little bit and I am using the server response here instead of duplicating it. But there are still some errorstrings needed on the clientside, e.g. for the immediate validations on the client. I am happy to rebase/squash, if you want me to. You can merge this pull request into a Git repository by running: $ git pull https://github.com/robertkowalski/couchdb COUCHDB-2170/admin-anonymous-user Alternatively you can review and apply these changes as the patch at: https://github.com/apache/couchdb/pull/167.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 #167 commit aab1d7046bd1473a4671d1b95e926292f7aa4288 Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-06T16:23:34Z Fauxton: Fix error if anon. user tries to create Admins Fixes #COUCHDB-2170 commit 9a61a5eb718c928a2cb3998b7e353287562d18bf Author: Robert Kowalski r...@kowalski.gd Date: 2014-03-06T16:24:46Z Fauxton: dry up promise error callbacks --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Fix error if anon. user tries to cr...
Github user garrensmith commented on the pull request: https://github.com/apache/couchdb/pull/167#issuecomment-36906752 +1, thanks for the contribution. I think @deathbearbrown can squash when merging. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (COUCHDB-2170) Weird error if anonymous user will try to create new admin
[
https://issues.apache.org/jira/browse/COUCHDB-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13922726#comment-13922726
]
ASF subversion and git services commented on COUCHDB-2170:
--
Commit b63ff1b50b7bde0c8f1f95988d076dda63f41fed in couchdb's branch
refs/heads/master from Robert Kowalski
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=b63ff1b ]
Fauxton: dry up promise error callbacks
Fauxton: Fix error if anon. user tries to create Admins
Fixes #COUCHDB-2170
Weird error if anonymous user will try to create new admin
--
Key: COUCHDB-2170
URL: https://issues.apache.org/jira/browse/COUCHDB-2170
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
Assignee: Sue Lockwood
When admin party is fixed and anonymous user trying to create new admin he'll
get the next error: {{Could not create admin. Reason[object Object].}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Fix error if anon. user tries to cr...
Github user deathbearbrown commented on the pull request: https://github.com/apache/couchdb/pull/167#issuecomment-36907478 squashed and merged, but thanks for offering to squash for me :) :+1: --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[GitHub] couchdb pull request: Fauxton: Fix error if anon. user tries to cr...
Github user kxepal commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/167#discussion_r10349367
--- Diff: src/fauxton/app/addons/auth/resources.js ---
@@ -20,6 +20,18 @@ function (app, FauxtonAPI, CouchdbSession) {
var Auth = new FauxtonAPI.addon();
+ var promiseErrorHandler = function (xhr, type, msg) {
+msg = xhr;
--- End diff --
mmm..why assign first argument to the third one?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Created] (COUCHDB-2190) Allow skip to be negative
Ivan Erceg created COUCHDB-2190: --- Summary: Allow skip to be negative Key: COUCHDB-2190 URL: https://issues.apache.org/jira/browse/COUCHDB-2190 Project: CouchDB Issue Type: Improvement Security Level: public (Regular issues) Components: HTTP Interface Reporter: Ivan Erceg I propose to allow skip to be a negative value in order to minimise the number of requests and/or the amount of data that has to be retrieved. An example: I have a key for a reduce and I want to find the next and the previous keys in a single request. If skip was allowed to be negative I could make a query with skip -1 and limit +3 thus retrieving the previous, the current and the next keys. I for one can't think of an alternative solution (though I'm a relative newbie in CouchDb) that would allow to do this in a single request. Considering how skip works (if I understand it correctly), there shouldn't be any technical impediment to search the B-tree for the given key, take one (or more) steps back (in the same way we take them forward for skip 0) and then retrieve the data from there. -- This message was sent by Atlassian JIRA (v6.2#6252)
[GitHub] couchdb pull request: Fauxton: Fix error if anon. user tries to cr...
Github user garrensmith commented on a diff in the pull request:
https://github.com/apache/couchdb/pull/167#discussion_r10351608
--- Diff: src/fauxton/app/addons/auth/resources.js ---
@@ -20,6 +20,18 @@ function (app, FauxtonAPI, CouchdbSession) {
var Auth = new FauxtonAPI.addon();
+ var promiseErrorHandler = function (xhr, type, msg) {
+msg = xhr;
--- End diff --
@kxepal, Sometimes the arguments passed to this function is just one that
is a message. So instead of doing an if else statemebt.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
Re: Planet CouchDB
Yup, it’s Sam Ruby’s Venus running on one of my boxes. I can’t give you access to it, but I can put up the config in git and deploy changes as they come in. We can also totally just run this on ASF infra, if we get it provisioned, I’ll help with the migration and everything :) Best Jan -- On 03 Mar 2014, at 02:52 , Paul Davis paul.joseph.da...@gmail.com wrote: As far as I know that was always just something that Jan ran personally. As for posting there, I don't think that's how it works. AFAIK it was just an RSS/Atom aggregator. On Sun, Mar 2, 2014 at 3:48 PM, Andy Wenk a...@nms.de wrote: Hi Jan, the marketing team would like to reactivate planet.couchdb.org. What is the process to post there? Can you give some short instructions? Here's the initial post from you (thanks Alex for searching) : http://mail-archives.apache.org/mod_mbox/couchdb-dev/200807.mbox/%3C3A2D7AF0-7BB0-4AC0-8AD8-86FF43C42E1F%40apache.org%3E Thanks a lot :) Cheers Andy -- Andy Wenk Hamburg - Germany RockIt! http://www.couchdb-buch.de http://www.pg-praxisbuch.de GPG fingerprint: C044 8322 9E12 1483 4FEC 9452 B65D 6BE3 9ED3 9588 https://people.apache.org/keys/committer/andywenk.asc signature.asc Description: Message signed with OpenPGP using GPGMail
[jira] [Commented] (COUCHDB-2170) Weird error if anonymous user will try to create new admin
[
https://issues.apache.org/jira/browse/COUCHDB-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923097#comment-13923097
]
ASF subversion and git services commented on COUCHDB-2170:
--
Commit b63ff1b50b7bde0c8f1f95988d076dda63f41fed in couchdb's branch
refs/heads/2128-autocomplete-section-name from Robert Kowalski
[ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=b63ff1b ]
Fauxton: dry up promise error callbacks
Fauxton: Fix error if anon. user tries to create Admins
Fixes #COUCHDB-2170
Weird error if anonymous user will try to create new admin
--
Key: COUCHDB-2170
URL: https://issues.apache.org/jira/browse/COUCHDB-2170
Project: CouchDB
Issue Type: Bug
Security Level: public(Regular issues)
Components: Fauxton
Reporter: Alexander Shorin
Assignee: Sue Lockwood
When admin party is fixed and anonymous user trying to create new admin he'll
get the next error: {{Could not create admin. Reason[object Object].}}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (COUCHDB-2123) Incorrect status message for active tasks
[ https://issues.apache.org/jira/browse/COUCHDB-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923096#comment-13923096 ] ASF subversion and git services commented on COUCHDB-2123: -- Commit abe96eb2c8f2a6fc2d8c6aec91af0676854ea598 in couchdb's branch refs/heads/2128-autocomplete-section-name from Robert Kowalski [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=abe96eb ] Fauxton: Fix status messages in Active Tasks Show Progress, current Sequence and Changes. Fix the display of `undefined` if value is undefined. Fixes #COUCHDB-2123 Incorrect status message for active tasks - Key: COUCHDB-2123 URL: https://issues.apache.org/jira/browse/COUCHDB-2123 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: Alexander Shorin Fauxton doesn't show any compaction progress like Futon does. Also it shows messages like 678 docs written. undefined pending changes. for replications while Futon is more verbose on this case: Checkpointed source sequence 3178, current source sequence 16065, progress 22% -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2041) upgrade ibrowse to next tag
[ https://issues.apache.org/jira/browse/COUCHDB-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923300#comment-13923300 ] ASF subversion and git services commented on COUCHDB-2041: -- Commit 948e7d9a66741b8178b154f3445620ee59ad28c1 in couchdb's branch refs/heads/2041-update-ibrowse from [~dch] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=948e7d9 ] ibrowse: update to 4.0.3 - for COUCHDB-2041 - should be re-pushed with amended VSN when upstream tags a release - ibrowse sha#108c131d at 20140306 upgrade ibrowse to next tag --- Key: COUCHDB-2041 URL: https://issues.apache.org/jira/browse/COUCHDB-2041 Project: CouchDB Issue Type: Improvement Components: HTTP Interface Reporter: Dave Cottlehuber ibrowse 4.0.3 pre (as it hasn't been released yet) has a couple of useful fixes for us. This branch passes distcheck and I've asked upstream for a tagged release. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (COUCHDB-2067) Not all rows in a non-reduced view are displayed
[ https://issues.apache.org/jira/browse/COUCHDB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923299#comment-13923299 ] ASF subversion and git services commented on COUCHDB-2067: -- Commit 4e60f0b7a7b26662dde0ebc0a73c70df54e0f309 in couchdb's branch refs/heads/2041-update-ibrowse from [~garren] [ https://git-wip-us.apache.org/repos/asf?p=couchdb.git;h=4e60f0b ] Fauxton: Improved pagination This is an improvement and fix on the current pagination. This fixes pagination so that it works with all query options. Pagination in Couchdb is quite complex and there are plenty of situations to cater for. This new pagination works quite differently to the previous way we had it working for a user. A user can set the number of documents they want to view on a page. This is not related to limit options in the query options - the limit option is an overall cap of how many documents to paginate too. A limit of none is possible and is the default. If the limit option is set to 50 and a user wants 10 docs per page, the would then be able to paginate 3 pages before hitting the end. Another change is that the api url and browser url does not change when we paginate. That happens internally and hence the new addition of urlParams and docParams. This allows Fauxton to keep track of the parameters that the user sees and the parameters that the document needs to paginate. Fixes COUCHDB-2067 Not all rows in a non-reduced view are displayed Key: COUCHDB-2067 URL: https://issues.apache.org/jira/browse/COUCHDB-2067 Project: CouchDB Issue Type: Bug Security Level: public(Regular issues) Components: Fauxton Reporter: James Blachly Assignee: Garren Smith When designing a view using a map function that emits multiple items, Fauxton shows only a subset of the rows from the view. I think, but have not confirmed, that it is only showing as many rows as there were source documents that emitted the rows in the view. For example, I have THREE documents of type A, each document having a list of alternate IDs, variable in length. The map function emits one or more alternate IDs per document. In my example, I have 8 rows returned from 3 documents. When looking at the view, Fauxton only shows 3 rows, but it correctly reports the total # of rows: Showing 1-3 of 8 rows.. The Next button takes you to: http://localhost:5984/_utils/fauxton/# which is putatively the list of databases, but for some reason is empty at that time (refreshing or clicking the database link to the left correctly displays the database list). -- This message was sent by Atlassian JIRA (v6.2#6252)
