-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Added use orc column names session #24158
base: master
Are you sure you want to change the base?
Added use orc column names session #24158
Conversation
|
Note I am not sure if I need to add testing to this feature extension. Also, I have signed the CLA late not sure if I need to update it further. |
hi @malinjawi , let's move the orc config property to HiveCommonClientConfig.java and session property to HiveCommonSessionProperties.java where the corresponding parquet properties are present. |
…roperty to HiveCommonSessionProperties.java to align with parquet properties.
This reverts commit a6c87ae.
Hi @nmahadevuni , I've moved the ORC config property to |
|
Description
This pull request adds a new session property orc_use_column_names to toggle the usage of ORC column names when accessing ORC files. This session property is analogous to the existing session property for Parquet (parquet_use_column_names). It allows users to enable or disable column name access for ORC files, offering more flexibility in how ORC files are processed within Presto.
Motivation and Context
Currently, there is no session property to control the use of column names when reading ORC files. This change aligns the behavior of ORC with that of Parquet, which already has a session property (parquet_use_column_names) to manage similar functionality. By adding this session property, users can now control whether column names are accessed from ORC files, improving consistency across file formats and enabling finer control over ORC file processing.
issue: #24134
Impact
Test Plan
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.
If release note is NOT required, use: