ChatGPT解决这个技术问题 Extra ChatGPT

How to tell Jackson to ignore a field during serialization if its value is null?

How can Jackson be configured to ignore a field value during serialization if that field's value is null.

For example:

public class SomeClass {
   // what jackson annotation causes jackson to skip over this value if it is null but will 
   // serialize it otherwise 
   private String someValue; 
}

P
Peter Wippermann

To suppress serializing properties with null values using Jackson >2.0, you can configure the ObjectMapper directly, or make use of the @JsonInclude annotation:

mapper.setSerializationInclusion(Include.NON_NULL);

or:

@JsonInclude(Include.NON_NULL)
class Foo
{
  String bar;
}

Alternatively, you could use @JsonInclude in a getter so that the attribute would be shown if the value is not null.

A more complete example is available in my answer to How to prevent null values inside a Map and null fields inside a bean from getting serialized through Jackson.


for my project, this worked: @JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL); somehow your annotation wasn't available.
The API changed a bit with the 2.0 release.
@ProgrammerBruce -1 change your answer accordingly since you're aware of the change.
Yeah, I just confirmed that the @JsonInclude notation doesn't work, but this works like a charm: @JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL) (I'm using Jackson 1.9.12 with Spring 3.2.2.)
@MartinAsenov - the answer shows the most recent API; it was changed from the @JsonSerialize syntax to @JsonInclude. The older syntax is deprecated.
d
davnicwil

Just to expand on the other answers - if you need to control the omission of null values on a per-field basis, annotate the field in question (or alternatively annotate the field's 'getter').

example - here only fieldOne will be omitted from the JSON if it is null. fieldTwo will always be included in the JSON regardless of if it is null.

public class Foo {

    @JsonInclude(JsonInclude.Include.NON_NULL) 
    private String fieldOne;

    private String fieldTwo;
}

To omit all null values in the class as a default, annotate the class. Per-field/getter annotations can still be used to override this default if necessary.

example - here fieldOne and fieldTwo will be omitted from the JSON if they are null, respectively, because this is the default set by the class annotation. fieldThree however will override the default and will always be included, because of the annotation on the field.

@JsonInclude(JsonInclude.Include.NON_NULL)
public class Foo {

    private String fieldOne;

    private String fieldTwo;
    
    @JsonInclude(JsonInclude.Include.ALWAYS)
    private String fieldThree;
}

UPDATE

The above is for Jackson 2. For earlier versions of Jackson you need to use:

@JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL) 

instead of

@JsonInclude(JsonInclude.Include.NON_NULL)

If this update is useful, please upvote ZiglioUK's answer below, it pointed out the newer Jackson 2 annotation long before I updated my answer to use it!


shouldn't the annotation on the field be ALWAYS to override ?
@AbhinavVishak you are right - thanks! It was a copy-paste typo when I updated the answer to use Jackson 2. Edited.
@JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL) is deprecated
@Yar yes, that's deprecated in Jackson 2.x. I've stated that you need to use that only in earlier versions of Jackson where not only it is not deprecated, it's the only option.
W
WTK

With Jackson > 1.9.11 and < 2.x use @JsonSerialize annotation to do that:

@JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL)


Nowadays (Jackson 2.x) is this approach deprecated.
@JsonInclude(JsonInclude.Include.NON_NULL)
@JsonSerialize(using = FooSerializer.class, include = JsonSerialize.Inclusion.NON_NULL) doesn't work. nullable values are serialized.
It's deprecated but if you need to maintain old stuff this answer is totally fine! so thanks @WTK :)
As a side note, Jackson 1.9.12 is standard in WebSphere 8.5, hopefully this info will save someone else a lot of time it took me to figure this out :-)
M
Matthew Read

In Jackson 2.x, use:

@JsonInclude(JsonInclude.Include.NON_NULL)

is this to be placed on the field.
@ams , this annotation should wrapper a class
Could you also include the fully qualified name? Jackson has multiple annotations with the same name and a different package, so that is ambiguous.
are you saying there are multiple @JsonInclude annotations in Jackson? I had no idea. What should the fully qualified name be then? feel free to edit the answer
Confusion with names is most likely due to Jackson 1.x and 2.x using different Java packages for everything, to avoid class loader conflicts (wrt incompatible class versions). Since this answer is for 2.x, package for annotations would be com.fasterxml.jackson.annotation -- Jackson 1.x had org.codehaus.jackson.annoation
A
Arturo Volpe

