Conversation
- Add unmatched_left_rows_ and unmatched_left_keys_ storage to HashJoinOperator - Add get_unmatched_left_rows() and get_unmatched_left_keys() methods - During probe, store unmatched LEFT tuples instead of just emitting - Add unit tests for LEFT and FULL join unmatched tracking
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 35 minutes and 25 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
unmatched_left_rows_andunmatched_left_keys_storage to HashJoinOperatorget_unmatched_left_rows()andget_unmatched_left_keys()methodsTest plan
Related
Part of Option C implementation for FULL JOIN support.