Google Git
Sign in
apache / doris-flink-connector / refs/heads/master
commit65d8c001cf2c6e2c6d72ddc94ffbccee37d25b3b[log] [tgz]
authorjqcc <897238475@qq.com>Fri Jun 20 10:42:35 2025 +0800
committerGitHub <noreply@github.com>Fri Jun 20 10:42:35 2025 +0800
treed9148e0a6a5408f9eb7718b75777d7625f2cfa32
parent9e06de984e199f352afd603f231976f9131d9eb7 [diff]
[Improve] support nested type fields in ArrayData (#606)
2 files changed
tree: d9148e0a6a5408f9eb7718b75777d7625f2cfa32
  1. .github/
  2. .mvn/
  3. flink-doris-connector/
  4. tools/
  5. .asf.yaml
  6. .gitignore
  7. .licenserc.yaml
  8. CODE_OF_CONDUCT.md
  9. CONTRIBUTING.md
  10. CONTRIBUTING_CN.md
  11. custom_env.sh.tpl
  12. env.sh
  13. LICENSE.txt
  14. mvnw
  15. NOTICE.txt
  16. README.md
README.md

Flink Connector for Apache Doris

License Join the Doris Community at Slack

Flink Doris Connector

Flink Doris Connector now support flink version from 1.11 to 1.20.

If you wish to contribute or use a connector from flink 1.13 (and earlier), please use the branch-for-flink-before-1.13

More information about compilation and usage, please visit Flink Doris Connector

License

Apache License, Version 2.0

How to Build

You need to copy customer_env.sh.tpl to customer_env.sh before build and you need to configure it before build.

git clone git@github.com:apache/doris-flink-connector.git
cd doris-flink-connector/flink-doris-connector
./build.sh

how-to-build

Code Style

Code Formatting

You need to install the google-java-format plugin. Spotless together with google-java-format is used to format the codes.

It is recommended to automatically format your code by applying the following settings:

  1. Go to “Settings” → “Other Settings” → “google-java-format Settings”.
  2. Tick the checkbox to enable the plugin.
  3. Change the code style to “Android Open Source Project (AOSP) style”.
  4. Go to “Settings” → “Tools” → “Actions on Save”.
  5. Under “Formatting Actions”, select “Optimize imports” and “Reformat file”.
  6. From the “All file types list” next to “Reformat code”, select “Java”.

For earlier IntelliJ IDEA versions, the step 4 to 7 will be changed as follows.

  • 4.Go to “Settings” → “Other Settings” → “Save Actions”.
  • 5.Under “General”, enable your preferred settings for when to format the code, e.g. “Activate save actions on save”.
  • 6.Under “Formatting Actions”, select “Optimize imports” and “Reformat file”.
  • 7.Under “File Path Inclusions”, add an entry for .*\.java to avoid formatting other file types. Then the whole project could be formatted by command mvn spotless:apply.

Checkstyle

Checkstyle is used to enforce static coding guidelines.

  1. Go to “Settings” → “Tools” → “Checkstyle”.
  2. Set “Scan Scope” to “Only Java sources (including tests)”.
  3. For “Checkstyle Version” select “8.14”.
  4. Under “Configuration File” click the “+” icon to add a new configuration.
  5. Set “Description” to “doris-flink-connector”.
  6. Select “Use a local Checkstyle file” and link it to the file tools/maven/checkstyle.xml which is located within your cloned repository.
  7. Select “Store relative to project location” and click “Next”.
  8. Configure the property checkstyle.suppressions.file with the value suppressions.xml and click “Next”.
  9. Click “Finish”.
  10. Select “doris-flink-connector” as the only active configuration file and click “Apply”.

You can now import the Checkstyle configuration for the Java code formatter.

  1. Go to “Settings” → “Editor” → “Code Style” → “Java”.
  2. Click the gear icon next to “Scheme” and select “Import Scheme” → “Checkstyle Configuration”.
  3. Navigate to and select tools/maven/checkstyle.xml located within your cloned repository.

Then you could click “View” → “Tool Windows” → “Checkstyle” and find the “Check Module” button in the opened tool window to validate checkstyle. Or you can use the command mvn clean compile checkstyle:checkstyle to validate.

Report issues or submit pull request

If you find any bugs, feel free to file a GitHub issue or fix it by submitting a pull request.

Contact Us

Contact us through the following mailing list.

NameScope
dev@doris.apache.orgDevelopment-related discussionsSubscribeUnsubscribeArchives

Links