Package org.epics.archiverappliance
Interface StoragePlugin
-
- All Known Implementing Classes:
BlackholeStoragePlugin
,ChannelArchiverReadOnlyPlugin
,MergeDedupStoragePlugin
,PBOverHTTPStoragePlugin
,PlainPBStoragePlugin
public interface StoragePlugin extends Reader, Writer
The main interface for a storage plugin; this is an object that implements the reader and the writer interfaces. In addition, this has some methods to help in initialization.- Author:
- mshankar
-
-
Method Summary
Modifier and Type Method Description void
convert(BasicContext context, String pvName, ConversionFunction conversionFuntion)
Sometimes, PVs change types, EGUs etc.String
getDescription()
Get a string description of this plugin; one that can potentially be used in log messages and provide context.String
getName()
Multiple PVs will probably use the same storage area and we identify the area using the name.void
initialize(String configURL, ConfigService configService)
Each storage plugin is registered to a URI scheme; for example, the PlainStoragePBPlugin uses pb:// as the scheme.void
renamePV(BasicContext context, String oldName, String newName)
Change the name of a PV.-
Methods inherited from interface org.epics.archiverappliance.Reader
getDataForPV, getFirstKnownEvent
-
Methods inherited from interface org.epics.archiverappliance.Writer
appendData, getLastKnownEvent
-
-
-
-
Method Detail
-
getName
String getName()
Multiple PVs will probably use the same storage area and we identify the area using the name. This is principally used in capacity planning/load balancing to identify the storage area for the PV. We should make sure that storage's with similar lifetimes have the same name in all the appliances. The name is also used to identify the storage in the storage report. For example, the PlainPBStoragePlugin takes a name parameter and we should use something like STS as the identity for the short term store in all the appliances.- Returns:
- name
-
getDescription
String getDescription()
Get a string description of this plugin; one that can potentially be used in log messages and provide context.- Returns:
- description
-
initialize
void initialize(String configURL, ConfigService configService) throws IOException
Each storage plugin is registered to a URI scheme; for example, the PlainStoragePBPlugin uses pb:// as the scheme. Configuration for a storage plugin typically comes in as a URL like URI.- The config service identifies the storage plugin using the scheme ("pb" maps to PlainStoragePBPlugin)
- Creates an instance using the default constructor.
- Calls initialize with the complete URL.
- Parameters:
configURL
- The complete URLconfigService
-- Throws:
IOException
-- See Also:
StoragePluginURLParser
-
renamePV
void renamePV(BasicContext context, String oldName, String newName) throws IOException
Change the name of a PV. This happens occasionally in the EPICS world when people change the names of PVs but want to retain the data. This method is used to change the name of the PV in any of the datasets for PVoldName
. For example, in PB files, the name of the PV is encoded in the file names and is also stored in the header. In this case, we expect the plugin to move the data to new files names and change the PV name in the file header. To avoid getting into issues about data changing when renaming files, the PV can be assumed to be in a paused state.- Parameters:
context
-oldName
- The old PV namenewName
- The new PV name- Throws:
IOException
-
-
convert
void convert(BasicContext context, String pvName, ConversionFunction conversionFuntion) throws IOException
Sometimes, PVs change types, EGUs etc. In these cases, we are left with the problem of what to do with the already archived data. We can rename the PV to a new but related name - this keeps the existing data as is. Or, we can attempt to convert to the new type, EGU etc. This method can be used to convert the existing data using the supplied conversion function. Conversions should be all or nothing; that is, first convert all the streams into temporary chunks and then do a bulk rename once all the conversions have succeeded. Note that we'll also be using the same conversion mechanism for imports and other functions that change data. So, when/if implementing the conversion function, make sure we respect the typical expectations within the archiver - monotonically increasing timestamps and so on. To avoid getting into issues about data changing when converting, the PV can be assumed to be in a paused state.- Parameters:
context
-pvName
- The PV nameconversionFuntion
-- Throws:
IOException
-
-
-