According to the discussion in #4993 (comment) we often encountered this scenario: we compare values repeatedly. The comparisons differs only in the parameters (vector to compare, start index, etc).
According to the current API, we have to create a new RangeEqualVisitor object each time the comparison is performed. This leads to non-trivial performance overhead.
To address this problem, we make the RangeEqualVisitor reusable, and allow the client to change parameters of an existing visitor.
Reporter: Liya Fan / @liyafan82
Assignee: Liya Fan / @liyafan82
PRs and other links:
Note: This issue was originally created as ARROW-6355. Please see the migration documentation for further details.
According to the discussion in #4993 (comment) we often encountered this scenario: we compare values repeatedly. The comparisons differs only in the parameters (vector to compare, start index, etc).
According to the current API, we have to create a new RangeEqualVisitor object each time the comparison is performed. This leads to non-trivial performance overhead.
To address this problem, we make the RangeEqualVisitor reusable, and allow the client to change parameters of an existing visitor.
Reporter: Liya Fan / @liyafan82
Assignee: Liya Fan / @liyafan82
PRs and other links:
Note: This issue was originally created as ARROW-6355. Please see the migration documentation for further details.