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

Feature/untangle dataset registry and meta storage #3502

Merged
merged 5 commits into from
Jul 25, 2024

Conversation

thoniTUB
Copy link
Collaborator

@thoniTUB thoniTUB commented Jul 24, 2024

Before DatasetRegistry and MetaStorage each referenced each other which complicated instantiation and initialization.

Now:

  • The DatasetRegistry is availiable to the MetaStorage (Executions + Forms) through the provided object mapper
  • The MetaStorage is availiable to the DatasetRegistry during Namespace creation as a method parameter
  • Every WorkerStorage and NamespaceStorage has its own ObjectMapper with its own InjectedValues (IdResolveContext)

@awildturtok you can review it but I'll want to rebase this PR onto develop so that it is more independent from the other caching related PRs

Comment on lines -37 to -38
@Getter
protected final DatasetRegistry<? extends Namespace> datasetRegistry;
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@awildturtok this went away

Comment on lines -49 to -53
@Getter
@Setter
private MetaStorage metaStorage;

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@awildturtok and this went away

@thoniTUB thoniTUB force-pushed the feature/untangle-datasetRegistry-and-MetaStorage branch from aa0004e to ca8b0eb Compare July 25, 2024 06:17
@thoniTUB thoniTUB changed the base branch from feature/integrate-object-initialization-upon-parsing to develop July 25, 2024 06:17
@@ -42,7 +38,7 @@ public T deserialize(JsonParser parser, DeserializationContext ctxt) throws IOEx
ID id = ctxt.readValue(parser, idClass);

try {
final CentralRegistry centralRegistry = CentralRegistry.get(ctxt);
final CentralRegistry centralRegistry = MetaStorage.get(ctxt).getCentralRegistry();
Copy link
Collaborator

Choose a reason for hiding this comment

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

würde es sich anbieten die CentralRegistry umzubennen, wenn sie hier nur für die MetaIds verantwortlich ist?

Copy link
Collaborator

Choose a reason for hiding this comment

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

also => Registry

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Ich würde davon absehen, da die CentralRegistry mit dem Caching verschwindet

@thoniTUB thoniTUB enabled auto-merge July 25, 2024 08:11
@thoniTUB thoniTUB merged commit 1c672bb into develop Jul 25, 2024
6 checks passed
@thoniTUB thoniTUB deleted the feature/untangle-datasetRegistry-and-MetaStorage branch October 2, 2024 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants