Skip to content

Feat/schema field rename - #363

Merged
viktorbeck98 merged 4 commits into
developmentfrom
feat/schema-field-rename
Oct 15, 2026
Merged

viktorbeck98 merged 4 commits into
developmentfrom
feat/schema-field-rename

Conversation

@viktorbeck98

@viktorbeck98 viktorbeck98 commented Oct 12, 2026 •

Copy link
Copy Markdown
Collaborator

Task

Description

How Has This Been Tested?

Checklist

  • This Pull-Request goes to the development branch.
  • I have successfully run prek locally.
  • I have added tests to cover my changes.
  • I have linked the issue-id to the task-description.
  • I have performed a self-review of my own code.

View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

EventID -> eventID, logFormatVariables -> headerVariables, alertsObtain -> alertDetails, extractedTimestamps -> logTimestamps, detectionTimestamp -> detectedTimestamp, outputTimestamp -> aggregatedTimestamp, __version__ -> schemaVersion. Field numbers and types are unchanged, so the binary wire format stays. Breaking: no aliases for the old names.

Refs #127

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@viktorbeck98
viktorbeck98 changed the base branch from main to development October 12, 2026 21:40
Base automatically changed from development to main October 13, 2026 07:29
Reverts the __version__ -> schemaVersion part of the rename. The schema version value stays at 2.0.0 for the other six renames.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@viktorbeck98
viktorbeck98 changed the base branch from main to development October 14, 2026 07:40
Apply the field rename to code that came in with development
(alert aggregation templates, alerts.json fixture, basic_concat).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@viktorbeck98
viktorbeck98 requested a review from ipmach October 14, 2026 08:14
@viktorbeck98
viktorbeck98 marked this pull request as ready for review October 14, 2026 08:14

@ipmach ipmach left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a little problematic because we have a demo coming soon, so it is important that before that:

  • DetectMateService does not raises errors.
  • Alina and Lukas codes do not stop working.

Can you make sure that everyone is ok with this change?

Comment thread tests/test_schemas/test_field_rename.py Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is redundant, it should be delete it

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

def deserialize(schema_class: SchemaT, message: bytes) -> SchemaT:

I think this function should have an error raise if the receive an schema 1.0.0. Because 2.0.0 is not backward compatible

@viktorbeck98
viktorbeck98 merged commit aeeecb5 into development Oct 15, 2026
4 checks passed
@viktorbeck98
viktorbeck98 deleted the feat/schema-field-rename branch October 15, 2026 14:20
viktorbeck98 added a commit that referenced this pull request Oct 15, 2026
Follow the schema field rename (#363) in the JsonParser fix.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
viktorbeck98 added a commit that referenced this pull request Oct 15, 2026
Follow the schema field rename (#363) in the docs changes, keep the
config Field descriptions and add one for deduplicate_values, and
regenerate the configuration argument tables.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants