AlenkaF commented on code in PR #41593:
URL: https://github.com/apache/arrow/pull/41593#discussion_r1764916919


##########
docs/source/format/Intro.rst:
##########
@@ -0,0 +1,485 @@
+.. 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.
+
+************
+Introduction
+************
+
+Apache Arrow was born from the need for a set of standards around
+tabular data representation and interchange between systems.
+The adoption of these standards reduce computing costs of data
+serialization/deserialization and implementation costs across
+systems implemented in different programming languages.
+
+The Apache Arrow specification can be implemented in any programming
+language but official implementations for many languages are available.
+An implementation consists of format definitions using the constructs
+offered by the language and common in-memory data processing algorithms
+(e.g. slicing and concatenating). Users can extend and use the utilities
+provided by the Apache Arrow implementation in their programming
+language of choice. Some implementations are further ahead and feature a
+vast set of algorithms for in-memory analytical data processing.
+
+As the format gets more adoption, it becomes easier for data processing
+systems to exchange tabular data. Among other things, an agreed upon
+in-memory format, enables the implementations of zero-copy IPC protocols
+(inter-process communication without copying data in memory) and
+more efficient reading and writing of file formats like CSV, `Apache ORC`_,
+and `Apache Parquet`_.

Review Comment:
   I have reverted the change in the last paragraph of the intro section from 
https://github.com/apache/arrow/pull/41593/commits/e2dc4bfb5505bc042b9ee9ebb3c69e93aec5937c.
 The change can be seen here: 
https://github.com/apache/arrow/pull/41593/commits/581daf346e80dceffc5291f78cb5149e6b4d3c4e.
   
   Would you agree with the intro now @jorisvandenbossche @felipecrv ?



-- 
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]

Reply via email to