You can use the following mapper configuration:

mapper.getSerializationConfig().setSerializationInclusion(Inclusion.NON_NULL);

Since 2.5 you can user:

mapper.setSerializationInclusion(Include.NON_NULL);

Since this is deprecated in 1.9, use mapper.getSerializationConfig().withSerializationInclusion(JsonSerialize.Inclusion.NON_NULL);
..or directly: mapper.setSerializationInclusion(NON_NULL);
@ruslan: Probably because the documentation of getSerializationConfig() says: Note that since instances are immutable, you can NOT change settings by accessing an instance and calling methods: this will simply create new instance of config object.
For 2.5.4 use mapper.setSerializationInclusion(Include.NON_NULL);
p
pXel

You can set application.properties:

spring.jackson.default-property-inclusion=non_null

or application.yaml:

spring:
  jackson:
    default-property-inclusion: non_null

http://docs.spring.io/spring-boot/docs/current/reference/html/common-application-properties.html


a
alfthan

in my case

@JsonInclude(Include.NON_EMPTY)

made it work.


NON_EMPTY is subtly different from NON_NULL - it will ignore null values, that's true, but will also ignore values considered empty, which may not be the desired behaviour. See the Jackson javadocs for more info
i like this answer because returning Optional from things that are really optional is a good idea, and with just NON_NULL you would get something like { } for null, which pointlessly transfers a Java idiom to the consumer. same with AtomicReference--the consumer doesn't care how the developer chose to enforce thread safety on the internal representation of the response.
N
Neha Gangwar
@JsonInclude(JsonInclude.Include.NON_NULL)
@JsonInclude(JsonInclude.Include.NON_EMPTY)

should work.

Include.NON_EMPTY indicates that property is serialized if its value is not null and not empty. Include.NON_NULL indicates that property is serialized if its value is not null.


JsonInclude.Include.NON_EMPTY - is enough since it covers NOT_NULL case
D
Deva

This Will work in Spring boot 2.0.3+ and Jackson 2.0+

import com.fasterxml.jackson.annotation.JsonInclude;

@JsonInclude(JsonInclude.Include.NON_NULL)
public class ApiDTO
{
    // your class variable and 
    // methods
}

That same @JsonInclude(JsonInclude.Include.NON_NULL) worked for me on Spring boot 2.1.2 and Jackson annotations 2.9.0
@manasouza Yes, they have maintained consistency to all updates.
I
Ilia Kurtov

If you want to add this rule to all models in Jackson 2.6+ use:

mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);

a
acdcjunior

If in Spring Boot, you can customize the jackson ObjectMapper directly through property files.

Example application.yml:

spring:
  jackson:
    default-property-inclusion: non_null # only include props if non-null

Possible values are:

always|non_null|non_absent|non_default|non_empty

More: https://docs.spring.io/spring-boot/docs/current/reference/html/howto-spring-mvc.html#howto-customize-the-jackson-objectmapper


B
Bilal BBB

For Jackson 2.5 use :

@JsonInclude(content=Include.NON_NULL)

I
Ihor Patsian

If you're trying to serialize a list of object and one of them is null you'll end up including the null item in the JSON even with

mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);

will result in:

[{myObject},null]

to get this:

[{myObject}]

one can do something like:

mapper.getSerializerProvider().setNullValueSerializer(new JsonSerializer<Object>() {
        @Override
        public void serialize(Object obj, JsonGenerator jsonGen, SerializerProvider unused)
                throws IOException
        {
            //IGNORES NULL VALUES!
        }
    });

TIP: If you're using DropWizard you can retrieve the ObjectMapper being used by Jersey using environment.getObjectMapper()


p
prateek_cs_2012

This has been troubling me for quite some time and I finally found the issue. The issue was due to a wrong import. Earlier I had been using

com.fasterxml.jackson.databind.annotation.JsonSerialize

Which had been deprecated. Just replace the import by

import org.codehaus.jackson.map.annotate.JsonSerialize;
import org.codehaus.jackson.map.annotate.JsonSerialize.Inclusion;

and use it as

@JsonSerialize(include=Inclusion.NON_NULL)

X
Xelian

Global configuration if you use Spring

