Conversation
…ogging https://hopsworks.atlassian.net/browse/FSTORE-1903 FSTORE-1871 reworked feature logging around a single combined logging feature group, while feature views that enabled logging before the upgrade keep their frozen pre-1871 pair of feature groups. Running model deployments and batch services embed old Python clients that must keep logging against those legacy feature groups with zero downtime, and new clients must keep working against them too. Document the upgrade compatibility contract on the feature logging user guide: pre-upgrade feature views keep working for old and new clients alike, purging converts them to the combined layout, enabling logging on new feature views requires a 4.6 or later client, and positional log() calls written for the pre-4.6 signature keep working on pre-upgrade feature views with the keyword form as the migration target. Also correct the enablement section, which still described the pre-4.6 pair of logging feature groups. Signed-off-by: Manu Sathyarajan Joseph <manu.joseph@logicalclocks.com> Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ogging https://hopsworks.atlassian.net/browse/FSTORE-1903 Pre-PR review fix for the FSTORE-1903 documentation: two sections of the feature logging guide still described the pre-4.6 layout. The materialize and delete sections described a pair of logs and the transformed argument as selecting one of them. They now state what the argument does on each layout: on the pre-4.6 pair delete_log() replaces the pair as a whole whichever slot is named, and on the combined layout there is a single log, so materialize_log(transformed=...) makes no difference and delete_log(transformed=True) does nothing. Signed-off-by: Manu Sathyarajan Joseph <manu.joseph@logicalclocks.com> Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
manu-sj
force-pushed
the
FSTORE-1903
branch
from
September 11, 2026 09:32
8ae455d to
bc02eca
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
FSTORE-1871 combined the logging feature groups, renamed label columns to
predicted_<label>and replacedhsml_modelwithmodel_name/model_version. Model deployments and batch services already running a pre-4.6 Hopsworks client must keep logging against an upgraded backend without any code change, and current clients must read and write the logging feature groups those old clients created.This repo documents the resulting behaviour for users: what a pre-4.6 client can and cannot do against an upgraded backend, and what happens to logging feature groups created before the upgrade, including the materialize and delete paths.
Test plan
🤖 Generated with Claude Code
https://claude.ai/code/session_01DxdV8jEhUKSKssaLexdYSQ