Skip to content

Spelling#17393

Merged
rschlussel merged 1 commit intoprestodb:masterfrom
jsoref:spelling
Mar 7, 2022
Merged

Spelling#17393
rschlussel merged 1 commit intoprestodb:masterfrom
jsoref:spelling

Conversation

@jsoref
Copy link
Copy Markdown
Contributor

@jsoref jsoref commented Mar 3, 2022

Test plan

This PR corrects misspellings identified by the check-spelling action.

The misspellings have been reported at jsoref@f42e814#commitcomment-67876501

The action reports that the changes in this PR would make it happy: jsoref@4a11b58

  • A bunch of things failed, but it looked like GitHub CI was broken overnight. I don't expect this to be merged as-is.

Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Please make sure your submission complies with our Development, Formatting, and Commit Message guidelines. Don't forget to follow our attribution guidelines for any code copied from other projects.

Fill in the release notes towards the bottom of the PR description.
See Release Notes Guidelines for details.

== RELEASE NOTES ==

MongoDB Connector Changes
* Fix the spelling of the write concern option ``JOURNAL_SAFE`` for the property ``mongodb.write-concern``.

Copy link
Copy Markdown
Contributor Author

@jsoref jsoref left a comment

Choose a reason for hiding this comment

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

Most corrections were automatically suggested by Google Sheets.
The doubling fixes were by me in a slightly more targeted manner, but I did try to skip the @param cases. I'll drop the ones I've flagged here.

I'm happy to drop anything as directed/split/etc.


Each pull request submission will be reviewed by a contributor or [committer](https://github.com/prestodb/presto/wiki/committers)
in the project. Only committers may merge a pull request. Large contributions should have an associated Github issue.
in the project. Only committers may merge a pull request. Large contributions should have an associated GitHub issue.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is a brand. (It's flagged by recently added tooling.)

Comment on lines -98 to +102
The Presto Web UI is composed of several React components and is written in JSX and ES6. This source code is compiled and packaged into browser-compatible Javascript, which is then checked in to the Presto source code (in the `dist` folder). You must have [Node.js](https://nodejs.org/en/download/) and [Yarn](https://yarnpkg.com/en/) installed to execute these commands. To update this folder after making changes, simply run:
The Presto Web UI is composed of several React components and is written in JSX and ES6. This source code is compiled and packaged into browser-compatible JavaScript, which is then checked in to the Presto source code (in the `dist` folder). You must have [Node.js](https://nodejs.org/en/download/) and [Yarn](https://yarnpkg.com/en/) installed to execute these commands. To update this folder after making changes, simply run:

yarn --cwd presto-main/src/main/resources/webapp/src install

If no Javascript dependencies have changed (i.e., no changes to `package.json`), it is faster to run:
If no JavaScript dependencies have changed (i.e., no changes to `package.json`), it is faster to run:
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Also a brand.

fi

# For Migwn, ensure paths are in UNIX format before anything is touched
# For Mingw, ensure paths are in UNIX format before anything is touched
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Also a brand (but, not flagged by the same tooling, this was just caught by the fact that it isn't in the dictionary).

* Presto module to do all kinds of run Guice injection stuff!
* <p>
* WARNING: Contains black magick
* WARNING: Contains black magic
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Some projects are intentionally cute, this one doesn't appear to be particularly.

.add("preGroupedSymbols", preGroupedSymbols)
.add("masks", masks)
.add("groudId", groupId)
.add("groupId", groupId)
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

?

* </ol>
* <p> This prioritizes query performance over total cluster storage capacity, and therefore may
* produce a cluster state that is imbalanced in terms of disk utilization.
* produce a cluster state that is uneven in terms of disk utilization.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Notable change

// Until we migrate all connectors to parametrized varchar we check two options
assertTrue(actual.equals(expectedParametrizedVarchar) || actual.equals(expectedUnparametrizedVarchar),
format("%s does not matche neither of %s and %s", actual, expectedParametrizedVarchar, expectedUnparametrizedVarchar));
format("%s matches neither %s nor %s", actual, expectedParametrizedVarchar, expectedUnparametrizedVarchar));
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Notable

@jsoref jsoref force-pushed the spelling branch 3 times, most recently from b8ddb61 to 6ff65c7 Compare March 3, 2022 16:46
Copy link
Copy Markdown
Contributor

@rschlussel rschlussel left a comment

Choose a reason for hiding this comment

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

This is awesome. Can you also update the commit messages to say" Fix Spelling: ..." instead of just "Spelling ..." to match our commit guidelines https://github.com/prestodb/presto/wiki/Review-and-Commit-guidelines#commit-formatting-and-pull-requests.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

curious about the changes to add "example". Is that to avoid accidentally creating a real uri?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, if you don't own a domain you shouldn't use it. example is allowed per DNS RFCs.

doesnotmatter.com is a real domain backed by real web servers and people shouldn't compose URLs that might go to things they don't control.

There are a number of examples of various major vendors (and individuals) messing up the internet in scary ways because they included strings and didn't realize that users might actually use the things. (A number of the examples are from Microsoft, but plenty aren't.)

}

If you want to allow users to use the extractly same name as their Kerberos principal
If you want to allow users to use exactly same name as their Kerberos principal
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

should be "exactly the same name" (add the)

public static final ConnectorTableMetadata METADATA = tableMetadataBuilder(NAME)
.column("procedure_cat", createUnboundedVarcharType())
.column("procedure_schem", createUnboundedVarcharType())
.column("procedure_schema", createUnboundedVarcharType())
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can you pull this change out? it needs a release note since it's a column name in a table we expose. I also want to double check whether there's anything else we need to do to make this change.

Copy link
Copy Markdown
Contributor

@rschlussel rschlussel left a comment

Choose a reason for hiding this comment

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

One last thing

Comment on lines -367 to +372
public Iterable<RowExpression> nonInferrableConjuncts(RowExpression expression)
public Iterable<RowExpression> nonInferableConjuncts(RowExpression expression)
{
return filter(extractConjuncts(expression), not(isInferenceCandidate()));
}

public static Iterable<RowExpression> nonInferrableConjuncts(Metadata metadata, RowExpression expression)
public static Iterable<RowExpression> nonInferableConjuncts(Metadata metadata, RowExpression expression)
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

thanks. this is not an api

Includes some minor grammatical fixes as well.

Notable change:

`JOURNAL_SAFEY` -> `JOURNAL_SAFE`

Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
@rschlussel rschlussel merged commit 5c6efc7 into prestodb:master Mar 7, 2022
@jsoref jsoref deleted the spelling branch March 7, 2022 19:12
@varungajjala varungajjala mentioned this pull request Mar 22, 2022
9 tasks
@asjadsyed asjadsyed mentioned this pull request Mar 23, 2022
9 tasks
@asjadsyed asjadsyed mentioned this pull request Apr 1, 2022
8 tasks
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.

2 participants