-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Add function $redacted$()
#24790
Comments
Saving users from themselves - I like that :) |
Can we instead use a function
|
You can even do:
which will use 124 == |
I have a few concerns:
Even if we provide a clear message (e.g., "This is a redacted property"), why can't we use a function with a concise, self-explanatory name instead? |
this is an error-code and it's optional, fail is hidden so it's not listed but it's used across a codebase so it won't be removed in the future. wdyt @martint ? |
In #24563, we'd like to introduce the redaction of sensitive information in statements like
CREATE CATALOG
in query events and endpoints that expose query text (e.g.,v1/query
).There is an idea to mask secrets by replacing them with a function call that always fails. For example, the redacted text of:
Would look like this:
This approach prevents users from copying the redacted query text and unintentionally creating a catalog with the password
***
.To summarize: we propose introducing the
$redacted$()
function, which always fails. I’m extracting this proposal into a separate GitHub issue because I believe it requires a syntax review.cc: @dain @hashhar
The text was updated successfully, but these errors were encountered: