[
https://issues.apache.org/jira/browse/ARROW-13359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17382158#comment-17382158
]
Eduardo Ponce commented on ARROW-13359:
---------------------------------------
What are the tools/languages that Arrow wants to conform to the most? If there
is an answer to this question, then we can come up with a priority-driven
naming convention based on the conformance to such tools.
For example, if function exists in SQL, then use the SQL form. If function does
not exists in SQL, then use numpy's form. Etc. etc.
> [C++][Python] Revisit compute functions names
> ---------------------------------------------
>
> Key: ARROW-13359
> URL: https://issues.apache.org/jira/browse/ARROW-13359
> Project: Apache Arrow
> Issue Type: Improvement
> Components: C++, Documentation, Python
> Reporter: Eduardo Ponce
> Priority: Major
> Fix For: 6.0.0
>
>
> Compute function's naming convention should be "standardized" for the C++ API
> and the *CallFunction* string name. There are inconsistencies between the
> name used and its form (short vs. long form). This is not a trivial task
> because existing software tools/languages (SQL, numpy, R, C++, etc.) use
> different function names.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
