I *think* that will just work (if you put the correct type annotations in, I believe). Have you tried?
To be honest, we have been so focused on the typed API that pretty much solves all these issues with clear types, that I don't recall the answer to your question. The original fields API is not going to be removed, but we haven't put any development work into it in years. If you can, I recommend you use `TypedPipe` and friends instead. On Thu, Aug 17, 2017 at 12:18 PM, Russell Carden <[email protected]> wrote: > Hello, > I am new to scalding and scala. > Based on a scanLeft example, I wrote some code that looks like > > .insert('tempfield,0.0) > .groupBy('field1,'field2) > {group => group.sortBy('field3) > .scanLeft(('field4,'field5','temp) -> ('Copyfield4, > 'Copyfield5,'desiredfield)) > .... More code > > } > The code does what I want, but I am wondering if it is possible to do away > with the Copies of field 4 and field 5 as well as the temp field. and have > something that looks like > > > .groupBy('field1,'field2) > {group => group.sortBy('field3) > .scanLeft(('field4,'field5') -> ('desiredfield)) > .... More code > > } > > Would this be possible? Any pointers would be much appreciated. Is it a > matter of providing an implicit converter for the outField, if so how and > where can I specify that? > > Thank you > > -- > You received this message because you are subscribed to the Google Groups > "Scalding Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Scalding Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
