Outer join handles case when both are empty

[aposwolsky]

• If we are doing an outer join (K, A) x (K, B) by itself then it makes sense to assume that either A or B must exist for every key, but when composed with subsequent joins it is possible to get a key for which both A and B would be empty and the correct interpretation is to return an empty iterator (previously would do (None, None))

[johnynek]

Thanks a ton! I had to restart the build, but it looks like travis issues.

I'll make a new version today (0.12rc4) and if that looks good when we use it at Twitter, we'll publish 0.12 final.

[aposwolsky]

great! thanks..

On Wed, Sep 24, 2014 at 2:46 PM, P. Oscar Boykin notifications@github.com
wrote:

Thanks a ton! I had to restart the build, but it looks like travis issues.

I'll make a new version today (0.12rc4) and if that looks good when we use
it at Twitter, we'll publish 0.12 final.

Reply to this email directly or view it on GitHub
#1065 (comment).