Closed pereferrera closed 12 years ago
+1 But it is important to see how the API would look like to have a good decision.
Iván
2012/5/17 Pere Ferrera < reply@reply.github.com
Currently it lacks some functionality that TupleMRBuilder.
Ideally we shouldn't be replicating code. MapOnlyJoBuilder is a nice API but maybe it could be developed on top of TupleMRBuilder. Then, TupleMRBuilder would need to be adapted in order to support map-only Jobs.
Reply to this email directly or view it on GitHub: https://github.com/datasalt/pangool/issues/11
Iván de Prado CEO & Co-founder www.datasalt.com
I think it is better to have a separated builder for now. It makes the API look better for me. I have just refactored the code for supporting the same functionality (multi inputs and named outputs) in both builders without repeating code.
Currently it lacks some functionality that TupleMRBuilder has.
Ideally we shouldn't be replicating code. MapOnlyJoBuilder is a nice minimal API but maybe it could be developed on top of TupleMRBuilder. Then, TupleMRBuilder would need to be adapted in order to support map-only Jobs.