[Data] Upgrade Arrow version from 17 to 18

[scottjlee]

Why are these changes needed?

Upgrade CI to use pyarrow 18, the latest released version from Pyarrow.

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[aslonnie]

do you want to change the versions in maybe data-requirements.txt or something so that the python/requirements_compiled is updated too?

[scottjlee]

hmm, we don't want to force users to install pyarrow 18 / the latest version of pyarrow. they should be able to choose any version within the general bounds (pyarrow >= 6.0.1,<18). so i think we shouldn't add any explicit pyarrow pin in data-requirements.txt or data-test-requirements.txt? cc @can-anyscale

[can-anyscale]

The python/requirements_compiled.txt indicates the versions we install in the rayproject/ray docker image (orthogonal to ray pypi). It's currently on 14 (https://github.com/ray-project/ray/blob/master/python/requirements_compiled.txt#L1595) so pretty outdated itself.

It's optional but I recommend to update it to the latest version yes (or whoever supports python 3.13 will eventually upgrade it anyway). If so, maybe do it in another PR; it's not a blocker in this PR.

[richardliaw]

Hi @can-anyscale @aslonnie can we get this merged?

[can-anyscale]

[can-anyscale]

upgraded to latest and enable auto-merge ;)