[
https://issues.apache.org/jira/browse/ARROW-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16830348#comment-16830348
]
Antoine Pitrou commented on ARROW-2835:
---------------------------------------
I'm leaning towards #1, because it helps expose bugs.
As a sidenote, Tensorflow's RandomAccessFile only supports ReadAt-like
operation, not implicit positioning with Seek() or Tell(). See
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/platform/file_system.h#L231
> [C++] ReadAt/WriteAt are inconsistent with moving the files position
> --------------------------------------------------------------------
>
> Key: ARROW-2835
> URL: https://issues.apache.org/jira/browse/ARROW-2835
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Dimitri Vorona
> Priority: Major
> Fix For: 0.14.0
>
>
> Right now, there is inconsistent behaviour regarding moving the files
> position pointer after calling ReadAt or WriteAt. For example, the default
> implementation of ReadAt seeks to the desired offset and calls Read which
> moves the position pointer. MemoryMappedFile::ReadAt, however, doesn't change
> the position. WriteableFile::WriteAt seem to move the position in the current
> implementation, but there is no docstring which prescribes this behaviour.
> Antoine suggested that *At methods shouldn't touch the position and it makes
> more sense, IMHO. The change isn't huge and doesn't seem to break anything
> internally, but it might break the existing user code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
