1. 22 7月, 2020 1 次提交
  2. 08 6月, 2020 1 次提交
  3. 18 5月, 2020 1 次提交
  4. 17 5月, 2020 1 次提交
  5. 24 2月, 2020 1 次提交
  6. 21 2月, 2020 1 次提交
  7. 13 1月, 2020 1 次提交
  8. 17 12月, 2019 1 次提交
  9. 10 12月, 2019 1 次提交
  10. 05 9月, 2019 1 次提交
  11. 01 8月, 2019 1 次提交
  12. 12 7月, 2019 2 次提交
  13. 11 4月, 2019 1 次提交
  14. 25 2月, 2019 1 次提交
  15. 31 1月, 2019 1 次提交
    • T
      [FLINK-11064] [table] Setup a new flink-table module structure · 0ab1549f
      Timo Walther 提交于
      This commit splits the flink-table module into multiple submodules in
      accordance with FLIP-32 (step 1).
      
      The new module structure looks as follows:
      
      flink-table-common
             ^
             |
      flink-table-api-java <------- flink-table-api-scala
             ^                                 ^
             |                                 |
      flink-table-api-java-bridge    flink-table-api-scala-bridge
             ^
             |
      flink-table-planner
      
      The module structure assumes that the type system has been reworked such
      that only one table environment exists for both Java and Scala users.
      
      The module `flink-table-planner` contains the content of the old
      `flink-table` module. From there we can distribute ported classes to
      their final module without breaking backwards compatibility or
      force users to update their dependencies again.
      
      For example, if a user wants to implement a pure table program in Scala,
      `flink-table-api-scala` and `flink-table-planner` need to be
      added to the project.
      
      Until we support pure table programs, `flink-table-api-scala/java-bridge`
      and `flink-table-planner` need to be added to the project.
      
      This closes #7587.
      0ab1549f
  16. 04 1月, 2019 1 次提交
  17. 30 11月, 2018 1 次提交
  18. 20 11月, 2018 1 次提交
  19. 09 11月, 2018 1 次提交
  20. 03 11月, 2018 1 次提交
  21. 20 7月, 2018 1 次提交
  22. 17 7月, 2018 1 次提交
  23. 29 5月, 2018 1 次提交
  24. 15 3月, 2018 1 次提交
  25. 28 2月, 2018 1 次提交
  26. 27 2月, 2018 1 次提交
  27. 16 2月, 2018 1 次提交
  28. 22 11月, 2017 1 次提交
  29. 07 11月, 2017 2 次提交
  30. 03 11月, 2017 3 次提交
  31. 02 11月, 2017 1 次提交
  32. 01 11月, 2017 1 次提交
    • A
      [FLINK-7902] Use TypeSerializer in TwoPhaseCommitSinkFunctions · 0ba528c7
      Aljoscha Krettek 提交于
      We use custom serializers to ensure that we have control over the
      serialization format, which allows us easier evolution of the format in
      the future.
      
      This also implements custom serializers for KafkaProducer11, the only
      TwoPhaseCommitSinkFunction we currently have.
      0ba528c7
  33. 10 10月, 2017 1 次提交
  34. 07 8月, 2017 1 次提交
  35. 23 7月, 2017 1 次提交
  36. 28 5月, 2017 1 次提交