editorial

Signed-off-by: gal salomon <gal.salomon@gmail.com>

diff --git a/PendingReleaseNotes b/PendingReleaseNotes
index e79b04fdf9fd385e984449deb77082e9e62c17d3..3c5762c26c619d36689049dc77322ea092c2699d 100644 (file)
--- a/PendingReleaseNotes
+++ b/PendingReleaseNotes
@@ -48,15 +48,10 @@
   upgrading the sole active MDS for a file system.
 
 * Parquet implementation is about accessing columnar objects(Parquet format) 
-  using s3select queries.
-  The s3select-engine contains a Parquet-reader(apache/arrow) that enables access
-  to specific columns according to query, which saves a lot of IOPS.
-  The s3select-engine is using (call-back) GetObj-RangeScan to access these types 
-  of objects.
-  The Parquet object is identified by its name(*.parquet) and magic-number exists 
-  in objects. thus, upon sending s3select query, there are 2 main flows, one 
-  for CSV the other for Parquet format.
-  RGW chooses the flow according the object name.
+  using Parquet reader(apache arrow) that will eventually save a lot of IOPS.
+  The s3select-engine(RGW submodule) contains that Parquet-reader.
+  The Parquet object is identified by its name(*.parquet) and by the magic-number exists 
+  in objects.
 
 * RGW: RGW now supports rate limiting by user and/or by bucket.
   With this feature it is possible to limit user and/or bucket, the total operations and/or