Skip to content

Add register_table procedure usage instructions #25536

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

Closed
wants to merge 1 commit into from

Conversation

XavieLee
Copy link
Member

@XavieLee XavieLee commented Apr 9, 2025

Description

People try to register tables in a different location and face query failures later, add description for this function.

Additional context and related issues

#16105

Release notes

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

Copy link

cla-bot bot commented Apr 9, 2025

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Li Xuan(Xavier.L).
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email [email protected]
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@github-actions github-actions bot added the docs label Apr 9, 2025
@XavieLee XavieLee force-pushed the update/doc/register_table branch from 6e83d62 to 4bfb928 Compare April 9, 2025 11:11
Copy link

cla-bot bot commented Apr 9, 2025

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Li Xuan(Xavier.L).
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email [email protected]
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@XavieLee XavieLee force-pushed the update/doc/register_table branch from 4bfb928 to 5b1d764 Compare April 9, 2025 11:17
Copy link

cla-bot bot commented Apr 9, 2025

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Li Xuan(Xavier.L).
This is most likely caused by a git client misconfiguration; please make sure to:

  1. check if your git client is configured with an email to sign commits git config --list | grep email
  2. If not, set it up using git config --global user.email [email protected]
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@XavieLee XavieLee force-pushed the update/doc/register_table branch from 5b1d764 to 258439f Compare April 9, 2025 11:25
Copy link

cla-bot bot commented Apr 9, 2025

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

@mosabua
Copy link
Member

mosabua commented Apr 12, 2025

Please submit a signed CLA.

@XavieLee
Copy link
Member Author

Please submit a signed CLA.

submitted last week, wating for processing.

@XavieLee XavieLee force-pushed the update/doc/register_table branch from 258439f to 2af99c7 Compare April 14, 2025 02:57
Copy link

cla-bot bot commented Apr 14, 2025

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

@ebyhr
Copy link
Member

ebyhr commented Apr 21, 2025

@cla-bot check

@cla-bot cla-bot bot added the cla-signed label Apr 21, 2025
Copy link

cla-bot bot commented Apr 21, 2025

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

@XavieLee XavieLee force-pushed the update/doc/register_table branch from 2af99c7 to b6abfff Compare May 5, 2025 06:48
@XavieLee XavieLee closed this by deleting the head repository May 13, 2025
@XavieLee
Copy link
Member Author

Hi @findinpath , new PR is #25784 , please help review it. Thanks.

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.

5 participants