Camel
  1. Camel
  2. CAMEL-5170

Add support for delete event in camel-zookeeper

    Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.10.0
    • Component/s: camel-zookeeper
    • Labels:
      None
    • Estimated Complexity:
      Novice

      Description

      See nabble
      http://camel.465427.n5.nabble.com/Receiving-NodeDeleted-event-using-Camel-s-ZooKeeper-component-tp5630121p5630121.html

      We should add support so this event is also triggered in the camel-zookeeper component.

      1. CAMEL-5170_v2.patch
        21 kB
        Arnoud Glimmerveen
      2. CAMEL-5170.patch
        20 kB
        Arnoud Glimmerveen

        Activity

        Hide
        Claus Ibsen added a comment -

        Thanks. I have updated the docs

        Show
        Claus Ibsen added a comment - Thanks. I have updated the docs
        Hide
        Arnoud Glimmerveen added a comment -

        In the Options section the new option sendEmptyMessageOnDelete should be documented as follows:

        sendEmptyMessageOnDelete true upon the delete of a znode, should an empty message be send to the consumer

        In the Reading from znode section the following should be added:

        When data is read due to a WatchedEvent received from the ZooKeeper ensemble, the CamelZookeeperEventType header holds ZooKeeper's EventType value from that WatchedEvent. If the data is read initially (not triggered by a WatchedEvent) the CamelZookeeperEventType header will not be set.

        Show
        Arnoud Glimmerveen added a comment - In the Options section the new option sendEmptyMessageOnDelete should be documented as follows: sendEmptyMessageOnDelete true upon the delete of a znode, should an empty message be send to the consumer In the Reading from znode section the following should be added: When data is read due to a WatchedEvent received from the ZooKeeper ensemble, the CamelZookeeperEventType header holds ZooKeeper's EventType value from that WatchedEvent. If the data is read initially (not triggered by a WatchedEvent) the CamelZookeeperEventType header will not be set.
        Hide
        Claus Ibsen added a comment -

        Is there anything to be added/updated on the documentation?
        http://camel.apache.org/zookeeper

        Show
        Claus Ibsen added a comment - Is there anything to be added/updated on the documentation? http://camel.apache.org/zookeeper
        Hide
        Willem Jiang added a comment -

        Applied patch with thanks to Arnoud.

        Show
        Willem Jiang added a comment - Applied patch with thanks to Arnoud.
        Hide
        Arnoud Glimmerveen added a comment -

        Attached a new patch, as the previous patch missed a file.

        Show
        Arnoud Glimmerveen added a comment - Attached a new patch, as the previous patch missed a file.
        Hide
        Arnoud Glimmerveen added a comment -

        This patch adds support for communicating the NodeDeleted event to a Camel route as an empty message (sendEmptyMessageOnDelete flag on the endpoint controls this behaviour, defaulting to true).
        In addition a header is added that communicates ZooKeeper's EventType, adding information to the Message describing what sort of ZooKeeper event triggered the Camel route.

        Show
        Arnoud Glimmerveen added a comment - This patch adds support for communicating the NodeDeleted event to a Camel route as an empty message (sendEmptyMessageOnDelete flag on the endpoint controls this behaviour, defaulting to true). In addition a header is added that communicates ZooKeeper's EventType, adding information to the Message describing what sort of ZooKeeper event triggered the Camel route.

          People

          • Assignee:
            Willem Jiang
            Reporter:
            Claus Ibsen
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development