-
Notifications
You must be signed in to change notification settings - Fork 56
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
2. Add abstractions for MetadataProfile #1440
base: mvp_demo
Are you sure you want to change the base?
2. Add abstractions for MetadataProfile #1440
Conversation
'}'; | ||
} | ||
|
||
} |
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.
EOF missing
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.
Added missing EOF
|
||
private final List<String> mandatoryQueryVariables = new ArrayList<>(Arrays.asList( | ||
AnalyzerConstants.AutotuneObjectConstants.NAME, | ||
AnalyzerConstants.AutotuneObjectConstants.DATASOURCE, |
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 datasource should also be available at the global level. In the query variables, the datasource should not be mandatory; if not specified, it will default to the global level.
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.
Updated the validation of datasource field at the global level
private static final Logger LOGGER = LoggerFactory.getLogger(MetadataProfileValidation.class); | ||
private boolean success; | ||
private String errorMessage; | ||
private final Map<String, MetadataProfile> metadataProfilesMap; |
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.
why hashMap ? can we have String and MetadataProfile variable instead
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.
HashMap will store all the metadata profiles created.. helping in validation with few database calls and also will be used in Create and List REST APIs in the subsequent PRs.
Description
This PR includes abstractions for MetadataProfile:
MetadataProfile
being the base class.MetadataProfileValidation
andMetadataProfileUtil
classes for validating metadata profile and fields.Fixes # (issue)
Type of change
How has this been tested?
Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.
Test Configuration
Checklist 🎯
Additional information
.