API for defining views in more declarative way

Volker Mische added a comment - 21/Feb/13 7:40 AM I've assigned it to me, since I'd like to know what happens to it (and it doesn't matter who if the view-engine teams owns). Anyone feel free to assign it to yourself if you want to come up with a nice syntax.

Jasdeep Jaitla added a comment - 21/Feb/13 11:31 AM The idea is straightforward, we are making collection indexes on a single field: if (match_json_key_a, value_a) index (json_key_b) which translates to: function(doc,meta) {   if (doc.json_key_a == value_a) {     emit(json_key_b);   } } The method syntax can be something like: create_index(index_name, collection_json_key, collection_json_value, index_json_key, [optional_json_key_value_output]) Example #1: create_index("all_users_by_email", "doctype", "user", "email") Translates to: View Name: all_users_by_email function(doc,meta) {   if (doc.doctype == "user") {     emit(doc.email);   } } Example #2 (with output value): create_index("all_users_by_email", "doctype", "user", "email", "uid") Translates to: View Name: all_users_by_email function(doc,meta) {   if (doc.doctype == "user") {     emit(doc.email, doc.uid);   } }

Volker Mische added a comment - 21/Feb/13 11:57 AM Perhaps it could be more JSON like (people using Couchbase should know JSON). Example #1:     {       "name": all_users_by_email",       "filter": {         "key": "doctype",         "value": "user"       },       "emit": {         "key": "email"       }     } Example #2     {       "name": all_users_by_email",       "filter": {         "key": "doctype",         "value": "user"       },       "emit": {         "key": "email",         "value": "uid"       }     }

Jasdeep Jaitla added a comment - 21/Feb/13 12:01 PM Sure, i just picked that style as a way to express the idea :)

Jasdeep Jaitla added a comment - 21/Feb/13 12:26 PM One question I had was how to optimize these so that we can have more of them than other VIews, how can we reduce the overhead so that many more of these can live in a design document. I thought the JSON pointer might be one way since it's really not V8 that is a bottleneck. At least we reduce the needs to convert to JSON objects for each document, although the cost of that is shared amongst all Map functions (right?), or is that per Design Document/Indexer?

Volker Mische added a comment - 21/Feb/13 12:41 PM This is not about performance, this is about convenience. The map functions currently aren't the bottle neck.

Dipti Borkar added a comment - 13/May/13 7:34 PM Marty, is this something you are looking at ?