[
https://issues.apache.org/jira/browse/ARROW-9390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antoine Pitrou updated ARROW-9390:
----------------------------------
Description:
We should probably make compute function naming more consistent while it's not
too late.
Examples:
* "isin", "minmax" but "less_equal", "or_kleene", "binary_contains_exact"
* "binary_contains_exact" only works on string types
* "ascii_length" accepts non-ascii input and simply counts the number of bytes
* "partition_to_indices" vs. "NthToIndices"
was:
We should probably make compute function naming more consistent while it's not
too late.
Examples:
* "isin", "minmax" but "less_equal", "or_fleene", "binary_contains_exact"
* "binary_contains_exact" only works on string types
* "ascii_length" accepts non-ascii input and simply counts the number of bytes
* "partition_to_indices" vs. "NthToIndices"
> [C++] Review compute function names
> -----------------------------------
>
> Key: ARROW-9390
> URL: https://issues.apache.org/jira/browse/ARROW-9390
> Project: Apache Arrow
> Issue Type: Wish
> Components: C++
> Reporter: Antoine Pitrou
> Assignee: Antoine Pitrou
> Priority: Blocker
> Fix For: 1.0.0
>
>
> We should probably make compute function naming more consistent while it's
> not too late.
> Examples:
> * "isin", "minmax" but "less_equal", "or_kleene", "binary_contains_exact"
> * "binary_contains_exact" only works on string types
> * "ascii_length" accepts non-ascii input and simply counts the number of bytes
> * "partition_to_indices" vs. "NthToIndices"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
