Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
copr: improve in performance using lookup set in metadata #6000
Signed-off-by: TennyZhuang firstname.lastname@example.org
What have you changed?
Please explain in detail what the changes are in this PR and why they are needed:
Assume that the number of rows is n , and the number of constant args is m, then the vec_compare_in optimized from
What is the type of the changes?
How is the PR tested?
Please select the tests that you ran to verify your changes:
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
Does this PR affect
@sticnarf construct some Json case is complicated in test, how about add a new fn called
fn compare_in_by_compare_internal<T: InByCompare>(base_val: T, args: &[&Option<T>], default_ret: Option<Int>) -> Result<Option<Int>>)