View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
000080010000-011: Historical Accesspublic2009-07-23 11:282012-02-10 16:54
ReporterWolfgang Mahnke Assigned ToWolfgang Mahnke  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.02 
Summary0000800: Support for multiple historical configurations of a Variable / Event Notifier
Description

Systems might have different history configurations for the same variable (and maybe also the same event notifier) with different settings (e.g. sample rate, duration, filter).

We need a way to expose this information in a way that a client is able to pick which history should be accessed. We introduced to allow a variable / notifier having several history configurations, but that does not allow a client to pick the history to read / update.

Therefore we should make history configuration unique for variables and notifiers (as we had before) but create a reference type that would be used by a server to reference variables / notifiers only introduced to provide additional history configurations. Client can access those to get to the concrete history of the history configuration.
With the standardized reference type clients know that those variables / notifiers are only introduced for additional history configurations and have no other semantic.

Additional Information

This was shortly discussed in the TelCo 21sd of July 2009.

TagsNo tags attached.
Commit Version
Fix Due Date

Activities

user2

2010-01-19 18:19

  ~0001497

Need clarification from you in a telecon. Please add this to agenda for a HA call you can attend.

Paul Hunkar

2010-08-27 14:19

developer   ~0002068

The addition of text describbing that the primary configuration has a fixed name and that secondard configuration with alternate names corrects the first part of this issue. What is currently not supported is the ability to request historical data from one of the particular historical configuration. At this point in time it is up to the server to select the historical data source that best matches the request for data.

If required a new Mantis issue can be entered for defining a new extensible historical parameter that would allow specifing the historical configuration (nodeid or name possibly) from which the historical data request is to be processed.

Randy Armstrong

2010-08-31 16:38

administrator   ~0002081

Discussed Telcon Aug 31st

Added ability to have multiple HA configs.
No action on adding ability to select HA config.

Issue History

Date Modified Username Field Change
2009-07-23 11:28 Wolfgang Mahnke New Issue
2010-01-19 18:19 user2 Note Added: 0001497
2010-01-19 18:19 user2 Assigned To => Wolfgang Mahnke
2010-01-19 18:19 user2 Status new => feedback
2010-08-27 14:19 Paul Hunkar Status feedback => resolved
2010-08-27 14:19 Paul Hunkar Resolution open => fixed
2010-08-27 14:19 Paul Hunkar Note Added: 0002068
2010-08-31 16:38 Randy Armstrong Status resolved => closed
2010-08-31 16:38 Randy Armstrong Note Added: 0002081
2012-02-10 16:54 Jim Luth Fixed in Version => 1.02