-
Notifications
You must be signed in to change notification settings - Fork 998
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
Change register to apply #4
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.
LGTM.
Need to remember that register
is no longer exist and any documentation should refer to it as apply
* @param otherFeatureGroup | ||
* @return boolean | ||
*/ | ||
public boolean eq(FeatureGroupInfo otherFeatureGroup) { |
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.
Isn't it possible (and perhaps cleaner) to use the built in .equals() method that all Java objects have?
https://docs.oracle.com/javase/7/docs/api/java/lang/Object.html#equals(java.lang.Object)
EntityInfo entity1 = new EntityInfo(entitySpec); | ||
entity1.setCreated(Date.from(Instant.ofEpochSecond(1))); | ||
EntityInfo entity2 = new EntityInfo(entitySpec); | ||
entity1.setCreated(Date.from(Instant.ofEpochSecond(2))); |
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.
Is this line correct? Shouldn't it be entity2.setCreated(Date.from(Instant.ofEpochSecond(2)));
?
&& oldStoreOpts.equals( | ||
newStore == null | ||
? "" | ||
: TypeConversion.convertMapToJsonString(newStore.getOptionsMap())); |
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 really need to have oldStoreOpts here? Can this also be a method on StorageInfo?
Cleaned it up a bit. |
return storageInfo; | ||
} else { | ||
storageInfo = new StorageInfo(spec); | ||
StorageInfo out = storageInfoRepository.saveAndFlush(storageInfo); |
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.
Isn't there a more descriptive variable name that we can use instead of out
?
Builds, tests and runs Docker container for Feast core as well as needed services (Kafka, Redis and PostgreSQL). Uses a self-hosted agent VM (deployed on Azure) to speed up build thanks to Docker layer caching. The Docker Action automatically runs whenever a PR is made.
Integrating comments
# This is the 1st commit message: chore: Bump ws from 7.5.6 to 7.5.10 in /ui (feast-dev#4292) # This is the commit message feast-dev#2: Remove metric checks Signed-off-by: Twinkll Sisodia <[email protected]> # This is the commit message feast-dev#3: Draft different md file # This is the commit message feast-dev#4: Refine opentelemetry.md # This is the commit message feast-dev#5: Refine opentelemetry.md # This is the commit message feast-dev#6: Refine opentelemetry.md # This is the commit message feast-dev#7: Refine opentelemetry.md
# This is the 1st commit message: chore: Bump ws from 7.5.6 to 7.5.10 in /ui (feast-dev#4292) # This is the commit message feast-dev#2: Remove metric checks Signed-off-by: Twinkll Sisodia <[email protected]> # This is the commit message feast-dev#3: Draft different md file # This is the commit message feast-dev#4: Refine opentelemetry.md # This is the commit message feast-dev#5: Refine opentelemetry.md # This is the commit message feast-dev#6: Refine opentelemetry.md # This is the commit message feast-dev#7: Refine opentelemetry.md
Change register API to apply.
If you apply a spec for a resource that doesn't already exist in the system, it will be created. If not, then the resource will be updated to match the new spec provided. Note that only fields without dependencies can be updated; i.e. changes to ids, storage sinks, or value types are not allowed. If you apply a spec that has no changes without throwing an error.
Updated the CLI to reflect these changes as well.