Java Destination SPI: start v.s. accept

Hi, I’m trying to develop a Java-based Destination, and looking into AirbyteMessageConsumer.

My question here is: What is the difference between start v.s. accept?

I saw some connectors have comment in start (or startTracked) like:

// todo (cgardens) - move contents of #write into this method.

So I guessed implementing everything in accept might somewhat work, but I was not sure of their difference.

Do you have Javadoc for them?

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

There’s some more information in

 * Interface for the destination's consumption of incoming records wrapped in an
 * {@link io.airbyte.protocol.models.AirbyteMessage}.
 * This is via the accept method, which commonly handles parsing, validation, batching and writing
 * of the transformed data to the final destination i.e. the technical system data is being written
 * to.
 * Lifecycle:
 * <ul>
 * <li>1. Instantiate consumer.</li>
 * <li>2. start() to initialize any resources that need to be created BEFORE the consumer consumes
 * any messages.</li>
 * <li>3. Consumes ALL records via {@link AirbyteMessageConsumer#accept(AirbyteMessage)}</li>
 * <li>4. Always (on success or failure) finalize by calling
 * {@link AirbyteMessageConsumer#close()}</li>
 * </ul>
 * We encourage implementing this interface using the {@link FailureTrackingAirbyteMessageConsumer}
 * class.

1 Like

Hi @sh4sh,

Ah, thanks. Sorry that I’ve overlooked your response.

Got it. I understood that :

  • start() would be responsible on “initialization” that can be performed before accept() without any parameter (AirbyteMessage)
  • accept() would do anything remaining to consume the actual data with the given parameter (AirbyteMessage)
  • Then, some connectors have had only accept() because it could just work.

I was just curious that Airbyte does not release its Java components to Maven Central, nor publish its Javadocs. But anyway, your informations helps. Thanks!

I’m glad that it is helpful! My understanding is that these block comments are compatible with Javadoc so we might already be set up to generate it?

To be honest I’m not very familiar with this, but I agree it would be great to have this spec easily available. Would you be willing to submit a documentation request to our Github repo to publish our Javadoc?

If you’re willing to publish Airbyte-related Java components to Maven Central, they would include Javadocs, and that would be the most popular way to publish OSS Javadocs. (unofficial, but semi de-facto standard OSS Javadoc container) will automatically get Javadocs from Maven Central.

But whether releasing the Java components to Maven Central, or not, would depend on what Airbyte thinks. I can just file a GitHub Issue if it helps.

For sure, please submit a request to our Github repo so our team can take a look and users can vote on it!