Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement nats avro serdes #5195

Merged
merged 1 commit into from
Sep 18, 2024

Conversation

carlesarnal
Copy link
Member

No description provided.

@carlesarnal carlesarnal merged commit dbb071b into Apicurio:main Sep 18, 2024
19 checks passed
@carlesarnal carlesarnal deleted the avro-nats-serdes-impl branch September 18, 2024 13:15

T getPayload();

void ack();

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add Nack() and Term() also.


public static final Integer NATS_PORT = 4222;

public static final Integer NATS_MGMT_PORT = 8222;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

8222 is considered to be a monitoring port, can we rename this field to NATS_MNTR_PORT ?


NatsConsumerRecord<T> receive() throws JetStreamApiException, IOException;

NatsConsumerRecord<T> receive(Duration timeout) throws JetStreamApiException, IOException;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's rename it to fetch ?
NATS does not uses receive but pull or fetch.
Difference between pull and fetch is, fetch return the list of messages while pull keeps the message in in memory iterator and users then have to next() to read message from iterator.


public interface NatsProducer<T> extends AutoCloseable {

void send(T message) throws ApicurioNatsException;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

let's rename it to publish and add publishAsync too ?

@carlesarnal
Copy link
Member Author

Good comments, I'm going to create an issue so we can track them better.

@carlesarnal
Copy link
Member Author

@sourabhaggrawal I have created the following GH issue to track your comments: #5215. Would you be open to contribute a PR to address them?

@souravagrawal
Copy link

Thank you @carlesarnal, I have submitted PR for changes #5222

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants