Giter VIP home page Giter VIP logo

apache-flink-kotlin-starter's People

Contributors

aedenj avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar

apache-flink-kotlin-starter's Issues

Why are sourcesets needed in the stock build.gradle?

The suggested build.gradle file, https://nightlies.apache.org/flink/flink-docs-release-1.13/docs/dev/datastream/project-configuration/#gradle, sets various properties on the sourceSets.

    sourceSets {
        main.compileClasspath += configurations.flinkShadowJar
        main.runtimeClasspath += configurations.flinkShadowJar

        test.compileClasspath += configurations.flinkShadowJar
        test.runtimeClasspath += configurations.flinkShadowJar

        javadoc.classpath += configurations.flinkShadowJar
    }

why exactly is this needed? Not doing so doesn't appear to have any immediate consequences.

Demonstrate Checkpointing

Demonstrate in standalone job, cluster job and consider demonstration on minikbue

state.backend: filesystem
state.checkpoints.dir: file:///tmp/flink-checkpoints
state.savepoints.dir: file:///tmp/flink-savepoints
execution.checkpointing.interval: 120000 ms
execution.checkpointing.mode: AT_LEAST_ONCE

restart-strategy.fixed-delay.attempts: 3
restart-strategy.fixed-delay.delay: 10 s

Remove illegal reflective access warning

The following message is output when the Flink starts,

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.flink.api.java.ClosureCleaner (file:/Users/aedenjameson/.gradle/caches/modules-2/files-2.1/org.apache.flink/flink-core/1.14.3/8a608d16c47ee4353d7c7d3f3fe1ce14a1489a96/flink-core-1.14.3.jar) to field java.lang.String.value
WARNING: Please consider reporting this to the maintainers of org.apache.flink.api.java.ClosureCleaner
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

If possible, remove.

Parameterize Create & Delete Topics Gradle Tasks

Currently the desired topic names are hardcoded in the gradle tasks. Can parameters be passed in? Or is this flexibility best achieved by just running the scripts/create-topics.sh script directly? It is nice having uniform mechanism for running developer tasks? Better yet, use Make as a task library instead.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.