-
Type: Bug
-
Status: Resolved
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.4.1
-
Fix Version/s: 3.13.0
-
Component/s: Page Providers
-
Epic Link:
-
Tags:
-
Backlog priority:800
-
Sprint:NOS end Feb 11.1.3, NOS 11.1.6 - 2019-04 1, NOS 11.1.8 - 2019-05 01, NOS 11.1.9 - 2019-05 02, NOS 11.1.10 - 2019-06 01, NOS 11.1.11 - 2019-06 02
-
Story Points:3
When defining a Terms aggregate for a page provider, blob sub-fields properties (e.g. properties for file:content) are not exposed, which makes it impossible to define an aggregate on e.g. file:content/mime-type.
This is problematic because Nuxeo Server provides a way to search based on blob size in the default search, and this config can't be reproduced in Studio.
Expected:
sub fields should be exposed both for default blob field (file:content) and custom blob fields.
when a sub field is used, expose a warning
- in the popup
Using this field may impact performance.
- in the feature validation
Usage of [field name] in [predicate or aggregate name] may impact performance.
- depends on
-
NXS-5322 Fix error when chosing multiple complex field in Page Provider predicates
- Resolved
1.
|
Format registries JSON file | Resolved | Mincong Huang |
|