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

feat(ml): bringing ml screens up to date w/ the modern ui layout & improving ml lineage #4651

Merged
merged 13 commits into from
Apr 13, 2022

Conversation

gabe-lyons
Copy link
Contributor

The ml screens still used the old UI. Additionally, they did not support some modern features like glossary terms and domains. There were also some quirks w/ lineage that got ironed out.

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

github-actions bot commented Apr 12, 2022

Unit Test Results (build & test)

  96 files  ±0    96 suites  ±0   18m 5s ⏱️ - 2m 55s
689 tests ±0  630 ✔️ ±0  59 💤 ±0  0 ±0 

Results for commit 9fc5d92. ± Comparison against base commit 08c34bf.

♻️ This comment has been updated with latest results.

@github-actions
Copy link

github-actions bot commented Apr 12, 2022

Unit Test Results (metadata ingestion)

       5 files  ±0         5 suites  ±0   56m 29s ⏱️ - 6m 21s
   425 tests ±0     425 ✔️ ±  0    0 💤 ±  0  0 ±0 
2 050 runs  ±0  1 986 ✔️  - 20  64 💤 +20  0 ±0 

Results for commit 85338f6. ± Comparison against base commit ff685b7.

♻️ This comment has been updated with latest results.

throw new AuthorizationException(
"Unauthorized to perform this action. Please contact your DataHub administrator.");
}
DescriptionUtils.validateLabelInput(targetUrn, _entityService);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Validate label input?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Forget why we called it this...

Copy link
Contributor Author

@gabe-lyons gabe-lyons Apr 13, 2022

Choose a reason for hiding this comment

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

yeah, this is just an existing method. I think validateDescriptionInput would be a better name- I can refactor as a followup.

throw new AuthorizationException(
"Unauthorized to perform this action. Please contact your DataHub administrator.");
}
DescriptionUtils.validateLabelInput(targetUrn, _entityService);
Copy link
Collaborator

Choose a reason for hiding this comment

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

Seems like some duplicated code in these methods

Copy link
Collaborator

Choose a reason for hiding this comment

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

I know its already the case - later we should see if any of it can be refactored out

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes... the pattern to duplicate code already exists in this resolver. we can look into removing it but its tricky bc each needs to interact w/ its own aspect

@@ -60,6 +60,11 @@ export const EntityPage = ({ entityType }: Props) => {
entityType === EntityType.Chart ||
entityType === EntityType.DataFlow ||
entityType === EntityType.DataJob ||
entityType === EntityType.Mlmodel ||
Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice!!

import { useEntityRegistry } from '../../../../useEntityRegistry';
import { GetMlPrimaryKeyQuery } from '../../../../../graphql/mlPrimaryKey.generated';

export const FeatureTableTab = () => {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we need 2 FeatureTableTab components?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Its a bit simpler this way so we can keep things typesafe

@@ -361,7 +361,7 @@ fragment nonRecursiveMLFeature on MLFeature {
featureNamespace
description
dataType
featureProperties {
properties {
Copy link
Collaborator

Choose a reason for hiding this comment

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

nice!!!

@@ -401,7 +413,7 @@ fragment nonRecursiveMLPrimaryKey on MLPrimaryKey {
featureNamespace
description
dataType
primaryKeyProperties {
properties {
Copy link
Collaborator

Choose a reason for hiding this comment

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

yessss

@@ -442,7 +466,7 @@ fragment nonRecursiveMLFeatureTable on MLFeatureTable {
...platformFields
}
description
featureTableProperties {
properties {
Copy link
Collaborator

Choose a reason for hiding this comment

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

oooooooo

deprecation {
...deprecationFields
}
properties {
Copy link
Collaborator

Choose a reason for hiding this comment

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

ahhhhh

@@ -174,4 +174,39 @@ entities:
keyAspect: dataPlatformInstanceKey
aspects:
- status
- name: mlModel
category: internal
Copy link
Collaborator

Choose a reason for hiding this comment

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

qq: are these internal? internal usually used for things like policies and secrets that the outside world shouldn't generally look at

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh ill fix that

Copy link
Collaborator

@jjoyce0510 jjoyce0510 left a comment

Choose a reason for hiding this comment

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

Overall this LGTM

@gabe-lyons gabe-lyons force-pushed the gabe--updatingMlModels branch from feb6e8a to 9fc5d92 Compare April 13, 2022 04:57
@gabe-lyons gabe-lyons merged commit c92990d into datahub-project:master Apr 13, 2022
maggiehays pushed a commit to maggiehays/datahub that referenced this pull request Aug 1, 2022
…proving ml lineage (datahub-project#4651)

* backend ml changes

* updating ml model UI

* more work on the UI

* ml primary key joining the party

* more progress on UI

* making progress on lineage

* finalizing UI experience

* remove irrelevant test

* fixing lint

* fixups

* add tests and fix what the issues they discovered

* internal > core
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