Package org.apache.kafka.common.serialization

Class ShortDeserializer

java.lang.Object

org.apache.kafka.common.serialization.ShortDeserializer

All Implemented Interfaces:

Closeable, AutoCloseable, Deserializer<Short>

public class ShortDeserializer
extends Object
implements Deserializer<Short>

Constructor Summary

Constructors

Constructor	Description
ShortDeserializer()

Method Summary

Modifier and Type	Method	Description
Short	deserialize(String topic, byte[] data)	Deserialize a record value from a byte array into a value or object.
Short	deserialize(String topic, Headers headers, ByteBuffer data)	Deserialize a record value from a ByteBuffer into a value or object.

Methods inherited from class java.lang.Object

equals, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Methods inherited from interface org.apache.kafka.common.serialization.Deserializer

close, configure, deserialize

Constructor Details

ShortDeserializer

public ShortDeserializer()

Method Details

deserialize

public Short deserialize(String topic,
 byte[] data)

Description copied from interface: Deserializer

Deserialize a record value from a byte array into a value or object.

It is recommended to deserialize a null byte array to a null object.

Specified by:

deserialize in interface Deserializer<Short>

Parameters:

topic - topic associated with the data

data - serialized bytes; may be null

Returns:

deserialized typed data; may be null

deserialize

public Short deserialize(String topic,
 Headers headers,
 ByteBuffer data)

Description copied from interface: Deserializer

Deserialize a record value from a ByteBuffer into a value or object.

If ByteBufferDeserializer is used by an application, the application code cannot make any assumptions about the returned ByteBuffer like the position, limit, capacity, etc., or if it is backed by an array or not.

Similarly, if this method is overridden, the implementation cannot make any assumptions about the passed in ByteBuffer either.

It is recommended to deserialize a null ByteBuffer to a null object.

Note that the passed in Headers may be empty, but never null. The implementation is allowed to modify the passed in headers, as a side effect of deserialization. It is considered best practice to not delete or modify existing headers, but rather only add new ones.

Specified by:

deserialize in interface Deserializer<Short>

Parameters:

topic - topic associated with the data

headers - headers associated with the record

data - serialized ByteBuffer; may be null

Returns:

deserialized typed data; may be null