Release of v2.0.3

What's Changed

• WIP: support pull consumer by @aaron-ai in #67
• Add new ClientType: PULL_CONSUMER by @aaron-ai in #70
• Add Code: ILLEGAL_OFFSET by @xdkxlk in #72
• Add code OFFSET_NOT_FOUND by @xdkxlk in #77
• [ISSUE #78] add attempt_id in ReceiveMessageRequest by @xdkxlk in #79
• [ISSUE #80] Update document for pull-related RPC by @xdkxlk in #81
• Add comments for pull-related RPC by @aaron-ai in #82

Full Changelog: v2.0.2...v2.0.3

Release 2.0.3 of java

See: v2.0.3

Release of v2.0.2

What's Changed

• [ISSUE #65] Add long_polling_timeout for ReceiveMessageRequest by @drpmma in #66

Full Changelog: v2.0.1...v2.0.2

Release 2.0.2 of java

See: v2.0.2

Release of v2.0.1

What's Changed

• add ILLEGAL_POLLING_TIME by @xdkxlk in #63
• add dlq information to message's systemProperties by @lollipopjin in #64

Full Changelog: v2.0...v2.1.0

Release 2.0.1 of java

See: v2.0.1

Release of v2.0

Changelog:

• Bi-directional stream API is used, allowing servers to issue
  diagnosing telemetry commands to clients;
• Server side stream API is employed for receive message API, which
  mitigates costs of serialization/deserialization of large data chunks
• Error codes are re-organized, roughly following HTTP semantics. Each
  code now has five digits, the first three of them complies HTTP status
  code; The rest two digits are used to specify each exact scenario.
• A few concepts are renamed to follow RocketMQ 5.x terminologies.

Release 2.0.0 of Java

Release java generate code by gRPC and Protocol Buffer through the IDL. The version number will follow the version of corresponding IDL.

• Adapt to the v2 protocol
• Bump gRPC-java to 1.47.0
• Bump protobuf to 3.21.1

See more from here.

Release v2.0-alpha

Changelog:

1. Bi-directional stream API is used, allowing servers to issue
   diagnosing telemetry commands to clients;
2. Server side stream API is employed for receive message API, which
   mitigates costs of serialization/deserialization of large data chunks
3. Error codes are re-organized, roughly following HTTP semantics. Each
   code now has five digits, the first three of them complies HTTP status
   code; The rest two digits are used to specify each exact scenario.
4. A few concepts are renamed to follow RocketMQ 5.x terminologies.

Release of v1.0

Release of v1.0