[jira] [Updated] (COUCHDB-812) implement randomization in views resultset
[
https://issues.apache.org/jira/browse/COUCHDB-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Bailly updated COUCHDB-812:
---
Labels: merge rcouch (was: )
> implement randomization in views resultset
> --
>
> Key: COUCHDB-812
> URL: https://issues.apache.org/jira/browse/COUCHDB-812
> Project: CouchDB
> Issue Type: Wish
> Components: Database Core
>Affects Versions: 0.11
> Environment: CouchDB
>Reporter: Mickael Bailly
>Priority: Minor
> Labels: merge, rcouch
>
> This is a proposal for a new feature in CouchDB : allow a randomization of
> rows in a view response. We can for example add a randomize query parameter...
> This request would probably not return the same results for the same request.
> As an example :
> GET /db/_design/doc/_view/example :
> {
> ..
> rows: [
> {key: 1 ...},
> {key: 2 ...},
> {key: 3 ...}
> ]
> }
> GET /db/_design/doc/_view/example?randomize=true :
> {
> ..
> rows: [
> {key: 2 ...},
> {key: 3 ...},
> {key: 1 ...}
> ]
> }
> GET /db/_design/doc/_view/example?randomize=true :
> {
> ..
> rows: [
> {key: 1 ...},
> {key: 3 ...},
> {key: 2 ...}
> ]
> }
> This is a feature hard to implement client-side (but by reading all doc ids
> and use client-side random function). It's implemented by the RDBMS from
> ages, probably for the very same reasons : if we should read all the rows
> client-side to random-select some of them, performances are awful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (COUCHDB-792) Bespin integrated in Futon views editor
[
https://issues.apache.org/jira/browse/COUCHDB-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932004#action_12932004
]
Mickael Bailly commented on COUCHDB-792:
I suggest to report this integration, because of the current rewrite of futon
by Mikeal & the changes inside bespin project (now skywriter). Let's wait for
those things to stabilize first.
> Bespin integrated in Futon views editor
> ---
>
> Key: COUCHDB-792
> URL: https://issues.apache.org/jira/browse/COUCHDB-792
> Project: CouchDB
> Issue Type: New Feature
> Components: Futon
> Environment: HTML5 / Javascript
>Reporter: Mickael Bailly
>Priority: Minor
> Fix For: 1.2
>
> Attachments: futon-bespin.patch.gz
>
>
> Here is the "less-intrusive-I-can" patch to enable bespin editor in Futon
> database views page.
> Implementation constraints :
> - bespin can't have multiple instances
> - bespin can't be enabled=>disabled=>enabled
> I also met a bug on Google Chrome because CouchDB doesn't set a charset in
> HTTP response headers for database.html ... As a result I only succeded with
> BespinEmbedded 0.7.1.
> Implementation details :
> - created proxy functions to get and set map/reduce code to/from editor (
> instead of $("#viewcode_map").val() ... )
> - created bespin wrapper class
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-934) inside a design doc, a broken view makes all others views fail
inside a design doc, a broken view makes all others views fail
--
Key: COUCHDB-934
URL: https://issues.apache.org/jira/browse/COUCHDB-934
Project: CouchDB
Issue Type: Improvement
Components: Database Core
Affects Versions: 1.0.1
Environment: All
Reporter: Mickael Bailly
Priority: Minor
If a design document got a broken view, all other views don't work anymore.
Steps to reproduce :
1/ create a new database
2/ Create a design doc :
{
"_id": "_design/doc1",
"views": {
"v1": {
"map": "function() {}"
},
"v2": {
"map": "thefunction() {}"
}
},
"language": "javascript"
}
3/ Create a doc :
{
"_id": "doc1"
}
4/ Call the "v1" view
It's annoying because :
- we're unable to know what view fails to run
- a fix on the broken view will result in the rebuilding of all other views of
the design doc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-812) implement randomization in views resultset
[
https://issues.apache.org/jira/browse/COUCHDB-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883200#action_12883200
]
Mickael Bailly commented on COUCHDB-812:
I _of course_ disagree with your point of view. The random ordering of results
is implemented by any mainstream rdbms (mysql, postgresql, mssqlserver, oracle,
db2...). Don't think it's for "niche" use cases. The "static random" views that
I can use only once isn't even applicable in my particular app.
Of course, you decide, and I respect couch devs decisions, but I find the "not
interesting" flagging of this feature a little fast :-)
If couchDB could provide a way for me to implement that (by some
"non-deterministic lists" for example), it will be OK, but at the moment I
can't do that as a couchdb user.
For the big-O cost argument... I must admit I don't understand what that
means... :-/ However I can imagine the big-network cost of retrieving all keys
I'm interested in, pick some random ones client-side, and then fetch those
docs... That's how my current implementation is.
Hope you'll reconsider adding this particular feature or a more generic
"non-deterministic list" feature, even if performance is bad for you, it'll
certainly be better than couch request + network IO + client code + couch
request...?
Regards
> implement randomization in views resultset
> --
>
> Key: COUCHDB-812
> URL: https://issues.apache.org/jira/browse/COUCHDB-812
> Project: CouchDB
> Issue Type: Wish
> Components: Database Core
>Affects Versions: 0.11
> Environment: CouchDB
>Reporter: Mickael Bailly
>Priority: Minor
>
> This is a proposal for a new feature in CouchDB : allow a randomization of
> rows in a view response. We can for example add a randomize query parameter...
> This request would probably not return the same results for the same request.
> As an example :
> GET /db/_design/doc/_view/example :
> {
> ..
> rows: [
> {key: 1 ...},
> {key: 2 ...},
> {key: 3 ...}
> ]
> }
> GET /db/_design/doc/_view/example?randomize=true :
> {
> ..
> rows: [
> {key: 2 ...},
> {key: 3 ...},
> {key: 1 ...}
> ]
> }
> GET /db/_design/doc/_view/example?randomize=true :
> {
> ..
> rows: [
> {key: 1 ...},
> {key: 3 ...},
> {key: 2 ...}
> ]
> }
> This is a feature hard to implement client-side (but by reading all doc ids
> and use client-side random function). It's implemented by the RDBMS from
> ages, probably for the very same reasons : if we should read all the rows
> client-side to random-select some of them, performances are awful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-812) implement randomization in views resultset
implement randomization in views resultset
--
Key: COUCHDB-812
URL: https://issues.apache.org/jira/browse/COUCHDB-812
Project: CouchDB
Issue Type: Wish
Components: Database Core
Affects Versions: 0.11
Environment: CouchDB
Reporter: Mickael Bailly
Priority: Minor
This is a proposal for a new feature in CouchDB : allow a randomization of rows
in a view response. We can for example add a randomize query parameter...
This request would probably not return the same results for the same request.
As an example :
GET /db/_design/doc/_view/example :
{
..
rows: [
{key: 1 ...},
{key: 2 ...},
{key: 3 ...}
]
}
GET /db/_design/doc/_view/example?randomize=true :
{
..
rows: [
{key: 2 ...},
{key: 3 ...},
{key: 1 ...}
]
}
GET /db/_design/doc/_view/example?randomize=true :
{
..
rows: [
{key: 1 ...},
{key: 3 ...},
{key: 2 ...}
]
}
This is a feature hard to implement client-side (but by reading all doc ids and
use client-side random function). It's implemented by the RDBMS from ages,
probably for the very same reasons : if we should read all the rows client-side
to random-select some of them, performances are awful.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-792) Bespin integrated in Futon views editor
[
https://issues.apache.org/jira/browse/COUCHDB-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Bailly updated COUCHDB-792:
---
Attachment: futon-bespin.patch.gz
patch built on top of CouchDB github repository :
http://github.com/apache/couchdb/commit/5aae08bf66411e4e81b21a3c137627733efa6b26
> Bespin integrated in Futon views editor
> ---
>
> Key: COUCHDB-792
> URL: https://issues.apache.org/jira/browse/COUCHDB-792
> Project: CouchDB
> Issue Type: New Feature
> Components: Futon
> Environment: HTML5 / Javascript
>Reporter: Mickael Bailly
>Priority: Minor
> Fix For: 0.11.1
>
> Attachments: futon-bespin.patch.gz
>
>
> Here is the "less-intrusive-I-can" patch to enable bespin editor in Futon
> database views page.
> Implementation constraints :
> - bespin can't have multiple instances
> - bespin can't be enabled=>disabled=>enabled
> I also met a bug on Google Chrome because CouchDB doesn't set a charset in
> HTTP response headers for database.html ... As a result I only succeded with
> BespinEmbedded 0.7.1.
> Implementation details :
> - created proxy functions to get and set map/reduce code to/from editor (
> instead of $("#viewcode_map").val() ... )
> - created bespin wrapper class
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-792) Bespin integrated in Futon views editor
Bespin integrated in Futon views editor
---
Key: COUCHDB-792
URL: https://issues.apache.org/jira/browse/COUCHDB-792
Project: CouchDB
Issue Type: New Feature
Components: Futon
Environment: HTML5 / Javascript
Reporter: Mickael Bailly
Priority: Minor
Fix For: 0.11.1
Here is the "less-intrusive-I-can" patch to enable bespin editor in Futon
database views page.
Implementation constraints :
- bespin can't have multiple instances
- bespin can't be enabled=>disabled=>enabled
I also met a bug on Google Chrome because CouchDB doesn't set a charset in HTTP
response headers for database.html ... As a result I only succeded with
BespinEmbedded 0.7.1.
Implementation details :
- created proxy functions to get and set map/reduce code to/from editor (
instead of $("#viewcode_map").val() ... )
- created bespin wrapper class
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-770) Designer add-on for Futon
[ https://issues.apache.org/jira/browse/COUCHDB-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Bailly updated COUCHDB-770: --- Attachment: (was: futon-designer.zip) > Designer add-on for Futon > - > > Key: COUCHDB-770 > URL: https://issues.apache.org/jira/browse/COUCHDB-770 > Project: CouchDB > Issue Type: New Feature > Components: Futon >Affects Versions: 0.11 > Environment: html/javascript/css >Reporter: Mickael Bailly >Priority: Minor > Attachments: futon-designer.zip > > > This adds a designer.html futon page, that allows you to edit views, lists, > and shows with the Mozilla's bespin editor. > You can then run your views/lists/shows and see returned data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-770) Designer add-on for Futon
[ https://issues.apache.org/jira/browse/COUCHDB-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Bailly updated COUCHDB-770: --- Attachment: futon-designer.zip - views, shows and lists now share the same error and success callback functions - improved timeout errors handling - bespin editor is now resizable (you can track changes from github : http://github.com/dready92/futon-designer/ ) > Designer add-on for Futon > - > > Key: COUCHDB-770 > URL: https://issues.apache.org/jira/browse/COUCHDB-770 > Project: CouchDB > Issue Type: New Feature > Components: Futon >Affects Versions: 0.11 > Environment: html/javascript/css >Reporter: Mickael Bailly >Priority: Minor > Attachments: futon-designer.zip, futon-designer.zip > > > This adds a designer.html futon page, that allows you to edit views, lists, > and shows with the Mozilla's bespin editor. > You can then run your views/lists/shows and see returned data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-770) Designer add-on for Futon
[ https://issues.apache.org/jira/browse/COUCHDB-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mickael Bailly updated COUCHDB-770: --- Attachment: futon-designer.zip The actual code. move the folder's content to [couchdb install dir]/share/couchdb/www > Designer add-on for Futon > - > > Key: COUCHDB-770 > URL: https://issues.apache.org/jira/browse/COUCHDB-770 > Project: CouchDB > Issue Type: New Feature > Components: Futon >Affects Versions: 0.11 > Environment: html/javascript/css >Reporter: Mickael Bailly >Priority: Minor > Attachments: futon-designer.zip > > > This adds a designer.html futon page, that allows you to edit views, lists, > and shows with the Mozilla's bespin editor. > You can then run your views/lists/shows and see returned data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (COUCHDB-770) Designer add-on for Futon
Designer add-on for Futon - Key: COUCHDB-770 URL: https://issues.apache.org/jira/browse/COUCHDB-770 Project: CouchDB Issue Type: New Feature Components: Futon Affects Versions: 0.11 Environment: html/javascript/css Reporter: Mickael Bailly Priority: Minor This adds a designer.html futon page, that allows you to edit views, lists, and shows with the Mozilla's bespin editor. You can then run your views/lists/shows and see returned data. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
