Skip to content

Conversation

@shangm2
Copy link

@shangm2 shangm2 commented May 20, 2025

  1. This allows us to add custom codec within pom file like below
Screenshot 2025-05-20 at 16 07 31

so that we will be able to generate .thrift idl file by building the presto-thrift-spec module within presto like below
Screenshot 2025-05-20 at 16 16 07

  1. This is for Update plugin to generate idl thrift file automatically presto#25164

@shangm2 shangm2 requested a review from a team as a code owner May 20, 2025 23:08
@shangm2 shangm2 requested a review from jaystarshot May 20, 2025 23:08
Copy link

@NikhilCollooru NikhilCollooru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@arhimondr arhimondr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@shangm2 shangm2 force-pushed the customCodecInPom branch from 79ce209 to fc964ff Compare May 22, 2025 05:06
@shangm2 shangm2 force-pushed the customCodecInPom branch from fc964ff to ce7ba67 Compare May 22, 2025 16:17
@arhimondr arhimondr merged commit 38a9946 into prestodb:master May 22, 2025
2 checks passed
shangm2 added a commit to prestodb/presto that referenced this pull request May 22, 2025
## Description
1. Automatically generate idl file for 3 classes, taskStatus, taskInfo,
and taskUpdateRequest via plugin
2. Requires prestodb/drift#63

## Motivation and Context
<!---Why is this change required? What problem does it solve?-->
<!---If it fixes an open issue, please link to the issue here.-->

## Impact
<!---Describe any public API or user-facing feature change or any
performance impact-->

## Test Plan
1.  Build successfully and the generated idl file looks good.
<img width="1174" alt="Screenshot 2025-05-20 at 16 16 07"
src="https://github.com/user-attachments/assets/3d20b193-9aed-4635-a4f4-f45ccdde8538"
/>

<img width="1134" alt="Screenshot 2025-05-20 at 17 19 08"
src="https://github.com/user-attachments/assets/5fe74591-5f7c-458e-bb25-4616b612ccf0"
/>

## Contributor checklist

- [ ] Please make sure your submission complies with our [contributing
guide](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md),
in particular [code
style](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#code-style)
and [commit
standards](https://github.com/prestodb/presto/blob/master/CONTRIBUTING.md#commit-standards).
- [ ] PR description addresses the issue accurately and concisely. If
the change is non-trivial, a GitHub Issue is referenced.
- [ ] Documented new properties (with its default value), SQL syntax,
functions, or other functionality.
- [ ] If release notes are required, they follow the [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines).
- [ ] Adequate tests were added if applicable.
- [ ] CI passed.

## Release Notes
Please follow [release notes
guidelines](https://github.com/prestodb/presto/wiki/Release-Notes-Guidelines)
and fill in the release notes below.


```
== NO RELEASE NOTE ==
```
@aaneja
Copy link

aaneja commented May 28, 2025

@wanglinsong @shangm2 @arhimondr Just a heads up - we decided to migrate drift to airlift
This was discussed on PrestoDB Slack, and in a TSC call as well

The drift code was migrated via - prestodb/airlift@7fc3927

While we are waiting for the updated airlift to land in Presto via the JDK Upgrade PR, can you make sure that if there are new changes that you're making here, they also are made against the airlift/drift version ?

@ZacBlanco and I would be happy to review any PRs around this

Update : Looks like @ZacBlanco and you'll have already connected. Ignore this comment

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.

4 participants