paleolimbot commented on code in PR #50408: URL: https://github.com/apache/arrow/pull/50408#discussion_r3537544836
########## docs/source/cpp/security.rst: ########## @@ -120,6 +120,22 @@ variants, but these typically fall into two categories: arguments (this is typical of the :ref:`array builders <cpp-api-array-builders>` and :ref:`buffer builders <cpp-api-buffer-builders>`). +Controlling and restricting memory allocation +--------------------------------------------- + +By construction, many Arrow C++ APIs can allocate large amounts of memory, depending +on their input parameters. Arrow C++ allows customizing the memory allocator for +such large data areads through the :ref:`MemoryPool <cpp_memory_pool>` interface. Review Comment: ```suggestion such large data requests through the :ref:`MemoryPool <cpp_memory_pool>` interface. ``` ########## docs/source/format/Security.rst: ########## @@ -180,6 +180,11 @@ their own risks. For example, buffer offsets and sizes encoded in IPC messages may be out of bounds for the IPC stream; Flatbuffers-encoded metadata payloads may carry incorrect offsets pointing outside of the designated metadata area. +Besides, the IPC format provides optional :ref:`buffer compression <buffer-compression>` Review Comment: ```suggestion In addition, the IPC format provides optional :ref:`buffer compression <buffer-compression>` ``` -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
