-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diff on parquet filter agg #11257
Comments
cc @Yuhta |
Can you upload the |
@zml1206 I cannot repro it using the table scan operator and Hive connector in Velox. It is probably some bug in Gluten integration. The test code: TEST_F(ParquetTableScanTest, aggregatePushdown) {
auto outputType = ROW({"c1", "c2", "c3"}, {BIGINT(), BIGINT(), BIGINT()});
auto plan = PlanBuilder().tableScan(outputType, {"c1 = 1"}, "").singleAggregation({"c2"}, {"sum(c3)"}).planNode();
std::vector<std::shared_ptr<connector::ConnectorSplit>> splits;
for (int i = 0; i < 32; ++i) {
splits.push_back(makeSplit(getExampleFilePath(fmt::format("t1/part-{:05}-6c0bb0b9-d8d5-464c-bb5f-6a4eaeb83228-c000.snappy.parquet", i))));
};
auto result = AssertQueryBuilder(plan).splits(splits).copyResults(pool());
FAIL() << result->toString(0, result->size());
} Output:
|
@Yuhta What is your system info? I can reproduce it on ubuntu22.04.
|
It could be a compiler difference. Are you using gcc? Can you try clang and see if it still repros? |
Yes, clang cannot reproduce, but gcc can. |
Bug description
Write parquet file requires disable gluten.
result
Through testing, found that #11010 caused, it worked after reverted it.
System information
Velox System Info v0.0.2
Commit: 2883361
CMake Version: 3.28.3
System: Linux-5.15.0-113-generic
Arch: x86_64
C++ Compiler: /usr/bin/c++
C++ Compiler Version: 11.4.0
C Compiler: /usr/bin/cc
C Compiler Version: 11.4.0
CMake Prefix Path: /usr/local;/usr;/;/usr/local/lib/python3.10/dist-packages/cmake/data;/usr/local;/usr/X11R6;/usr/pkg;/opt
\nThe results will be copied to your clipboard if xclip is installed.
Relevant logs
No response
The text was updated successfully, but these errors were encountered: