Uses of Package
org.yamcs.parameterarchive
Packages that use org.yamcs.parameterarchive
-
Classes in org.yamcs.parameterarchive used by org.yamcs.http.apiClassDescriptionThe parameter archive stores data in partitions(optional) -> intervals -> segments.Contains retrieval options used when extracting parameters from the parameter archive.an array of values for one
ParameterId -
Classes in org.yamcs.parameterarchive used by org.yamcs.parameterarchiveClassDescriptionBack-fills the parameter archive by triggering replays: - either regularly scheduled replays - or monitor data streams (tm, param) and keep track of which segments have to be rebuildBase class for all segments of values, timestamps or ParameterStatusBoolean value sgement uses BitSet to represent the boolean values as a set of bits32 bit integers encoded as deltas of deltas (good if the values are relatively constant or in increasing order)A collection of ParameterValueSegment with a common timeSegment.Segment for all non primitive types.The parameter archive stores data in partitions(optional) -> intervals -> segments.Stores a map between List<parameter_id> and ParameterGroup_id.The parameter archive gives each (fqn, rawType, engType) a numeric 32 bits pid.Stores a map (parameter_fqn, type) -> parameter_idA list of parametersIds with values all having the same timestampIterator over values of one (parameterId, group id)Contains retrieval options used when extracting parameters from the parameter archive.an array of values for one
ParameterIdStores parameter values for one parameter over a time range.RocksDb style iterator.Parameter Group segment - keeps references to Time and Value segments for a given parameter group and segment.Realtime archive filler task - it works even if the data is not perfectly sortedHolder, encoder and decoder for the segment keys (in the sense of key,value storage used for RocksDb)TimeSegment stores timestamps relative to a segmentStart.Interface for segments of columnar data.