SpringBoot一对多序列化时排除FitnessRecord关联User的name字段

Hey there! Let's work through how to strip out that name field from the nested User object when you return your FitnessRecord JSON via FitnessRecordRepository.findAll(). Here are a few practical approaches tailored to different scenarios:

1. Use Jackson's @JsonIgnoreProperties Annotation #

This is probably the quickest fix if you only need to exclude the name field specifically when returning FitnessRecord data. Just add the annotation to the user field in your FitnessRecord class, specifying which fields to ignore:

public class FitnessRecord {
    private Long fitness_id;
    private LocalDate date_of_performance;
    
    // Ignore the "name" field from the associated User object
    @JsonIgnoreProperties({"name"})
    private User user;
    
    // Getters and setters omitted for brevity
}

If you ever need to include the name field in other contexts (like when returning User data directly), this method won't interfere—since the ignore rule is only applied to the User instance nested inside FitnessRecord.

2. Use Jackson JSON Views for Granular Control #

If you need different sets of fields returned in different scenarios (e.g., include name for admin endpoints but exclude it for public ones), JSON Views are perfect.

First, define view interfaces:

public class Views {
    // Base view for public-facing data
    public static class Public {}
    // Extended view for more detailed data
    public static class ExtendedPublic extends Public {}
}

Then annotate your User class fields with the appropriate views:

public class User {
    @JsonView(Views.Public.class)
    private Long user_id;
    
    // Only include this in the extended view
    @JsonView(Views.ExtendedPublic.class)
    private String name;
    
    @JsonView(Views.Public.class)
    private String email;
    
    // Getters and setters omitted
}

Finally, apply the Public view to your controller method that returns FitnessRecord data:

@RestController
public class FitnessRecordController {
    @Autowired
    private FitnessRecordRepository repo;
    
    @JsonView(Views.Public.class)
    @GetMapping("/fitness-records")
    public List<FitnessRecord> getAllRecords() {
        return repo.findAll();
    }
}

3. Use Spring Data Projections (Performance-Friendly) #

If you want to avoid fetching the name field from the database entirely (which boosts performance), use a Spring Data Projection. This lets you define exactly which fields you want to retrieve.

First, create projection interfaces:

// Projection for FitnessRecord
public interface FitnessRecordProjection {
    Long getFitness_id();
    LocalDate getDate_of_performance();
    // Nested projection for User
    UserProjection getUser();
    
    interface UserProjection {
        Long getUser_id();
        String getEmail();
    }
}

Then update your repository to return this projection:

public interface FitnessRecordRepository extends JpaRepository<FitnessRecord, Long> {
    List<FitnessRecordProjection> findAll();
}

When you call findAll(), Spring Data will generate a query that only selects the fields defined in the projections—so the name field isn't even fetched from the database, and the resulting JSON will automatically exclude it.

All of these methods will get you your desired JSON output:

{ "fitness_id": 1, "date_of_performance": "2018-04-06", "user": { "user_id": 1, "email": "hilalkaldane@gmail.com" } }

内容的提问来源于stack exchange，提问作者user6192854