From 82f2b4cbc16485a15c2979c1c681d50c47e30062 Mon Sep 17 00:00:00 2001 From: Stanislav Bogatyrev Date: Sat, 20 Feb 2021 11:10:36 +0300 Subject: [PATCH] [#135] Clarify empty search filter behaviour It may be confusing for the user to get all types of objects as the result of a search with no filters set. Human users may expect to see only the objects intended for direct manipulation by humans. Signed-off-by: Stanislav Bogatyrev --- object/service.proto | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/object/service.proto b/object/service.proto index b975945..5bcb095 100644 --- a/object/service.proto +++ b/object/service.proto @@ -308,6 +308,11 @@ message SearchRequest { // Filter structure checks if object header field or attribute content // matches a value. // + // If no filters set, search request will return all objects of the + // container, including Regular object, Tombstones and Storage Group + // objects. Most human users expect to get only object they can directly + // work with. In that case the `$Object:ROOT` filter should be used. + // // By default `key` field refers to the corresponding object's `Attribute`. // Some Object's header fields can also be accessed by adding `$Object:` // prefix to the name. Here is the list of fields available via this prefix: