StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14133669
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-03T05:44:40.587
FavoriteCount
0
LastActivityDate
2013-01-03T05:44:40.587
LastEditDate
LastEditorUserId
0
OwnerUserId
1698443
ParentId
12250352
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
The split pattern is in the Cascading User Guide at: <a href="http://docs.cascading.org/cascading/2.1/userguide/htmlsingle/#N21362" rel="nofollow">http://docs.cascading.org/cascading/2.1/userguide/htmlsingle/#N21362</a> Another (simpler) example is included in "Cascading for the Impatient", parts 5 & 6: <ul> <li><a href="https://github.com/Cascading/Impatient/wiki/Part-5" rel="nofollow">https://github.com/Cascading/Impatient/wiki/Part-5</a></li> <li><a href="https://github.com/Cascading/Impatient/wiki/Part-6" rel="nofollow">https://github.com/Cascading/Impatient/wiki/Part-6</a></li> </ul> One point about the code shown above is that it seem to be missing the variable definitions for <code>report1Pipe</code> and <code>report2Pipe</code>. To use a split pattern, each branch requires a name and the names need to be different. The exception gets thrown because there are two branches which have both inherited the same name from earlier in the pipe assembly. So, for example, those <code>flowDef.addSink(..)</code> calls are ambiguous to the flow planner. So in "Impatient" part 5, look at how the "D", "DF", and "TF" branches get named within operations. It may seem a bit counter-intuitive for Cascading to require this naming, but it becomes quite important in large, complex workflows when you're attaching failure traps, debug, etc., to specific branches. Alternatively, the Cascalog DSL in Clojure is much more declarative, so this gets handled by the language directly -- branches are subqueries, and the traps, etc., get handled within the closure of a subquery.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHadoop Cascading - create flow with one source, two sinks
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPaco
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
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.