Uh oh!
There was an error while loading. Please reload this page.
ARROW-13358: [C++] Improve type support in if_else - #11218
Conversation
There was a problem hiding this comment.
Much of this will need to be reconciled with ARROW-13390/#11080.
pitrou
commented
Sep 29, 2021
This needs rebasing now. |
bca16d4 to
870c1a6Comparelidavidm
commented
Sep 29, 2021
Contains some changes from #11272 so if_else/case_when/coalesce have mostly similar implicit cast rules (though I will leave it to ARROW-14105 to fully unify these). I may also revisit the dictionary case here as it seems slow from test runtime; instead of unifying the dictionaries on-the-fly we should unify them up front and construct a transposition map. (If we copy the RHS to the output, we can use the existing function for transposing indices, and assuming unification preserves the first dictionary's indices exactly, we can then copy the LHS to the output without having to transpose again.) |
lidavidm
commented
Sep 29, 2021
Ah, the described optimization would require being able to unify dictionaries with nulls. Filed ARROW-14177 for now. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pitrou
left a comment
There was a problem hiding this comment.
Thanks for the updates. +1 from me.
Closesapache#11218 from lidavidm/arrow-13358 Lead-authored-by: David Li <li.davidm96@gmail.com> Co-authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
No description provided.