pub struct VisualizationData {
pub data_source_end_token: Option<String>,
pub data_source_separator_token: Option<String>,
pub diagnostic_messages: Option<Vec<DiagnosticMessage>>,
pub end_key_strings: Option<Vec<String>>,
pub has_pii: Option<bool>,
pub indexed_keys: Option<Vec<String>>,
pub key_separator: Option<String>,
pub key_unit: Option<String>,
pub metrics: Option<Vec<Metric>>,
pub prefix_nodes: Option<Vec<PrefixNode>>,
}Expand description
There is no detailed description.
This type is not used in any activity, and only used as part of another schema.
Fields§
§data_source_end_token: Option<String>The token signifying the end of a data_source.
data_source_separator_token: Option<String>The token delimiting a datasource name from the rest of a key in a data_source.
diagnostic_messages: Option<Vec<DiagnosticMessage>>The list of messages (info, alerts, …)
end_key_strings: Option<Vec<String>>We discretize the entire keyspace into buckets. Assuming each bucket has an inclusive keyrange and covers keys from k(i) … k(n). In this case k(n) would be an end key for a given range. end_key_string is the collection of all such end keys
has_pii: Option<bool>Whether this scan contains PII.
indexed_keys: Option<Vec<String>>Keys of key ranges that contribute significantly to a given metric Can be thought of as heavy hitters.
key_separator: Option<String>The token delimiting the key prefixes.
key_unit: Option<String>The unit for the key: e.g. ‘key’ or ‘chunk’.
metrics: Option<Vec<Metric>>The list of data objects for each metric.
prefix_nodes: Option<Vec<PrefixNode>>The list of extracted key prefix nodes used in the key prefix hierarchy.
Trait Implementations§
Source§impl Clone for VisualizationData
impl Clone for VisualizationData
Source§fn clone(&self) -> VisualizationData
fn clone(&self) -> VisualizationData
1.0.0 · Source§fn clone_from(&mut self, source: &Self)
fn clone_from(&mut self, source: &Self)
source. Read more