Re: Where is my output going

DUMP sends your Pig script output to stdout of wherever you launched the Grunt shell from. If you want to write to a file, check out the STORE command instead. On Fri, Mar 2, 2012 at 7:38 PM, Mohit Anchlia wrote: > I run a job with "DUMP A". At the end it says output in " > hdfs://db1:54310/tmp/

vim snipmate pig.snippet

I've created a vim snipmate plugin for PigLatin which saves me a lot of time developing Pig jobs. For those unfamiliar: Snipmate is a Vim plugin for code completion. I've made a small writeup here .

Re: mongo-hadoop Pig users must turn off speculative execution to avoid duplicate inserts

I think I'm going to add 'fire command' before/after, to set up indexes. Russell Jurney twitter.com/rjurney russell.jur...@gmail.com datasyndrome.com On Mar 2, 2012, at 1:48 PM, Bill Graham wrote: > Ahh yes, a bug in the documentation perhaps for not pointing this out. > > On Fri, Mar 2, 2012 a

Re: mongo-hadoop Pig users must turn off speculative execution to avoid duplicate inserts

Ahh yes, a bug in the documentation perhaps for not pointing this out. On Fri, Mar 2, 2012 at 1:44 PM, Russell Jurney wrote: > It is creating a new collection, that has no keys, and inserting dupes. > > The docs don't say you need to do this, thus the bug. > > Russell Jurney http://datasyndrome.c

Re: mongo-hadoop Pig users must turn off speculative execution to avoid duplicate inserts

It is creating a new collection, that has no keys, and inserting dupes. The docs don't say you need to do this, thus the bug. Russell Jurney http://datasyndrome.com On Mar 2, 2012, at 1:00 PM, Jeremy Hanna wrote: > Not sure what mongo's doing (generate ID or triggers or something) but it > sh

Re: PigServer vs PigRunner

On 3/1/12 8:15 AM, Jacob Perkins wrote: Hello, I find myself needing to run a pig script iteratively from within a java program. Since I'm writing the data to a db (Cassandra) I can't (as far as I can tell) use PigServer's store method. There is a PigServer.store(String id, String filename, Stri

Re: mongo-hadoop Pig users must turn off speculative execution to avoid duplicate inserts

Not sure what mongo's doing (generate ID or triggers or something) but it should only be a problem of efficiency if the writes are idempotent. On Mar 2, 2012, at 3:39 AM, Jonathan Coveney wrote: > I agree with Bill. Speculative execution is a feature of Hadoop that > doesn't jive nicely with sto

Re: [Blog Post]: Accumulo and Pig play together now

- bcc: u...@nutch.apache.org common-u...@hadoop.apache.org This is great Jason. One thing to add though is this line in your Pig script: SET mapred.map.tasks.speculative.execution false Otherwise you'll likely going to get duplicate writes into accumulo. On Fri, Mar 2, 2012 at 5:48 AM, Jason T

[Blog Post]: Accumulo and Pig play together now

For anyone interested... Accumulo and Pig play together now: http://www.covert.io/post/18605091231/accumulo-and-pig and https://github.com/jt6211/accumulo-pig --Jason

Re: Processing hierarchical information in Pig

Re-surfacing the questions. This sounds like a common use case, butI am still stuck -:) Thanks! On Thu, Mar 1, 2012 at 1:03 AM, prash987 prash987 wrote: > Thank You Norbert for your reply. > > > > I am still not sure how/if I can do this through Pig script, though? > Given the below adjacency li

Re: mongo-hadoop Pig users must turn off speculative execution to avoid duplicate inserts

I agree with Bill. Speculative execution is a feature of Hadoop that doesn't jive nicely with storing data into non-hadoop systems. 2012/3/1 Bill Graham > I don't think this is a bug. This is something that always needs to be done > when writing to any DB. > > On Thu, Mar 1, 2012 at 5:19 PM, Rus