Summary

CouchDB keeps a list of purge infos to ensure that purges can be applied on a cluster without purged documents being re-introduced by internal replication.

It would be useful to make this list available for replication clients like PouchDB, who then could apply local purges on their own. I know PouchDB doesn’t implement purge just yet, but it’s something that folks will need befor

Is this a bug or a feature request?

Feature / improvement

What did you expect?

When creating a or updating a routing profile, the NS should validate that it can talk back to the given AS hostname. If not, the create or update should fail with a descriptive error.

What happened?

The create or update succeeds and the communication from the NS to AS fails afterwards.

If I set:

camel.component.twitter-search.xxx

The camel-twitter component should be added to the set of dependencies automatically.

Also because the new property-binding mechanism goes in error otherwise.

We should inspect direct properties and property-files.
We may extend the search also to linked secrets and configmaps.

This is a question for the backend and integration with the MQTT service.

What do you want to do?
I'm looking to develop a AzureFunctions Trigger that listens to messages/topics on the MQTT/AMQP service for a given application; and allows the developer to capture the message(s) received routing/processing message in the cloud

What steps did you take?
I'm able to successfully connect to the

Expected Behavior

I should be able to define functions passing a string to views field

await handle.insert({
      _id: '_design/des',
      view: {
        view1: `
          function (doc) {
            if (doc.ClassName ===

Expected Behavior

Right now, when we edit a document, it brings us back to the document listing page. I sometime need to test some application change by modifying a document re