Skip to content
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

[trino-ignite] Ensure primary_key columns exist while creating table #16266

Merged
merged 2 commits into from
Mar 20, 2023
Merged

[trino-ignite] Ensure primary_key columns exist while creating table #16266

merged 2 commits into from
Mar 20, 2023

Conversation

sahoss
Copy link
Contributor

@sahoss sahoss commented Feb 25, 2023

Description

Adds a check to validate that the column names defined in primary_key table property exists as column names in the table definition.

Fixes #16215

Release notes

(x) This is not user-visible or docs only and no release notes are required.

@cla-bot
Copy link

cla-bot bot commented Feb 25, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@sahoss sahoss marked this pull request as ready for review February 25, 2023 04:59
@cla-bot
Copy link

cla-bot bot commented Feb 25, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@sahoss
Copy link
Contributor Author

sahoss commented Feb 25, 2023

@chenjian2664 @ebyhr please take a look :)

@cla-bot
Copy link

cla-bot bot commented Feb 25, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

1 similar comment
@cla-bot
Copy link

cla-bot bot commented Feb 25, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@cla-bot
Copy link

cla-bot bot commented Feb 25, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@sahoss sahoss requested a review from chenjian2664 February 25, 2023 12:20
Copy link
Member

@ebyhr ebyhr left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution. Please squash commits into one and follow this guideline for commit messages. https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#format-git-commit-messages

By the way, have you already submit CLA?

@sahoss
Copy link
Contributor Author

sahoss commented Feb 26, 2023

Thanks for your contribution. Please squash commits into one and follow this guideline for commit messages. https://github.com/trinodb/trino/blob/master/.github/DEVELOPMENT.md#format-git-commit-messages

:)

Will do this

By the way, have you already submit CLA?

Yes. i have submit it via email, but yet to be accepted.

@ebyhr
Copy link
Member

ebyhr commented Feb 26, 2023

@sahoss Please feel free to ping me after addressing comments.

@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@trinodb trinodb deleted a comment from cla-bot bot Feb 27, 2023
@cla-bot
Copy link

cla-bot bot commented Feb 27, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@sahoss
Copy link
Contributor Author

sahoss commented Feb 27, 2023

@sahoss Please feel free to ping me after addressing comments.

@ebyhr Done. please take a look.
328e5a6 deletes the unused branch.

#16266 (comment) and #16266 (comment) is addressed as well.

@cla-bot
Copy link

cla-bot bot commented Feb 28, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

3 similar comments
@cla-bot
Copy link

cla-bot bot commented Feb 28, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@cla-bot
Copy link

cla-bot bot commented Mar 1, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@cla-bot
Copy link

cla-bot bot commented Mar 1, 2023

Thank you for your pull request and welcome to the Trino community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. Continue to work with us on the review and improvements in this PR, and submit the signed CLA to [email protected]. Photos, scans, or digitally-signed PDF files are all suitable. Processing may take a few days. The CLA needs to be on file before we merge your changes. For more information, see https://github.com/trinodb/cla

@sahoss
Copy link
Contributor Author

sahoss commented Mar 3, 2023

@ebyhr wondering if you could take a look at this pr (#16266 (comment) has been addressed)

also, verification/cla-signed bot is failing, but i have mailed my CLA. anything/anyone specifically i should do or reachout to? thanks.

@ebyhr
Copy link
Member

ebyhr commented Mar 7, 2023

@cla-bot check

@cla-bot cla-bot bot added the cla-signed label Mar 7, 2023
@cla-bot
Copy link

cla-bot bot commented Mar 7, 2023

The cla-bot has been summoned, and re-checked this pull request!

Copy link
Member

@ebyhr ebyhr left a comment

Choose a reason for hiding this comment

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

Remove unreachable branch and for loop

I would change to "Remove unreachable code from IgniteClient"

@sahoss
Copy link
Contributor Author

sahoss commented Mar 11, 2023

@ebyhr updated the commit message and updated the test_name variable. ptal!

sahoss added 2 commits March 15, 2023 11:25
Exception was unreachable as the same check is also present
from create table task
Adds a check for create table in IgniteClient. The check ensures
that the column names mentioned in the table property 'primary_key'
exists in the column defined in the create table statement.
@ebyhr ebyhr merged commit 8df3c9c into trinodb:master Mar 20, 2023
@github-actions github-actions bot added this to the 411 milestone Mar 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Make sure Ignite primary_key column exists while creating table
3 participants