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

ASF GitHub Bot commented on COUCHDB-2651:
-----------------------------------------

GitHub user robertkowalski opened a pull request:

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

    Mango: creation and listing of indexes

    Part 1/2 for Mango:
    
    Creation of Mango indexes and listing them. Disabled pagination
    and bulk-deletion for now, see:
    
    https://issues.apache.org/jira/browse/COUCHDB-2651
    https://issues.apache.org/jira/browse/COUCHDB-2652
    
    As you can't use the feature right now (querying is part 2/2)
    the buttons to reach the features are hidden behind a feature flip.
    
    Use the direct urls to access the features:
    
    http://localhost:8000/#database/$YOUR_DATABASE/_index
    http://localhost:8000/#database/$YOUR_DATABASE/_indexlist
    
    or add `?beta=showquery` to your url, e.g.
    
    http://localhost:8000/#database/$YOUR_DATABASE/?beta=showquery
    
    Additionally prepares the app for i18n.
    
    COUCHDB-2627

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

    $ git pull https://github.com/robertkowalski/couchdb-fauxton 
mango-tropical-fruits

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

    https://github.com/apache/couchdb-fauxton/pull/343.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 #343
    
----
commit 330c2585a77d03bbf7f66ebd22fd0f0ffc39836e
Author: Robert Kowalski <[email protected]>
Date:   2015-03-27T13:16:43Z

    Mango: creation and listing of indexes
    
    Part 1/2 for Mango:
    
    Creation of Mango indexes and listing them. Disabled pagination
    and bulk-deletion for now, see:
    
    https://issues.apache.org/jira/browse/COUCHDB-2651
    https://issues.apache.org/jira/browse/COUCHDB-2652
    
    As you can't use the feature right now (querying is part 2/2)
    the buttons to reach the features are hidden behind a feature flip.
    
    Use the direct urls to access the features:
    
    http://localhost:8000/#database/$YOUR_DATABASE/_index
    http://localhost:8000/#database/$YOUR_DATABASE/_indexlist
    
    or add `?beta=showquery` to your url, e.g.
    
    http://localhost:8000/#database/$YOUR_DATABASE/?beta=showquery
    
    Additionally prepares the app for i18n.
    
    COUCHDB-2627

----


> Deleting a Mango Design Docs using bulk docs
> --------------------------------------------
>
>                 Key: COUCHDB-2651
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2651
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: go
>            Reporter: Robert Kowalski
>
> In Fauxtont the user can list documents / indexes and select multiple of 
> them. The user can then press one button to delete all selected documents. 
> This works for Mango created design docs, but it is quite hard to get the 
> revision id as /_index does not list them. Current workarounds are:
> 1. firing a lot of multiple requests, but given that one doc list can have 
> 100 entries this is not a viable solution:
> curl -XGET 
> "http://localhost:8000/animaldb/_design/e4d338e5d6f047749f5399ab998b4fa04ba0c816";
> {"_id":"_design/e4d338e5d6f047749f5399ab998b4fa04ba0c816","_rev":"1-1f37105891681e717ae37dae973bc6a4","language":"query","views":{"e4d338e5d6f047749f5399ab998b4fa04ba0c816":{"map":{"fields":{"_id":"asc"}},"reduce":"_count","options":{"def":{"fields":["_id"]},"w":2}}}}
> 2. Querying all the design docs with includedocs, and don't use the _index 
> endpoint, then filter out all all indexes which are not mango indexes and use 
> the result for building the list of documents which then can get checked and 
> deleted (downside: performance, not using the existing endpoint from mango 
> which makes it a bit obsolete, at least for Fauxton)
> For me there are two possible solutions:
>  - returning the rev id in GET /_index
>  - implementing an additional POST /_bulk_index endpoint
> while I would prefer the first as the _bulk_docs endpoint already exists and 
> works very well.



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

Reply via email to