[ 
https://issues.apache.org/jira/browse/DATAFU-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003421#comment-14003421
 ] 

Matthew Hayes commented on DATAFU-49:
-------------------------------------

Committed :)

I also added one more commit with some additional changes.  The README files 
now include commands for running the scripts.  The sessionize script now 
doesn't convert the time to iso time because this isn't needed; Sessionize 
works with the epoch time directly now.  I had an issue using ToString with Pig 
0.12.1.  The data generation script for quantile now outputs the file with a 
tsv extension, since the data file isn't checked in.

> Scripts in Examples Directory work again
> ----------------------------------------
>
>                 Key: DATAFU-49
>                 URL: https://issues.apache.org/jira/browse/DATAFU-49
>             Project: DataFu
>          Issue Type: Bug
>            Reporter: Philip (flip) Kromer
>            Priority: Minor
>              Labels: data, example, pig
>             Fix For: 1.3.0
>
>         Attachments: 
> 0001-DATAFU-49-Examples-work-again-data-for-the-quantile-example.patch, 
> 0002-DATAFU-49-Examples-work-again.patch
>
>
> Examples work again.
> * removed dependency on Guava (which it didn't actually depend on) and on 
> Piggybank (since date functions are now first class)
> * path to datafu jar correct for current repo layout
> * The quantile examples demonstrate a comparison of the exact vs approx 
> algorithms (my first question was "how approximate is approximate?" 0.5% to 
> 1.5% on the little drip of data that's using)
> * added the script to generate data for quantile and a frozen version of 30k 
> records.
> * Quantile examples demonstrate both ways of constructing a Quantile UDF 
> (number of partitions vs list of breakpoints)
> There are _two_ patches attached. One adds a 30k-line data file. The other 
> holds the changes to the code and so forth.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to