-
Notifications
You must be signed in to change notification settings - Fork 8
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
Feature: Update Metadata service for Java 17 #351
Comments
jacksondelametter
changed the title
BUG: JDK 17 Upgrade Support - Build extensions-metadata-service
BUG: JDK 17 Upgrade Support Series - Build extensions-metadata-service
Sep 19, 2024
jacksondelametter
changed the title
BUG: JDK 17 Upgrade Support Series - Build extensions-metadata-service
FEATURE: JDK 17 Upgrade Support Series - Build extensions-metadata-service
Sep 19, 2024
jacksondelametter
added
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Sep 19, 2024
ewilkins-csi
changed the title
FEATURE: JDK 17 Upgrade Support Series - Build extensions-metadata-service
FEATURE: JDK 17 Upgrade Support Series - Metadata Service
Sep 19, 2024
carter-cundiff
changed the title
FEATURE: JDK 17 Upgrade Support Series - Metadata Service
FEATURE: Update Metadata service for Java 17
Oct 15, 2024
carter-cundiff
changed the title
FEATURE: Update Metadata service for Java 17
Feature: Update Metadata service for Java 17
Oct 15, 2024
carter-cundiff
added a commit
that referenced
this issue
Oct 18, 2024
carter-cundiff
added a commit
that referenced
this issue
Oct 18, 2024
carter-cundiff
added a commit
that referenced
this issue
Oct 18, 2024
OTS with @jacksondelametter |
carter-cundiff
added a commit
that referenced
this issue
Oct 18, 2024
carter-cundiff
added a commit
that referenced
this issue
Oct 18, 2024
#351 Update metadata to be compatible with Java 17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Follow on to #133, where we want to migrate our whole repository to java 17. This issue will focus on migrating the metadata modules to enable provenance within downstream projects.
Definition of Done
foundation-metadata-core
foundation-metadata-producer
extensions-metadata-service
aissemble-metadata
(docker)mvn dependency:analyze
Test Strategy/Script
mvn -v
to verify it's configured properly. The output should be similar to the following (Note: java distributions different thankopenjdk
are okay):OTS Only:
Create a downstream project:
Add the attached SparkPipelineMetadata.json to the
test-351-pipeline-models/src/main/resources/pipelines/
directoryRun
mvn clean install
until all the manual actions are completeRun
mvn clean install -Dmaven.build.cache.skipCache
to get any remaining manual actionsOTS Only:
test-351-deploy/src/main/resources/apps/metadata/values.yaml
:tilt up
Wait for all the resources to be ready on the tilt ui
In a separate terminal, run the following:
spark-pipeline-metadata
resource and wait for it to completemetadata
resource logs the following (Note:VertxException: Thread blocked
are expected):References/Additional Context
The text was updated successfully, but these errors were encountered: