oscerd commented on PR #23010:
URL: https://github.com/apache/camel/pull/23010#issuecomment-4388297340

   @apupier no — this should be a transparent upgrade for end-users.
   
   Looking at what actually lands in the generated 
`org.apache.camel.dataformat.ocsf.model.*` classes (the script generates with 
`profiles=[]`, so profile-bound attributes are filtered out in both versions):
   
   - **No fields are removed** from any of the 34 event classes or 68 reusable 
objects already generated for 1.7.0.
   - The change is purely additive: ~30 new fields across event classes (e.g. 
`app_protocol_name`, `network_observation_point`, `packet_list` on the network 
classes), ~15 new fields across reusable objects (e.g. `account.is_disabled`, 
`device.mac_vendor`, `api.token`), and 2 new top-level POJOs (`Packet`, 
`Token`).
   - Every existing OCSF event class UID is stable across 1.7.0 and 1.8.0.
   
   So routes that marshal/unmarshal OCSF events, populate fields via setters, 
or read existing getters keep working as-is. Existing 1.7.0 JSON payloads 
continue to deserialize cleanly. The only behavioural change is that fields 
newly typed in 1.8.0 (such as `packet_list` on the network activity classes) 
now land on a typed getter instead of `additionalProperties` — that's a 
non-breaking improvement.
   
   The one tiny caveat is the `OcsfConstants.SCHEMA_VERSION` constant value 
moves from `"1.7.0"` to `"1.8.0"`. The constant itself still exists with the 
same signature; only the string value changes, so code that hardcodes 
`equals("1.7.0")` against it would need to update.
   
   _Claude Code on behalf of Andrea Cosentino_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to