Uploaded image for project: 'Kafka'
  1. Kafka
  2. KAFKA-1865

Add a flush() call to the new producer API

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 0.9.0.0
    • None
    • None

    Description

      The postconditions of this would be that any record enqueued prior to flush() would have completed being sent (either successfully or not).

      An open question is whether you can continue sending new records while this call is executing (on other threads).

      We should only do this if it doesn't add inefficiencies for people who don't use it.

      Attachments

        Issue Links

        blocks

        Bug - A problem which impairs or prevents the functions of the product. SAMZA-524 Update KafkaSystemProducer after Kafka provides a flush behavior

        • Major - Major loss of function.
        • Resolved
        is related to

        Bug - A problem which impairs or prevents the functions of the product. SAMZA-227 Upgrade KafkaSystemProducer to new API

        • Major - Major loss of function.
        • Resolved
        relates to

        Bug - A problem which impairs or prevents the functions of the product. KAFKA-1863 Exception categories / hierarchy in clients

        • Major - Major loss of function.
        • Resolved

        Activity
          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jkreps Jay Kreps
            jkreps Jay Kreps
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment