-
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
feat(ml): bringing ml screens up to date w/ the modern ui layout & improving ml lineage #4651
feat(ml): bringing ml screens up to date w/ the modern ui layout & improving ml lineage #4651
Conversation
throw new AuthorizationException( | ||
"Unauthorized to perform this action. Please contact your DataHub administrator."); | ||
} | ||
DescriptionUtils.validateLabelInput(targetUrn, _entityService); |
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.
Validate label input?
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.
Forget why we called it this...
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, 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); |
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.
Seems like some duplicated code in these methods
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 know its already the case - later we should see if any of it can be refactored out
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.
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 || |
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.
Nice!!
import { useEntityRegistry } from '../../../../useEntityRegistry'; | ||
import { GetMlPrimaryKeyQuery } from '../../../../../graphql/mlPrimaryKey.generated'; | ||
|
||
export const FeatureTableTab = () => { |
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.
Do we need 2 FeatureTableTab components?
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.
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 { |
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.
nice!!!
@@ -401,7 +413,7 @@ fragment nonRecursiveMLPrimaryKey on MLPrimaryKey { | |||
featureNamespace | |||
description | |||
dataType | |||
primaryKeyProperties { | |||
properties { |
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.
yessss
@@ -442,7 +466,7 @@ fragment nonRecursiveMLFeatureTable on MLFeatureTable { | |||
...platformFields | |||
} | |||
description | |||
featureTableProperties { | |||
properties { |
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.
oooooooo
deprecation { | ||
...deprecationFields | ||
} | ||
properties { |
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.
ahhhhh
@@ -174,4 +174,39 @@ entities: | |||
keyAspect: dataPlatformInstanceKey | |||
aspects: | |||
- status | |||
- name: mlModel | |||
category: internal |
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.
qq: are these internal? internal usually used for things like policies and secrets that the outside world shouldn't generally look at
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 ill fix that
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.
Overall this LGTM
feb6e8a
to
9fc5d92
Compare
…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
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