apache/fory

[Java] Deserialization optimization, instead of discarding fields, puts non-existent fields into a specified field.

Open

#1,799 opened on Aug 13, 2024

View on GitHub
 (6 comments) (2 reactions) (1 assignee)Java (426 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (4,419 stars)
PR merge metrics
 (PR metrics pending)

Description

Is your feature request related to a problem? Please describe.

When the upstream and downstream attributes are inconsistent, for example, the upstream is 10 fields, the downstream is not synchronized to update the field attributes, and there are only 9 attributes, then the downstream non-existent attributes will be ignored during deserialization.

Describe the solution you'd like

In some scenarios, we don't want the attribute to be lost, so can we put the attribute into a specified field, such as the other field (a map collection)?

Contributor guide

Research direction
Tech stack
Domain
Issue type
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Prerequisites
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.