[CALCITE-6241] Enable a few existing functions to hive library

[ChengJie1053]

Add hive as a supported library for functions that have already been implemented for other libraries.

Hive Functions Link：https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-ArithmeticOperators

[caicancai]

@ChengJie1053 Thanks for your contribution, can you confirm that these functions give the same results in some boundary tests?

In my experience, this is difficult to guarantee.

[mihaibudiu]

I haven't verified that indeed all these functions in Hive have the exact same behavior as the existing implementation. But assuming they do, this PR is fine.

[ChengJie1053]

I haven't verified that indeed all these functions in Hive have the exact same behavior as the existing implementation. But assuming they do, this PR is fine.

Ok, thanks for reviewing the code for me

[ChengJie1053]

@ChengJie1053 Thanks for your contribution, can you confirm that these functions give the same results in some boundary tests?

In my experience, this is difficult to guarantee.

Ok, thanks for reviewing the code for me, are there any other test cases I need to modify for testing

[caicancai]

Please remove the adaptation of log related functions. I have not adapted the log function to hive.

[ChengJie1053]

Please remove the adaptation of log related functions. I have not adapted the log function to hive.

Ok, thanks for reviewing the code for me, I will change the code

[NobiGo]

LGTM. If we discover inconsistent function semantics, we can resolve it by a new ISSUE.

[ChengJie1053]

LGTM. If we discover inconsistent function semantics, we can resolve it by a new ISSUE.

Ok, thanks for reviewing the code for me

[caicancai]

Please remove the log function before merging.

[ChengJie1053]

Please remove the log function before merging.

Ok, thanks for reviewing the code for me, I will change the code

[ChengJie1053]

Please remove the log function before merging.

Hello, the code has been modified

[mihaibudiu]

Can you please fix the conflicts and squash the commits in preparation for merging?

[caicancai]

@ChengJie1053

Can you please fix the conflicts and squash the commits in preparation for merging?

[ChengJie1053]

Can you please fix the conflicts and squash the commits in preparation for merging?

Ok, thank you. I'll fix it as soon as possible

[mihaibudiu]

The 1.38 release is coming soon, if you can squash the commits we can merge this.

[ChengJie1053]

The 1.38 release is coming soon, if you can squash the commits we can merge this.

Ok, thank you. I tried squash commits, but failed. Can I submit a new pr

[mihaibudiu]

There is no reason squashing cannot be done. Try git reset HEAD~5 and then you can start as if there is no commit at all. You just have to use -f when you push again

[ChengJie1053]

There is no reason squashing cannot be done. Try git reset HEAD~5 and then you can start as if there is no commit at all. You just have to use -f when you push again

Ok, thank you very much. I'll try that

[sonarcloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[mihaibudiu]

This PR is fine, but the JIRA issue CALCITE-6241 has a different title and has been closed for 1.37.
There are also conflicts.
One course of action is to remove the CALCITE-6241 from the PR and commit message.
Another course of action is to file a new JIRA issue and use that.

[mihaibudiu]

Unfortunately this has developed new conflicts, can you please solve these and we can now merge it.

[mihaibudiu]

Tried to fix the conflict using the browser editor and I failed... sorry about this.