You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sorry for the lack of clarity.
The above example is the json document put into elastic search by the population scripts developed at FRIB. The multi-value property would ease the mapping.
Additionally there are certain channels which might have properties with multiple values. A example could be a pv that has a property "system" and since it belongs to many systems should have values "linac", "linac-to-booster",...
My comment argued against adding such a feature right now and rather using property/tag naming conventions resolve this issue.
With the migration to the new backend some of the performance concerns associated with a large number of properties and tags should be resolved too.
The text was updated successfully, but these errors were encountered: