Skip to content

Migrate CaseInsensitiveMapping tests to BaseCaseInsensitiveMappingTest#8374

Closed
OLMS99 wants to merge 3 commits intotrinodb:masterfrom
OLMS99:trino_issue7864
Closed

Migrate CaseInsensitiveMapping tests to BaseCaseInsensitiveMappingTest#8374
OLMS99 wants to merge 3 commits intotrinodb:masterfrom
OLMS99:trino_issue7864

Conversation

@OLMS99
Copy link
Copy Markdown

@OLMS99 OLMS99 commented Jun 24, 2021

Fixes #7864

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 24, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

Copy link
Copy Markdown
Member

@hashhar hashhar 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 working on it - some comments.

Also can you please change the commit message to Migrate CaseInsensitiveMapping tests to BaseCaseInsensitiveMappingTest.

@hashhar hashhar changed the title attempt to solve issue #7864 Migrate CaseInsensitiveMapping tests to … Migrate CaseInsensitiveMapping tests to BaseCaseInsensitiveMappingTest Jun 24, 2021
@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jun 24, 2021

Working on it and two questions: Is there a way to make the pull request without using my virtual machine's name and use my username instead? And Is there a way to edit the name out of cla-bot's message?

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Jun 24, 2021

Working on it and two questions: Is there a way to make the pull request without using my virtual machine's name and use my username instead? And Is there a way to edit the name out of cla-bot's message?

You can follow the instructions from the bot. Specifically git config --global user.email <your-email> and git config --global user.name <username or your name>.

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 24, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jun 24, 2021

I followed the instructions and the username is still the machine's name, any idea?

Copy link
Copy Markdown
Member

@hashhar hashhar left a comment

Choose a reason for hiding this comment

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

I can see the new commit has the correct identity OLMS99 <olavolucasprogrammer@protonmail.com>.
You might want to squash both commits together.

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jun 24, 2021

And what about the clabot?

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Jun 24, 2021

And what about the clabot?

The CLA bot picks the name from the commit. Once you push all commits with new name it'll reflect there.
Also, have you already sent in the CLA via email?

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 24, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jun 24, 2021

Yes, I've sent 3 days ago

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Jun 24, 2021

@OLMS99 The CLA is a manual process and it'll get approved in some time. Meanwhile can you fix the failing tests and the checkstyle errors? It might be easier to tackle this as 3 separate commits (one for each connector).

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 26, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

4 similar comments
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 26, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 27, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 28, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 29, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jun 29, 2021

@hashhar hey so, any idea what's causing error in pt (default, suite-7-non-generic)? And is there any reference to Trino coding conventions? Does the memsql.license on the remote repository in order?

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Jun 30, 2021

There was an issue with SQL Server docker images being moved. It's fixed now. See #8416

For codestyle follow the instructions at https://github.com/trinodb/trino/blob/master/DEVELOPMENT.md#code-style.

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jun 30, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

1 similar comment
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 1, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jul 3, 2021

@hashhar Working on the TestBigQueryCaseInsensitiveMapping, and there's a different Table and Schema naming convention (TestOracleCaseInsensitiveMapping have this same situation), should I ignore this in favor to BaseCaseInsensitiveMappingTest naming convention, the other way around or find a way to keep both?

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 6, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

3 similar comments
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 7, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 7, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 7, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jul 8, 2021

@hashhar Hey there, my errorprone plugin stopped working, I'm using comunity version of intellj and I can't test the code because of it, any sugestion to solve it?

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 9, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

1 similar comment
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 9, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 23, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

3 similar comments
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 24, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 25, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 25, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@kokosing
Copy link
Copy Markdown
Member

@cla-bot check

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 26, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 26, 2021

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

@kokosing
Copy link
Copy Markdown
Member

@OLMS99 Can you please rebase and squash all commits. This should make it easier to review this PR and also make @cla-bot happy as it is now saying:

2021-07-26T10:53:14.783Z INFO Some commits from the following contributors are not signed with a valid email address: Presto_fdp.

@OLMS99 OLMS99 force-pushed the trino_issue7864 branch from 0a5e641 to e297bd7 Compare July 26, 2021 12:55
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 26, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Jul 26, 2021

Trying to squash

@OLMS99 OLMS99 force-pushed the trino_issue7864 branch from e297bd7 to 850389f Compare July 26, 2021 19:15
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 26, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: Presto_fdp.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@kokosing
Copy link
Copy Markdown
Member

Presto_fdp authored and OLMS99 committed 17 hours ago

There is some issue with your account in GitHub. Somehow github thinks you are not the author the code. Can you please make github to display OLMS99 as an author of the commit?

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Jul 27, 2021

I think rebase/squash don't change author unless --reset-author is also passed. You can see what git sees by running git log --format=fuller and look at Author and Comitter fields.

@OLMS99 OLMS99 force-pushed the trino_issue7864 branch from 850389f to 2bbe015 Compare July 27, 2021 13:43
@cla-bot
Copy link
Copy Markdown

cla-bot bot commented Jul 27, 2021

Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: OLMS99.
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@example.com
  3. Make sure that the git commit email is configured in your GitHub account settings, see https://github.com/settings/emails

@OLMS99 OLMS99 force-pushed the trino_issue7864 branch from 2bbe015 to d3b29d6 Compare July 27, 2021 15:02
@cla-bot cla-bot bot added the cla-signed label Jul 27, 2021
@kokosing
Copy link
Copy Markdown
Member

image
🎉

Copy link
Copy Markdown
Member

@kokosing kokosing left a comment

Choose a reason for hiding this comment

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

Looks good. Few minor comments.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

bump

}

@Test
@Test @Override
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Can you please add a comment why method is overriden?

Please put each annotation in separate line

public void testTableNameClash()
throws Exception
{
String[] nameVariants = {"\"casesensitivename\"", "\"CaseSensitiveName\"", "\"CASESENSITIVENAME\""};
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

why quotes were removed?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

the methods withTable and withSchema at BaseCaseInsensitiveappingTest.java insert the quotes on the names received using the method quoted.

Copy link
Copy Markdown
Member

@hashhar hashhar left a comment

Choose a reason for hiding this comment

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

Looks mostly good % Oracle changes and @kokosing's comments.

I'll verify the MemSQL and BigQuery changes since they don't run on CI.
Thanks for consistently and patiently working on this @OLMS99.

protected SqlExecutor onRemoteDatabase()
{
memSqlServer.execute(sql);
return memSqlServer::execute;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You can inline the function here. So something like return sql -> memSqlServer.execute(sql) and then remove the execute function since it's not used anywhere anymore.

Copy link
Copy Markdown
Author

@OLMS99 OLMS99 Jul 30, 2021

Choose a reason for hiding this comment

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

ok, do the inline at onRemoteDataBase() of TestOracleCaseInsensitiveMapping.java too? @hashhar

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Aug 5, 2021

About the "user trino_test doesn't exist" problem, if I put a withSchema("trino_test"), it's raised an error of ambiguous username, and if I don't, it's raised an error of user "trino_user" doesn't exist. Any idea whats happening? @hashhar

@OLMS99
Copy link
Copy Markdown
Author

OLMS99 commented Aug 21, 2021

@hashhar ?

@hashhar
Copy link
Copy Markdown
Member

hashhar commented Mar 15, 2022

Done in #11250

@hashhar hashhar closed this Mar 15, 2022
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.

Migrate CaseInsensitiveMapping tests to BaseCaseInsensitiveMappingTest

3 participants