A public-library intern writes a Python loop that walks every checkout row to recode a material label. The table is columnar and already on the GPU. What should they use instead?
Select an answer to reveal the explanation.
Short Explanation
The checkout table is columnar and already on the GPU. Recode the material label with cuDF and Arrow column operations, not a Python row loop. Host-side cells, a visit-each-row kernel, and Guardrails miss that Arrow path.
Full Explanation
GPU data prep uses columnar frames. cuDF sits on Apache Arrow memory, so a material-label recode should be a column operation, not a Python row walk. Pulling rows back to the host, writing a kernel, or invoking Guardrails misses that official Arrow mention. Stay columnar on the device.