New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

joinWithLarger gives different output field ordering from joinWithSmaller #239

Open

johnynek opened this issue Dec 3, 2012 · 1 comment

Collaborator

johnynek commented Dec 3, 2012

because the pipes are reversed in the implementation:

https://github.com/twitter/scalding/blob/develop/src/main/scala/com/twitter/scalding/JoinAlgorithms.scala#L162

but we never reverse the values after.

How can we fix this currently? It seems like cascading doesn't yet give us the API to do so.

cwensel commented Dec 3, 2012

when and where do you need the api call. we know all the fields after the Flow has been planned. just a matter of exposing them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment