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

Reference copy refresh events #197

Open
cmgrote opened this issue Jan 11, 2020 · 2 comments
Open

Reference copy refresh events #197

cmgrote opened this issue Jan 11, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@cmgrote
Copy link
Member

cmgrote commented Jan 11, 2020

Need to understand what methods need to be implemented and their intended behaviour.

@cmgrote cmgrote added the functionality-call To discuss and agree during weekly functionality call(s) label Jan 11, 2020
@cmgrote cmgrote added this to the 1.3 milestone Jan 11, 2020
@cmgrote cmgrote self-assigned this Jan 11, 2020
@cmgrote cmgrote added the bug Something isn't working label Jan 11, 2020
@cmgrote
Copy link
Member Author

cmgrote commented Jan 14, 2020

@mandy-chessell per discussion on call today, if you can help clarify the expected behaviour I should be implementing primarily to be able to respond to any refresh requests (where IGC is the home repository) that'd be great. For now, I can only see these methods in the base MetadataCollection that make any reference to "refresh":

  • refreshEntityReferenceCopy
  • refreshRelationshipReferenceCopy

... but from today's call my understanding is that these are the methods that cause a request event to be sent for a refresh -- not the methods that respond to such a request. (I'm wondering if the response to such a request may already be handled by the enterprise connector or broader cohort picking up such a request, determining the home repository ID involved, and then simply calling one of the other base methods like getEntityDetail or getRelationship to get the details and then the enterprise connector / cohort bundling the response to that invocation into an event (?) ... rather than a specific method only for responding to such requests in the MetadataCollection...)

@cmgrote cmgrote modified the milestones: 1.3, 1.4 Jan 20, 2020
@cmgrote
Copy link
Member Author

cmgrote commented Jan 21, 2020

Will update, if needed, based on documented interactions from odpi/egeria/issues/2470

@cmgrote cmgrote removed the functionality-call To discuss and agree during weekly functionality call(s) label Jan 21, 2020
@cmgrote cmgrote modified the milestones: 1.4, 1.5 Feb 5, 2020
@cmgrote cmgrote removed this from the 1.6 milestone Apr 2, 2020
@cmgrote cmgrote removed their assignment Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant