Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Managing high-frequency data streams in ONE Record #259

Open
aloccid-iata opened this issue Aug 12, 2024 · 0 comments
Open

Managing high-frequency data streams in ONE Record #259

aloccid-iata opened this issue Aug 12, 2024 · 0 comments
Labels

Comments

@aloccid-iata
Copy link
Collaborator

Problem Statement

Currently, ONE Record defines Sensor and Measurement Logistics objects to manage data streams from IoT devices. However, sensors can generate hundreds of data points in a short period, leading to an overwhelming number of change requests and a cluttered audit trail.

For this reason we would like to discuss a new way to handle high-frequency data streams.

@IATA-Cargo IATA-Cargo moved this to Backlog in API Changes Aug 12, 2024
@IATA-Cargo IATA-Cargo added the api label Aug 12, 2024
@IATA-Cargo IATA-Cargo assigned IATA-Cargo and unassigned IATA-Cargo Aug 12, 2024
@IATA-Cargo IATA-Cargo moved this from Backlog to In review in API Changes Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In review
Development

No branches or pull requests

2 participants