Releases: JeffersonLab/jaws
Releases · JeffersonLab/jaws
v1.2.0
- Bump confluent-kafka Python API to 1.5.0, avro to 1.10.1, fastavro to 1.3.0
- Bump Debezium container to 1.4, registry container to 6.0.1
- Converted broker bash scripts to Python (no longer depend on Java broker install)
- Moved import-registrations.sh functionality into the set-registered.py script (no longer depend on Java/Confluent libs)
- Renamed /scripts/alarms to /scripts/client
- All scripts installed in Docker console container (again)
- Started to clean up schema registry scripts (probably need to convert to Python still...)
- Started to organize a plugins directory (working towards loosely coupled plugins w/schema references...)
- Updated documentation
v1.1.0
- Updated scripts to work outside of Docker containers (lookup path instead of assume /scripts)
- Updated set-registered.py to read locations and categories from schemas instead of hard-coded
- Updated list-registrations.py
- Added with --nometa and --category options
- Export format is now closer to what kafka-avro-console-consumer expects
- Added script delete-all-alarm-schemas.sh
- Updated documentation
- Updated schemas for JLab data
- maxshelveduration renamed maxshelvedduration
v1.0.0
- Organized scripts, added import registrations example
- Beginning to work through production issues on a VM (bump to 1.0.0 is signal of production readiness)
v0.10.0
- Fixed bug where tombstones crashed list-shelved.py
v0.9.0
- Shelved expiration timestamp is now optional (set to None for indefinite shelving)
- list-shelved.py now formats timestamp as a human readable date instead of an integer value representing milliseconds from Epoch
- set-shelved.py now accepts an optional duration in seconds for expiration (before it was a required expiration in milliseconds from Epoch)
Note: The timestamp is stored as milliseconds from Epoch UTC, and due to limitations in the standard Python library the formatted date remains in UTC at this time.
v0.8.0
- Removed boolean alarming and boolean ack fields from active-alarms basic record types as tombstone vs empty (but not null) record accomplishes the same thing
v0.7.0
- Include /schemas directory inside Docker container
v0.6.0
- active-alarms topic now has complex key (alarm name + message type)
- active-alarms topic messages include: Alarming, Ack, AlarmingEPICS, AckEPICS
v0.5.0
- Add "maxshelveduration" to registered-alarms
v0.4.0
- Updated docs and order of items in active-alarms-value schema (I'm attempting to match it exactly in Connect)