Skip to content

Explicit/Unified filters for All Event Sources #1267

Closed

Description

@csviri

For v3 the PrimaryToSecondaryMapper was removed. However the idea was that user can do filtering events in SecondaryToPrimaryMapper and we would add more explicit event filters and related APIs if requested. But since now a caching mechanism is added to be able to remove PrimaryToSecondaryMapper, filtering events could mean in some cases that the indexing is not happening for the secondary resource. Basically if the resource is not mapped to a primary it is not added to the index (although the goal was just to filter out the event)
That's why there should be no filtering in SecondaryToPrimaryMapper but we should introduce explicit filters for events for provided event source implementations.

Activity

  1. added
    kind/featureCategorizes issue or PR as related to a new feature.
    on Jun 3, 2022
  2. self-assigned this
    on Jun 3, 2022
  3. changed the title [-]Explicit filters for All Event Sources[/-] [+]Explicit filters for Event Sources[/+] on Jun 3, 2022
  4. added this to the 3.1 milestone on Jun 3, 2022
  5. changed the title [-]Explicit filters for Event Sources[/-] [+]Explicit filters for All Event Sources[/+] on Jun 20, 2022
  6. changed the title [-]Explicit filters for All Event Sources[/-] [+]Explicit/Unified filters for All Event Sources[/+] on Jul 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions