This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 16854 - mapreduce / ChuQL
Summary: mapreduce / ChuQL
Status: NEW
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Requirements for Future Versions (show other bugs)
Version: Working drafts
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Jim Melton
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-25 14:23 UTC by Jonathan Robie
Modified: 2014-05-20 17:07 UTC (History)
2 users (show)

See Also:


Attachments

Description Jonathan Robie 2012-04-25 14:23:03 UTC
ChuQL adds support for Map/Reduce to XQuery

mapreduce {
  input { fn:collection("hdfs://input/") }
  rr { for $line at $i in $in//line return { key: $i, val: $line } }
  map { for $word in fn:tokenize($in=>val, " ")
  return { key: $word, val: 1 } }
  reduce { { key: $in=>key, val: fn:count($in=>val) } }
  rw { <word text="{$in=>key}" count="{$in=>val}"/> }
  output { fn:put($in,"hdfs://output/") }
}

See ceur-ws.org/Vol-749/paper25.pdf.

Seems like a plausible feature that would make XQuery much more useful for Big Data.
Comment 1 John Snelson 2012-06-26 12:31:16 UTC
This would be better off defined as an XQuery library that accepts function values for the map/reduce methods.

As it is a functional language, XQuery expressions can already automatically be split into map/reduce parts and executed in a map/reduce framework.
Comment 2 Jonathan Robie 2014-05-20 16:52:04 UTC
Assigning to future requirements per Working Group decision (https://lists.w3.org/Archives/Member/w3c-xsl-query/2012Oct/0087.html).