Skip to main content

Create a JAR application Limited availabilty

Aiven for Apache Flink® enables you to upload and deploy custom code as a JAR file, enhancing your Apache Flink applications with advanced data processing capabilities.

Prerequisite​

  • Custom JARs for Aiven for Apache Flink is a limited availability feature. To try this feature, request access by contacting the sales team.
  • Create a new Aiven for Apache Flink service and click Upload and deploy custom JARs to enable custom JARs during service creation.
note

Enabling Custom JARs for existing services is currently not possible. If you did not enable this feature during service creation, you must create a service with Custom JARs enabled.

Create and deploy application​

  1. Access the Aiven Console and select the Aiven for Apache Flink service where you want to deploy a JAR application.

  2. From the left sidebar, click Applications and then click Create application.

  3. In the Create application dialog, enter a name for your JAR application, and select JAR as the application type from the drop-down.

  4. Click Create application to proceed.

  5. Click Upload first version to upload the first version of the application.

    note

    There is a limit on the size of the custom JAR file you can upload to an Apache Flink JAR application. For more information, contact the sales or support team.

  6. In the Upload new version dialog:

    1. Click Choose file to select your custom JAR file.
    2. Select the Terms of Service checkbox to indicate your agreement.
    3. Click Upload version to upload your JAR file.

  7. After the upload, you are redirected to the application'soverview page.

  8. To deploy the application, click Create deployment. In the Create new deployment dialog:

    1. Select the application version to deploy.
    2. Select a savepoint if you wish to deploy from a specific state. No savepoints are available for the first application deployment.
    3. Toggle Restart on failure to automatically restart Flink jobs upon failure. See Restart strategy in SQL and JAR applications for details.
    4. In the Program args field, provide command-line arguments consisting of variables and configurations relevant to your application'slogic upon submission. Each argument is limited to 64 characters, with a total limit of 32 separate items.
    5. Specify the number of parallel instances you require for the task.

  9. Click Deploy without a savepoint to begin the deployment process.

  10. While deploying, the application status shows Initializing. Once deployed, the status changes to Running.