[PR] Clarify IPC security docs with validation API examples [arrow]

["shashbha14 (via GitHub)" <gi...@apache.org>]

shashbha14 opened a new pull request, #49254:
URL: https://github.com/apache/arrow/pull/49254

   Fixes #49241
   
   The current Security documentation mentions that users should “use the appropriate
   APIs to validate the Arrow data” when reading IPC streams from untrusted sources,
   but it doesn’t say which APIs those are.
   
   This PR adds a short “Security considerations for untrusted IPC data” section to
   the Python IPC docs. It:
   
   - Explains that you should explicitly validate RecordBatches/Tables when reading
     IPC data from untrusted or semi‑trusted sources.
   - Points to `RecordBatch.validate()` and `Table.validate()` as the relevant
     validation helpers.
   - Shows small code snippets using these methods with `pa.ipc.open_stream` and
     `pa.ipc.open_file`.
   
   This makes the recommended validation APIs discoverable for PyArrow users and
   matches what was requested in #49241.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] Clarify IPC security docs with validation API examples [arrow]

["github-actions[bot] (via GitHub)" <gi...@apache.org>]

github-actions[bot] commented on PR #49254:
URL: https://github.com/apache/arrow/pull/49254#issuecomment-3889178317

   <!--
     Licensed to the Apache Software Foundation (ASF) under one
     or more contributor license agreements.  See the NOTICE file
     distributed with this work for additional information
     regarding copyright ownership.  The ASF licenses this file
     to you under the Apache License, Version 2.0 (the
     "License"); you may not use this file except in compliance
     with the License.  You may obtain a copy of the License at
   
       http://www.apache.org/licenses/LICENSE-2.0
   
     Unless required by applicable law or agreed to in writing,
     software distributed under the License is distributed on an
     "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
     KIND, either express or implied.  See the License for the
     specific language governing permissions and limitations
     under the License.
   -->
   
   Thanks for opening a pull request!
   
   If this is not a [minor PR](https://github.com/apache/arrow/blob/main/CONTRIBUTING.md#Minor-Fixes). Could you open an issue for this pull request on GitHub? https://github.com/apache/arrow/issues/new/choose
   
   Opening GitHub issues ahead of time contributes to the [Openness](http://theapacheway.com/open/#:~:text=Openness%20allows%20new%20users%20the,must%20happen%20in%20the%20open.) of the Apache Arrow project.
   
   Then could you also rename the pull request title in the following format?
   
       GH-${GITHUB_ISSUE_ID}: [${COMPONENT}] ${SUMMARY}
   
   or
   
       MINOR: [${COMPONENT}] ${SUMMARY}
   
   See also:
   
     * [Other pull requests](https://github.com/apache/arrow/pulls/)
     * [Contribution Guidelines - Contributing Overview](https://arrow.apache.org/docs/developers/overview.html)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] MINOR: [Docs] Mention validate() helpers in Python IPC docs [arrow]

["shashbha14 (via GitHub)" <gi...@apache.org>]

shashbha14 commented on PR #49254:
URL: https://github.com/apache/arrow/pull/49254#issuecomment-3889917855

      Thanks for the review and clarification.You’re right, this PR doesn’t address the Security.rst text or the
      `always_validate` flag question. I’ve updated the title/description so this
      is just a small Python IPC docs improvement instead of trying to close
      #49241. I’m happy to leave the main issue open for the broader discussion and any
      changes you’d like to make on the Security page itself.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org