-
Notifications
You must be signed in to change notification settings - Fork 3k
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
refactor(ui): Making improvements to UI ingestion forms, adding MySQL, Trino, Presto, MSSQL, MariaDB forms #6607
refactor(ui): Making improvements to UI ingestion forms, adding MySQL, Trino, Presto, MSSQL, MariaDB forms #6607
Conversation
rules: null, | ||
required: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ingestion may work even without specifying a warehouse if user has a DEFAULT_WAREHOUSE
set (see https://docs.snowflake.com/en/sql-reference/sql/alter-user.html) and if the configured role has USAGE
access on that warehouse. However I agree that specifying warehouse explicitly is recommended for various reasons(troubleshooting, clarity).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I'd rather keep as required for now, even though technically you can get aware with it..
rules: null, | ||
required: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Snowflake ingestion supports multiple authentication types including default (username/password) auth, key-pair, oauth. This is driven by authentication_type
config in recipe. The "required" nature of username is therefore conditional and depends on authentication_type
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently we only support username / password thru the UI, so until we support Key-Pair as well, I think we should leave as required
section: 'Views', | ||
setValueOnRecipeOverride: (recipe: any, values: string[]) => | ||
setListValuesOnRecipe(recipe, values, viewDenyFieldPath), | ||
required: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comments as warehouse.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay - will leave for now to reduce the likelihood of ingestion failure
datahub-web-react/src/app/ingest/source/builder/RecipeForm/common.tsx
Outdated
Show resolved
Hide resolved
datahub-web-react/src/app/ingest/source/builder/RecipeForm/common.tsx
Outdated
Show resolved
Hide resolved
datahub-web-react/src/app/ingest/source/builder/RecipeForm/hive.ts
Outdated
Show resolved
Hide resolved
datahub-web-react/src/app/ingest/source/builder/RecipeForm/common.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me! I tried checking as close as possible but obviously with these forms there's a whole lot that goes into it.
I have some comments but they're minor and I'm approving now
datahub-web-react/src/app/ingest/source/builder/RecipeForm/RecipeForm.tsx
Outdated
Show resolved
Hide resolved
getValueFromRecipeOverride: (recipe: any) => { | ||
return get(recipe, isProfilingEnabled); | ||
}, | ||
setValueOnRecipeOverride: (recipe: any, value: boolean) => { | ||
return setFieldValueOnRecipe(recipe, value, isProfilingEnabled); | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think setting these override methods are necessary since isProfilingEnabled
is set as the fieldPath
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh nice catch yes this is simple!
datahub-web-react/src/app/ingest/source/builder/RecipeForm/common.tsx
Outdated
Show resolved
Hide resolved
…, Trino, Presto, MSSQL, MariaDB forms (datahub-project#6607)
Summary
In this PR, we add a new form to UI ingestion for
We also refactor every other form for copy edits, required field status, and more.
Screenshots
Checklist