@Configuration
public class JsonConfigurations {

    @Bean
    public Jackson2ObjectMapperBuilder objectMapperBuilder() {
        Jackson2ObjectMapperBuilder builder = new Jackson2ObjectMapperBuilder();
        builder.serializationInclusion(JsonInclude.Include.NON_NULL);
        builder.serializationInclusion(JsonInclude.Include.NON_EMPTY);
        builder.failOnUnknownProperties(false);
        return builder;
    }

}

Setting the serializationInclusion does not add one on another. public Jackson2ObjectMapperBuilder serializationInclusion(JsonInclude.Include serializationInclusion) { this.serializationInclusion = serializationInclusion; return this; } ; One should use the greater radius of inclusion enumeration. e.g NON_ABSENT includes NON_NULL and NON_EMPTY includes both. Thus it only should be builder.serializationInclusion(JsonInclude.Include.NON_EMPTY); JacksonInclude doc
佚名

We have lot of answers to this question. This answer may be helpful in some scenarios If you want to ignore the null values you can use the NOT_NULL in class level. as below

@JsonInclude(Include.NON_NULL)
class Foo
{
  String bar;
}

Some times you may need to ignore the empty values such as you may have initialized the arrayList but there is no elements in that list.In that time using NOT_EMPTY annotation to ignore those empty value fields

@JsonInclude(Include.NON_EMPTY)
class Foo
{
  String bar;
}

N
Nguyen Minh Hien

Case one

@JsonInclude(JsonInclude.Include.NON_NULL)
private String someString;

Case two

@JsonInclude(JsonInclude.Include.NON_EMPTY)
private String someString;

If someString is null, it will be ignored on both of cases. If someString is "" it just only be ignored on case two.

The same for List = null or List.size() = 0


m
mekdev

Jackson 2.x+ use

mapper.getSerializationConfig().withSerializationInclusion(JsonInclude.Include.NON_NULL);

.withSerializationInclusion(JsonInclude.Include.NON_NULL) instead right ?
Thanks for pointing that out, I'll hold off from upgrading :-(
@ruslan: Probably because the documentation of getSerializationConfig() says: Note that since instances are immutable, you can NOT change settings by accessing an instance and calling methods: this will simply create new instance of config object.
a
atom88

Also, you have to change your approach when using Map myVariable as described in the documentation to eleminate nulls:

From documentation:
com.fasterxml.jackson.annotation.JsonInclude

@JacksonAnnotation
@Target(value={ANNOTATION_TYPE, FIELD, METHOD, PARAMETER, TYPE})
@Retention(value=RUNTIME)
Annotation used to indicate when value of the annotated property (when used for a field, method or constructor parameter), or all properties of the annotated class, is to be serialized. Without annotation property values are always included, but by using this annotation one can specify simple exclusion rules to reduce amount of properties to write out.

*Note that the main inclusion criteria (one annotated with value) is checked on Java object level, for the annotated type, and NOT on JSON output -- so even with Include.NON_NULL it is possible that JSON null values are output, if object reference in question is not `null`. An example is java.util.concurrent.atomic.AtomicReference instance constructed to reference null value: such a value would be serialized as JSON null, and not filtered out.

To base inclusion on value of contained value(s), you will typically also need to specify content() annotation; for example, specifying only value as Include.NON_EMPTY for a {link java.util.Map} would exclude Maps with no values, but would include Maps with `null` values. To exclude Map with only `null` value, you would use both annotations like so:
public class Bean {
   @JsonInclude(value=Include.NON_EMPTY, content=Include.NON_NULL)
   public Map<String,String> entries;
}

Similarly you could Maps that only contain "empty" elements, or "non-default" values (see Include.NON_EMPTY and Include.NON_DEFAULT for more details).
In addition to `Map`s, `content` concept is also supported for referential types (like java.util.concurrent.atomic.AtomicReference). Note that `content` is NOT currently (as of Jackson 2.9) supported for arrays or java.util.Collections, but supported may be added in future versions.
Since:
2.0

R
Rishab Jula

Try this -

@JsonSerialize(include=JsonSerialize.Inclusion.NON_NULL)
public class XYZ {
    
    protected String field1;
    
    protected String field2;
 }

And for non-null values (On getters/class level) -

@JsonSerialize(include=JsonSerialize.Inclusion.NON_EMPTY)