Fix host buffer access from device function in the Parquet reader

[vuule]

Description

Closes #14311
The host access becomes an issue when pageable memory is used for host side of hostdevice_vector.
This PR fixes the device lambda to use the device pointer instead.

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.

[shrshi]

Looks good to me, thank you!

[ttnghia]

Is there any test for the related function? If yes, how this didn't crash the test?

[vuule]

Is there any test for the related function? If yes, how this didn't crash the test?

The use of pinned memory was hiding the issue. When using pageable memory in hostdevice_vectors, all of the Parquet reader tests crash.

[ttnghia]

The use of pinned memory was hiding the issue. When using pageable memory in hostdevice_vectors, all of the Parquet reader tests crash.

Then can we have a test with both pinned memory/pageable memory? Such as through macro definition or toggling the corresponding env variable?

[vuule]

The use of pinned memory was hiding the issue. When using pageable memory in hostdevice_vectors, all of the Parquet reader tests crash.

Then can we have a test with both pinned memory/pageable memory? Such as through macro definition or toggling the corresponding env variable?

I've started working on the test and realized some problems. The env var is read only once and cached. We can't enable pageable memory use for only one test.
We would also need separate tests for each format.
I don't think we should be adding tests for this at this time. Maybe if/when the option gets some use.

[vuule]

/merge

[vuule]

Merged to enable spark experiments; we can add tests in a separate PR.