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

refactor(ui): Making improvements to UI ingestion forms, adding MySQL, Trino, Presto, MSSQL, MariaDB forms #6607

Merged

Conversation

jjoyce0510
Copy link
Collaborator

@jjoyce0510 jjoyce0510 commented Dec 2, 2022

Summary

In this PR, we add a new form to UI ingestion for

  • MySQL
  • Trino
  • Presto
  • MSSQL
  • MariaDB

We also refactor every other form for copy edits, required field status, and more.

Screenshots

Screen Shot 2022-12-01 at 5 42 13 PM
Screen Shot 2022-12-01 at 5 42 21 PM
Screen Shot 2022-12-01 at 5 42 27 PM
Screen Shot 2022-12-01 at 5 42 33 PM
Screen Shot 2022-12-01 at 5 42 39 PM
Screen Shot 2022-12-01 at 5 42 45 PM
Screen Shot 2022-12-01 at 5 42 51 PM
Screen Shot 2022-12-01 at 5 43 23 PM

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added the product PR or Issue related to the DataHub UI/UX label Dec 2, 2022
@github-actions
Copy link

github-actions bot commented Dec 2, 2022

Unit Test Results (build & test)

622 tests  +1   618 ✔️ +1   15m 39s ⏱️ +2s
158 suites +1       4 💤 ±0 
158 files   +1       0 ±0 

Results for commit cfaabff. ± Comparison against base commit df96e89.

♻️ This comment has been updated with latest results.

rules: null,
required: true,
Copy link
Collaborator

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).

Copy link
Collaborator Author

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,
Copy link
Collaborator

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.

Copy link
Collaborator Author

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,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Same comments as warehouse.

Copy link
Collaborator Author

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

@jjoyce0510 jjoyce0510 changed the title refactor(ui): Making improvements to UI ingestion forms, adding MySQL form refactor(ui): Making improvements to UI ingestion forms, adding MySQL, Trino, Presto, MSSQL, MariaDB forms Dec 3, 2022
Copy link
Collaborator

@chriscollins3456 chriscollins3456 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 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

Comment on lines 295 to 300
getValueFromRecipeOverride: (recipe: any) => {
return get(recipe, isProfilingEnabled);
},
setValueOnRecipeOverride: (recipe: any, value: boolean) => {
return setFieldValueOnRecipe(recipe, value, isProfilingEnabled);
},
Copy link
Collaborator

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.

Copy link
Collaborator Author

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!

@jjoyce0510 jjoyce0510 merged commit 88d2d9b into datahub-project:master Dec 6, 2022
cccs-Dustin pushed a commit to CybercentreCanada/datahub that referenced this pull request Feb 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product PR or Issue related to the DataHub UI/UX
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants