ASF GitHub Bot (JIRA | 22 Apr 21:52 2014
Picon

[jira] [Commented] (COUCHDB-2136) Group log messages by date


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

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

Github user robertkowalski commented on a diff in the pull request:

    https://github.com/apache/couchdb/pull/214#discussion_r11872399

    --- Diff: src/fauxton/app/addons/logs/templates/dashboard.html ---
     <at>  <at>  -17,7 +17,7  <at>  <at> 
       <table class="table table-bordered log-table">
         <thead>
           <tr>
    -        <th class="date">Date</th>
    +        <th class="time">Date</th>
    --- End diff --

    But I am not using it in the JS

> Group log messages by date
> --------------------------
>
>                 Key: COUCHDB-2136
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2136
>             Project: CouchDB
>          Issue Type: Improvement
(Continue reading)

Nolan Lawson (JIRA | 22 Apr 01:06 2014
Picon

[jira] [Commented] (COUCHDB-2227) Feature request: _all_docs?exclude_ddocs=true


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

Nolan Lawson commented on COUCHDB-2227:
---------------------------------------

For a generic exclude operation, how about something like {{exclude_range=\[startkey, endkey]}}? It
would work for all three of \_changes, \_view, and \_all\_docs.  Then our {{include_ddocs=false}} would
just become {{exclude_range=\["design_", "design/"]}}, which is still kinda gnarly, but at least it
doesn't require two separate requests.  And it might have uses beyond excluding ddocs.

> Feature request: _all_docs?exclude_ddocs=true
> ---------------------------------------------
>
>                 Key: COUCHDB-2227
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2227
>             Project: CouchDB
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>            Priority: Minor
>
> Design docs are included in {{\_all_docs}} results, which is by design (hyuk hyuk).  However, this can be
surprising and unwanted behavior for new users, and plus, sometimes it's tricky to exclude them, e.g. if
your docids come both before and after the {{_}} character:
> {code:javascript}
> {"total_rows":6,"offset":0,"rows":[
(Continue reading)

Robert Newson (JIRA | 21 Apr 21:10 2014
Picon

[jira] [Commented] (COUCHDB-2227) Feature request: _all_docs?exclude_ddocs=true


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

Robert Newson commented on COUCHDB-2227:
----------------------------------------

to answer [~wohali]'s question, the only constraint for doc ids is that they're not empty and are valid
UTF-8. Database names are constrained to lowercase.

> Feature request: _all_docs?exclude_ddocs=true
> ---------------------------------------------
>
>                 Key: COUCHDB-2227
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2227
>             Project: CouchDB
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>            Priority: Minor
>
> Design docs are included in {{\_all_docs}} results, which is by design (hyuk hyuk).  However, this can be
surprising and unwanted behavior for new users, and plus, sometimes it's tricky to exclude them, e.g. if
your docids come both before and after the {{_}} character:
> {code:javascript}
> {"total_rows":6,"offset":0,"rows":[
> {"id":"Bar","key":"Bar","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
> {"id":"Foo","key":"Foo","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
(Continue reading)

Robert Newson (JIRA | 21 Apr 21:08 2014
Picon

[jira] [Commented] (COUCHDB-2227) Feature request: _all_docs?exclude_ddocs=true


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

Robert Newson commented on COUCHDB-2227:
----------------------------------------

Bit of an odd request or, at least, an overly specific one. _all_docs is basically a view keyed on doc._id, so
it would a conspicuous absence if one couldn't omit some rows from a view too. Since you can achieve the
desired effect of this ticket with a list function, this is a Won't Fix, I think. At most, some exclude=
parameter that works for _all_docs, _changes *and* views would be a useful addition, on the reasonable
assumption that it would operate far faster than a list function (since it doesn't require a couchjs
roundtrip) and would not require coding a design doc.

> Feature request: _all_docs?exclude_ddocs=true
> ---------------------------------------------
>
>                 Key: COUCHDB-2227
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2227
>             Project: CouchDB
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>            Priority: Minor
>
> Design docs are included in {{\_all_docs}} results, which is by design (hyuk hyuk).  However, this can be
surprising and unwanted behavior for new users, and plus, sometimes it's tricky to exclude them, e.g. if
your docids come both before and after the {{_}} character:
(Continue reading)

Nolan Lawson (JIRA | 21 Apr 19:56 2014
Picon

[jira] [Commented] (COUCHDB-2227) Feature request: _all_docs?exclude_ddocs=true


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

Nolan Lawson commented on COUCHDB-2227:
---------------------------------------

Thanks, {{include_ddocs}} would be awesome. Even without doc IDs containing capital letters, the sugar
is really nice.

> Feature request: _all_docs?exclude_ddocs=true
> ---------------------------------------------
>
>                 Key: COUCHDB-2227
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2227
>             Project: CouchDB
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: HTTP Interface
>            Reporter: Nolan Lawson
>            Priority: Minor
>
> Design docs are included in {{\_all_docs}} results, which is by design (hyuk hyuk).  However, this can be
surprising and unwanted behavior for new users, and plus, sometimes it's tricky to exclude them, e.g. if
your docids come both before and after the {{_}} character:
> {code:javascript}
> {"total_rows":6,"offset":0,"rows":[
> {"id":"Bar","key":"Bar","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
> {"id":"Foo","key":"Foo","value":{"rev":"1-967a00dff5e02add41819138abb3284d"}},
(Continue reading)

Dawid Jańczak (JIRA | 21 Apr 18:15 2014
Picon

[jira] [Resolved] (COUCHDB-2229) CouchDB not starting on icu 53


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

Dawid Jańczak resolved COUCHDB-2229.
------------------------------------

    Resolution: Not a Problem

> CouchDB not starting on icu 53
> ------------------------------
>
>                 Key: COUCHDB-2229
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2229
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Dawid Jańczak
>
> CouchDB version: 1.5.1
> icu version: 53.1
> system: Linux 3.14.1-1-ARCH
> CouchDB won't start after upgrading icu to 53.1:
> {"init terminating in
do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,collation_driver,"libicui18n.so.52:
cannot open shared object file: No such file or directory"}}}}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,272}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}

--
This message was sent by Atlassian JIRA
(Continue reading)

Dawid Jańczak (JIRA | 21 Apr 18:15 2014
Picon

[jira] [Commented] (COUCHDB-2229) CouchDB not starting on icu 53


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

Dawid Jańczak commented on COUCHDB-2229:
----------------------------------------

Yes, reinstalling CouchDB fixed it. Thanks!

> CouchDB not starting on icu 53
> ------------------------------
>
>                 Key: COUCHDB-2229
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2229
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Dawid Jańczak
>
> CouchDB version: 1.5.1
> icu version: 53.1
> system: Linux 3.14.1-1-ARCH
> CouchDB won't start after upgrading icu to 53.1:
> {"init terminating in
do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,collation_driver,"libicui18n.so.52:
cannot open shared object file: No such file or directory"}}}}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,272}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}

--
(Continue reading)

Alexander Shorin (JIRA | 21 Apr 18:05 2014
Picon

[jira] [Commented] (COUCHDB-2229) CouchDB not starting on icu 53


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

Alexander Shorin commented on COUCHDB-2229:
-------------------------------------------

The error explicitly tells:
{{libicui18n.so.52: cannot open shared object file: No such file or directory}}
The 52 in filename tail looks as the version against which CouchDB was compiled. Since you have 53.1 now,
have you tried to recompile CouchDB?

> CouchDB not starting on icu 53
> ------------------------------
>
>                 Key: COUCHDB-2229
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2229
>             Project: CouchDB
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Database Core
>            Reporter: Dawid Jańczak
>
> CouchDB version: 1.5.1
> icu version: 53.1
> system: Linux 3.14.1-1-ARCH
> CouchDB won't start after upgrading icu to 53.1:
> {"init terminating in
do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,collation_driver,"libicui18n.so.52:
(Continue reading)

Sebastian Rothbucher (JIRA | 21 Apr 17:57 2014
Picon

[jira] [Updated] (COUCHDB-2228) Allow filtering views, follow linked docs, application of show functions in Futon


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

Sebastian Rothbucher updated COUCHDB-2228:
------------------------------------------

    Component/s: Fauxton

> Allow filtering views, follow linked docs, application of show functions in Futon
> ---------------------------------------------------------------------------------
>
>                 Key: COUCHDB-2228
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2228
>             Project: CouchDB
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Fauxton, Futon
>            Reporter: Sebastian Rothbucher
>         Attachments: show1.png, show2.png, view1.png, view2.png, view3.png
>
>
> I did some improvements in Futon to do just that: one can filter a view for the start of the key (input the
start value, press enter, pretty similar to "jump to document"). 
> Plus: When a view value contains "_id" (a linked document), double clicking the right column jumps to the
linked document instead of the source document (aka doc._id). 
> Finally (as soon as at least one is actually available) a dropdown of show functions is displayed and the
JSON from the show function is rendered read-only once chosen (it's far away from COUCHDB-2047 but maybe
still helpful)
> Replacing the files (at least the five I touched) in the www folder of an existing couchdb should be
(Continue reading)

Dawid Jańczak (JIRA | 21 Apr 17:57 2014
Picon

[jira] [Created] (COUCHDB-2229) CouchDB not starting on icu 53

Dawid Jańczak created COUCHDB-2229:
--------------------------------------

             Summary: CouchDB not starting on icu 53
                 Key: COUCHDB-2229
                 URL: https://issues.apache.org/jira/browse/COUCHDB-2229
             Project: CouchDB
          Issue Type: Bug
      Security Level: public (Regular issues)
          Components: Database Core
            Reporter: Dawid Jańczak

CouchDB version: 1.5.1
icu version: 53.1
system: Linux 3.14.1-1-ARCH

CouchDB won't start after upgrading icu to 53.1:
{"init terminating in
do_boot",{{badmatch,{error,{bad_return,{{couch_app,start,[normal,["/etc/couchdb/default.ini","/etc/couchdb/local.ini"]]},{'EXIT',{{badmatch,{error,{shutdown,{failed_to_start_child,couch_primary_services,{shutdown,{failed_to_start_child,collation_driver,"libicui18n.so.52:
cannot open shared object file: No such file or directory"}}}}}},[{couch_server_sup,start_server,1,[{file,"couch_server_sup.erl"},{line,98}]},{application_master,start_it_old,4,[{file,"application_master.erl"},{line,272}]}]}}}}}},[{couch,start,0,[{file,"couch.erl"},{line,18}]},{init,start_it,1,[]},{init,start_em,1,[]}]}}

--
This message was sent by Atlassian JIRA
(v6.2#6252)

Sebastian Rothbucher (JIRA | 21 Apr 17:55 2014
Picon

[jira] [Commented] (COUCHDB-2228) Allow filtering views, follow linked docs, application of show functions in Futon


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

Sebastian Rothbucher commented on COUCHDB-2228:
-----------------------------------------------

Hi Alexander, bad timing indeed - but give me a little time, I'll give it a shot in fauxtron also.

> Allow filtering views, follow linked docs, application of show functions in Futon
> ---------------------------------------------------------------------------------
>
>                 Key: COUCHDB-2228
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2228
>             Project: CouchDB
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: Futon
>            Reporter: Sebastian Rothbucher
>         Attachments: show1.png, show2.png, view1.png, view2.png, view3.png
>
>
> I did some improvements in Futon to do just that: one can filter a view for the start of the key (input the
start value, press enter, pretty similar to "jump to document"). 
> Plus: When a view value contains "_id" (a linked document), double clicking the right column jumps to the
linked document instead of the source document (aka doc._id). 
> Finally (as soon as at least one is actually available) a dropdown of show functions is displayed and the
JSON from the show function is rendered read-only once chosen (it's far away from COUCHDB-2047 but maybe
still helpful)
(Continue reading)


Gmane