Skip to content

PrimaryToSecondaryMapper could be replaced with automatic indexing using the SecondaryToPrimaryMapper #1160

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.

Sign up for GitHub

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

Jump to bottom
Closed
csviri opened this issue Apr 15, 2022 · 0 comments · Fixed by #1161
Closed

PrimaryToSecondaryMapper could be replaced with automatic indexing using the SecondaryToPrimaryMapper #1160

csviri opened this issue Apr 15, 2022 · 0 comments · Fixed by #1161
Assignees
@csviri
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@csviri
Copy link
Collaborator

csviri commented Apr 15, 2022

Have to check more on deep but probably we at the end not need the PrimaryToSecondaryMapper at all, since we can just create a secondary index in the informer based SecondaryToPrimaryMapper and ready the secondary resource(s) from that index for the primary.
@csviri csviri added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 15, 2022
@csviri csviri self-assigned this Apr 15, 2022
@csviri csviri linked a pull request Apr 15, 2022 that will close this issue
feat: remove primary to secondary mapper (handled automatically) #1161
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@csviri csviri

Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Milestone
No milestone
1 participant
@csviri