Skip to content

[Improvement] Support event dispatching for catalog connection tests #12566

Closed

Description

@mchades

What would you like to be improved?

CatalogEventDispatcher currently delegates both pre-create and existing-catalog connection tests without emitting pre, success, or failure events. This prevents listeners and auditing integrations from observing these operations.

How should we improve?

Add event dispatching for all three testConnection overloads and cover their success and failure paths with unit tests. Follow the existing catalog event conventions for operation context and exceptions. Reuse the existing audit formatting and redaction behavior.

Activity

  1. ss666 commented on Aug 22, 2026

    @ss666
    Contributor

    Hi @mchades. Could you assign it to me?

  2. zhang-arvin commented on Aug 23, 2026

    @zhang-arvin
    Contributor

    I would like to work on this issue.

  3. added a commit that references this issue on Aug 25, 2026
  4. mchades commented on Aug 26, 2026

    @mchades
    ContributorAuthor

    @ss666 You are welcome to submit a PR directly, and I will review it promptly.

  5. ss666 commented on Aug 26, 2026

    @ss666
    Contributor

    Many thanks for your reply, @mchades. Since I haven’t started working on this yet, and both zhang-arvin and VedantMadane have already contributed great PRs, I think it might be better to wait for the community to review their PRs first, so we can avoid duplicating the work by submitting another PR. I’ve already left some comments on #12571.

  6. added a commit that references this issue on Aug 27, 2026
    50eb408
  7. added a commit that references this issue on Aug 28, 2026
  8. added 3 commits that reference this issue on Sep 7, 2026
  9. singhmrinal02 commented on Sep 16, 2026

    @singhmrinal02

    Hi, I'd like to work on this issue as a first contribution to Apache Gravitino. Could you please assign it to me?

  10. Zhou-Kan commented on Sep 23, 2026

    @Zhou-Kan

    @mchades could I work on this ticket as my first step here? Thanks

  11. added 2 commits that reference this issue on Oct 12, 2026
  12. added 3 commits that reference this issue on Oct 14, 2026
    7cd4a06
    9e5fd72
    e9e6c26
  13. added a commit that references this issue on Oct 22, 2026
  14. codewithsinchana commented on Oct 26, 2026

    @codewithsinchana

    Can you please assign it to me , I would like to work on it

  15. self-assigned this
    on Oct 26, 2026
  16. mchades commented on Oct 26, 2026

    @mchades
    ContributorAuthor

    20. Can you please assign it to me , I would like to work on it

    sorry @codewithsinchana , #12585 almost done

  17. added a commit that references this issue on Oct 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions