Databases
StackOverflow2013
Postsdbo
POUse mapReduce on a 'logs' collection to generate HTTP stream
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUse mapReduce on a 'logs' collection to generate HTTP stream
    primarykey
    data
    text
    <p>MongoDB newbie issue:</p> <p>I have a lot of HTTP logs stored into a collection with the following data structure:</p> <pre><code>{ 'client': { 'ip_address': '1.2.3.4', 'referrer':"http://....", 'user_agent':'Mozilla..." }, 'request':{ "stream": "stream1", "method": "GET", "fragment_id": 97, "date": 13482181, 'response':{ 'status':200, 'size': 654 } } </code></pre> <p>Each document describes an HTTP request (from a client to a content streamer). As each stream is fragmented into smaller pieces, I would like to use "mapReduce" on my collection and then create a "generic stream request" document, as below:</p> <pre><code>{ 'client_ip': '1.2.3.4', 'user_agent': 'Mozilla', 'streams':[ { 'stream':"stream1", 'referrer':'http://...', 'requests':[ { 'fragment_id':97, 'status':200, 'date': 13482181, 'size': 654 ... }, { 'fragment_id':98, 'status':200, 'date': 13482192, 'size': 624 ... }, [...] ] }, [...] ] </code></pre> <p>Here is what I tried:</p> <pre><code>map = function(){ emit({client_ip:this.client.ip,user_agent:this.client.user_agent},{ stream:this.request.stream, referrer:this.client.referer, status:this.response.status, date:this.request.date, size:this.response.total_size, fragment_id:this.request.fragment_infos[1] }); } reduce = function(key,values){ r = {'count':0,'request':[]}; values.forEach(function(v){ r.count += 1; r.request.push(v); }); return r; } </code></pre> <p>but here is what I get as a result:</p> <pre><code>"_id" : { "client_ip" : "1.2.3.4", "user_agent" : "Mozilla\/4.0" }, "value" : { "client_ip" : "1.2.3.4", "user_agent" : "Mozilla\/4.0", "count" : 17, "request" : { "0" : { "client_ip" : "1.2.3.4", "user_agent" : "Mozilla\/4.0", "count" : 2, "request" : { "0" : { "stream" : "stream1.isml", "referrer" : null, "status" : 200, "date" : 1341706566, "size" : 456, "fragment_id" : null, "count" : 1 }, "1" : { "stream" : "stream1.isml", "referrer" : null, "status" : 200, "date" : 1341706566, "size" : null, "fragment_id" : null, "count" : 1 } } }, "1" : { "client_ip" : "1.2.3.4", "user_agent" : "Mozilla\/4.0", "count" : 3, "request" : { "0" : { "client_ip" : "1.2.3.4", "user_agent" : "Mozilla\/4.0", "count" : 2, "request" : { "0" : { "stream" : "stream1.isml", "referrer" : null, "status" : 200, "date" : 1341706568, "size" : null, "fragment_id" : null, "count" : 1 ......... </code></pre> <p>Where am I wrong?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USFranquis
    1. USFranquis
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POUse mapReduce on a 'logs' collection to generate HTTP stream
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    2. VO
      singulars
      1. POUse mapReduce on a 'logs' collection to generate HTTP stream
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POUse mapReduce on a 'logs' collection to generate HTTP stream
      1. USOlaf
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload