-
Notifications
You must be signed in to change notification settings - Fork 3.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
Add test ORC multi column data generator. #15434
Conversation
368b1ed
to
3798070
Compare
f7e2420
to
b7b3092
Compare
b7b3092
to
e1f348f
Compare
Could you rebase on upstream to resolve conflicts? |
e1f348f
to
b2a97f8
Compare
done |
afcc50b
to
33dbf74
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the end result very good.
Please consider restructuring the commits.
I think that we can achieve the logical succession of the changes in fewer commits.
The refactoring related to working RecordWriterBuilder
can be done as a preparatory commit and (if i'm not mistaken) the changes related to multi-columns orc writer support can be done in one commit.
b3fd5fa
to
4cad5ed
Compare
LGTM % comments |
4cad5ed
to
801d376
Compare
i've fix file reading to bytest and tried locally this one^^^ - build passed with no errors. |
aff2479
to
eff1424
Compare
@ebyhr CPTAL? |
eff1424
to
a3eeeed
Compare
@mx123 Could you avoid rebasing when there's no conflict? It makes it hard to see the diff since the last review in GitHub UI. |
a3eeeed
to
c4e52f0
Compare
ok. sorry. will do. |
c4e52f0
to
ae28767
Compare
Can we test both |
ae28767
to
0173236
Compare
|
0173236
to
4ff0fd6
Compare
95a3089
to
c219687
Compare
Prior approach was to use pre-generated ORC file for multi column HIVE data. This approach is replaced to runtime generated data OCR file for testing.
c219687
to
6b33037
Compare
Description
Add test ORC multi column data generator.
Fixes: #15420