Skip to content

Fix/kafka connector build#696

Open
zhanglistar wants to merge 106 commits into
boostscale:mainfrom
bigo-sg:fix/kafka-connector-build
Open

Fix/kafka connector build#696
zhanglistar wants to merge 106 commits into
boostscale:mainfrom
bigo-sg:fix/kafka-connector-build

Conversation

@zhanglistar

Copy link
Copy Markdown

Fix Kafka connector build in the Velox monolithic build.

The previous build failed after enabling the Kafka connector for two reasons:

  1. Velox links against CppKafka::cppkafka, but the bundled cppkafka build only defines the cppkafka
    target. This caused CMake target resolution to fail.

  2. cppkafka exposes include/cppkafka as a public include directory. In the monolithic Velox build this
    include path leaked into unrelated targets, so Folly's #include <event.h> resolved to cppkafka/ event.h instead of the system libevent header. That broke Folly/libevent compilation with missing
    event, event_base, and libevent_fd_t types.

This PR adds a local cppkafka dependency resolver override that:

  • creates the missing CppKafka::cppkafka alias;
  • exposes cppkafka's parent include directories instead of include/cppkafka, avoiding the event.h
    header collision.

It also explicitly enables the Kafka connector and disables cppkafka examples/tests for the dependency
build.

Verified with:

JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 VELOX4J_BUILD_JOBS=16 mvn clean install -DskipTests
-Dgpg.skip -Dspotless.skip=true

lgbo-ustc and others added 29 commits January 28, 2026 09:45
- 在StatefulSerialTask中添加notifyWatermark(long watermark)方法
- 在JNI层添加notifyWatermark和notifyIndexedWatermark两个接口
- 将原有的notifyWatermark(带index)重命名为notifyIndexedWatermark
- 在SerialTask中添加不带index的notifyWatermark公共方法
- 最终调用velox的相应不带index的接口
feat: 添加不带index的notifyWatermark接口
[FLINK]Support processing time window for nexmark q12
Revert "[FLINK]Support processing time window for nexmark q12"
Fix aarch64 build: add missing folly assembly sources
@zhztheplayer

Copy link
Copy Markdown
Contributor

@zhanglistar is this submitted to the wrong repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants