| **S3select** has a definite set of functionalities that should be implemented (if we wish to stay compliant with AWS), currently only a portion of it is implemented.
| The implemented software architecture supports basic arithmetic expressions, logical and compare expressions, including nested function calls and casting operators, that alone enables the user reasonable flexibility.
- | review the below feature-table_.
+ | review the below s3-select-feature-table_.
Error Handling
+.. _s3-select-feature-table:
Features Support
----------------
-.. _feature-table:
| Currently only part of `AWS select command <https://docs.aws.amazon.com/AmazonS3/latest/dev/s3-glacier-select-sql-reference-select.html>`_ is implemented, table below describes what is currently supported.
| The following table describes the current implementation for s3-select functionalities:
RGW object storage
~~~~~~~~~~~~~~~~~~
+* Initial support for S3 Select. See :ref:`s3-select-feature-table` for supported queries.
+
+* Bucket notification topics can be configured as ``persistent``, where events
+ are recorded in rados for reliable delivery.
+
+* Bucket notifications can be delivered to SSL-enabled AMQP endpoints.
+
+* Lua scripts can be run during requests and access their metadata.
+
+* SSE-KMS now supports KMIP as a key management service.
+
+* Multisite data logs can now be deployed on ``cls_fifo`` to avoid large omap
+ cluster warnings and make their trimming cheaper. See ``rgw_data_log_backing``.
+
CephFS distributed file system
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~