ARROW-17160: [C++] Create a base directory for PyArrow CPP header files

[AlenkaF]

This PR is a follow-up of #13311 where it was decided to change the base directory for PyArrow C++ headers to avoid top level inclusions. See #13311 (comment)

[github-actions]

https://issues.apache.org/jira/browse/ARROW-17160

[jorisvandenbossche]

There is still the question about moving the include paths from "arrow/python/.." to "pyarrow/.." (and how to provide some transition path for this), but assuming the current status of exposing those as "arrow/python/.." (which seems the safe assumption for 10.0), this seems like a good change to use those paths in the code and headers itself.

[AlenkaF]

There is still the question about moving the include paths from "arrow/python/.." to "pyarrow/.." (and how to provide some transition path for this), but assuming the current status of exposing those as "arrow/python/.." (which seems the safe assumption for 10.0), this seems like a good change to use those paths in the code and headers itself.

I suggest we try to move the include paths from "arrow/python/.." to "pyarrow/.." for a future release. I can create a separate JIRA issue for it (guessing with Joris we will want to change namespaces from arrow&python to pyarrow also?). Or do you want to tackle this as a part of ARROW-17838@kou?

[kou]

Could you create a separate JIRA issue for it?

[AlenkaF]

Done: https://issues.apache.org/jira/browse/ARROW-17958

[kiszk]

I am sorry for rerunning this travis ci job at https://app.travis-ci.com/github/apache/arrow/builds/256419696 while the job was already succeeded.

[AlenkaF]

I am sorry for rerunning this travis ci job at https://app.travis-ci.com/github/apache/arrow/builds/256419696 while the job was already succeeded.

No problem at all =)

[pitrou]

Thank you very much @AlenkaF !

[pitrou]

@kou Do you have any other concerns?

[kou]

No.

[AlenkaF]

I will merge later today, if there is no objection =)

[jorisvandenbossche]

The Python failure is one of the flaky dataset tests

[jorisvandenbossche]

Thanks @AlenkaF !

[ursabot]

Benchmark runs are scheduled for baseline = d8f3946 and contender = 21dbf4a. 21dbf4a is a master commit associated with this PR. Results will be available as each benchmark for each run completes.
Conbench compare runs links:
[Finished ⬇️0.0% ⬆️0.0%] ec2-t3-xlarge-us-east-2
[Failed ⬇️0.56% ⬆️0.0%] test-mac-arm
[Failed ⬇️0.55% ⬆️0.0%] ursa-i9-9960x
[Finished ⬇️0.25% ⬆️0.0%] ursa-thinkcentre-m75q
Buildkite builds:
[Finished] 21dbf4ac ec2-t3-xlarge-us-east-2
[Failed] 21dbf4ac test-mac-arm
[Failed] 21dbf4ac ursa-i9-9960x
[Finished] 21dbf4ac ursa-thinkcentre-m75q
[Finished] d8f39460 ec2-t3-xlarge-us-east-2
[Failed] d8f39460 test-mac-arm
[Failed] d8f39460 ursa-i9-9960x
[Finished] d8f39460 ursa-thinkcentre-m75q
Supported benchmarks:
ec2-t3-xlarge-us-east-2: Supported benchmark langs: Python, R. Runs only benchmarks with cloud = True
test-mac-arm: Supported benchmark langs: C++, Python, R
ursa-i9-9960x: Supported benchmark langs: Python, R, JavaScript
ursa-thinkcentre-m75q: Supported benchmark langs: C++, Java