Skip to content

Routing: Publish will not use instance data from mapping file #76

Description

@ramonsmits

A subscriber which subscribes will use this routing data to route to the physical destination of a publisher, but the publisher doesn't use this routing data when publishing. The publisher will use the physical destinations in its subscription storage and not the physical destinations in the routing.

An endpoint instance which is decommissioned or moved to another machine still requires the subscriptions to be modified manually at each publisher it subscribed to.

  • What is there is no route in the mapping file? Should it then still use the subscription data?
  • What is there is a discrepancy between the file and the subscription data?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions