Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-11618

Add Connection - Add a Kafka Connection

    Details

    • Type: New Feature
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.0
    • Component/s: UI
    • Labels:
    • Epic Link:
    • Sprint:
      UP5 Sprint 1, UP5 Sprint 2
    • Release Notes:
      UI: Add Kafka Connection in Data Preparation
    • Rank:
      1|hzy0u2:

      Description

      As a user, I want to add a connection to a Kafka source.

      Workflow

      • I can add a connection by selecting "+ Add Connection" and selecting "Kafka"
      • A modal is displayed.
      • Title:"Add Connection: Kafka"
      • Content:
        "Name": text box; hint text: "Name this connection (30 characters max)"
        "Connection Type": toggle between "Kafka" and "Zookeeper"
        • KAFKA: "Broker Host": text box and "Port": numeric text field (default value: 9092)
        • ZOOKEEPER: "Zookeeper Host": text box and "Port": numeric text field (default value: 9092)
        Links: [Add Connection] [Test Connection]

      ADVANCED MODE: ask Bhooshan for details

      Acceptance Criteria

      • Connections are specific to Namespaces:
        • Databases added to a namespace is unique to that namespace.
        • If I want to connect a database to multiple namespaces, I will need to connect each namespace to a database.
      • Name of the source is unique. When the user set up a new source, the system validates that no other sources in the Namespace are named the same.
      • Character limit for the name of a source is set to 30. The user cannot type names that are longer than 30 characters.
      • The modal closes by clicking [x]. Any information added in the text fields will be lost.
      • [Add Connection] is disabled until all required fields are completed.
      • An error message is displayed if there is a problem with connecting or testing the connection. Error message: "CDAP can’t connect to the <Connection> source. Check the <field(s) names> input and try again."
        • Question: can we surface where and how the information failed? e.g. bad username or incorrect host, etc. and include it in the error message?
      • When "test connection" is successful, a success message is displayed: "The test connection to the <Connection> source was successful. " The message is displayed for 3 seconds before fading out
      • When a user [Add Connection] successfully:
        • Database category "folder" is added on the side left rail, displaying the newly created database with a label "New"
        • Label "New" disappears after 3 seconds.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                edwin Edwin Elia
                Reporter:
                lea Lea
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: