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

wip: fatal stats mismatch #51808

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

madelineliao
Copy link
Contributor

ignore, testing what happens if fatalOnStatsMismatch is set to true

@madelineliao madelineliao requested review from a team and miretskiy and removed request for a team July 22, 2020 23:18
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@madelineliao madelineliao removed the request for review from miretskiy July 22, 2020 23:19
adityamaru and others added 3 commits July 22, 2020 16:20
Previously, the user would have to specify both the source and
detination args when using `userfile upload`.  This change tweaks the
semantics to be as follows:

- Users must specify a source path.

- If the user does not specify a destination URI/path, we use the
  default URI scheme and host, and the basename from the source arg as
the path.

- If the destination is a well-formed userfile URI of the form
  userfile://db.schema.tablename_prefix/path/to/file, then we use that
as the final URI.

- If destination is not a well-formed userfile URI, we use the default
  userfile URI schema and host, and the destination as the path.

File paths are never cleaned during upload or interaction with the
UserFileStorage. Thus, the filename is the exact string represented by
the path of the constructed userfile URI. This is in keeping with the
semantics of s3 and gcsutil. To prevent user surprises we still reject
constructs where the URI post normalization != URI pre normalization.

egs: test/./test.csv or test/../../test.csv

Release note (cli change): Improves the user semantics for `userfile
upload` by supporting different patterns of specifying the source and
destination CLI args. The source arg is required, while the destination
arg is now optional.
My latest change in this area broke Nathan's previous fix.
This commit reverts it.

Release note: None
@madelineliao madelineliao requested a review from a team as a code owner July 22, 2020 23:20
@madelineliao madelineliao removed the request for review from a team July 22, 2020 23:21
@tbg tbg added the X-noremind Bots won't notify about PRs with X-noremind label May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
X-noremind Bots won't notify about PRs with X-noremind
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants