Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

RabbitMQ river plugin only supports direct exchange type #696

Closed
charles-dyfis-net opened this issue Feb 17, 2011 · 3 comments
Closed

RabbitMQ river plugin only supports direct exchange type #696

charles-dyfis-net opened this issue Feb 17, 2011 · 3 comments

Comments

@charles-dyfis-net
Copy link

There is a legitimate use case where one may ElasticSearch to be subscribed to a queue behind a fanout exchange (so not only ElasticSearch, but other client(s) as well, receive copies of the same messages). As such, org.elasticsearch.river.rabbitmq.RabbitmqRiver should allow the type passed to channel.exchangeDeclare to be parameterized.
@kimchy
Copy link
Member

kimchy commented Feb 17, 2011

Sounds good, want to work on a pull request for this change? :)

@charles-dyfis-net
Copy link
Author

Corresponds with #709

@kimchy
Copy link
Member

kimchy commented Feb 22, 2011

Allow exchange type and durability, queue durability and queue auto-delete to be specified; closed by d0780f0

mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Merged in dev/fabien/MPC-5179-CSP-through-CF (pull request elastic#696)
8eee398 
MPC-5179: CSP (and additional sec headers) through CloudFront

* naive attempt at using CSP (and additional sec headers) through CF

* remove eclub.house

* add sentry to CSP

* add google to script-src


Approved-by: Alan Nuchnoi
Approved-by: Can Yildiz
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@dliappis
Move away from env-id filters for tsdb charts (elastic#696)
a9267df 
This is effectively the same as elastic#689 for `tsdb*`.

The update queries (for `rally-races` and `rally-results`) were based on the example shown below, using `tsdb-time-series-synthetic-source-nightly`, `tsdb-standard-synthetic-source-nightly` and `tsdb-standard-nightly` as `user-tags.env-id` in combinarion with `tsdb-time-series-synthetic-source`, `tsdb-standard-synthetic-source`, `tsdb-standard` for `user-tags.benchmark-name` respectively.

```
POST rally-races-2022-*/_update_by_query
{
  "query": {
    "bool": {
      "must": [
        {
          "term": {
            "user-tags.env-id": "tsdb-time-series-synthetic-source-nightly"
          }
        },
        {
          "term": {
            "user-tags.setup": "esbench"
          }
        },
        {
          "term": {
            "environment": "nightly"
          }
        }
      ],
      "must_not": [
        {
          "exists": {
            "field": "user-tags.benchmark-name"
          }
        }
      ]
    }
  },
  "script": {
    "source": "ctx._source['user-tags']['benchmark-type'] = 'nightly'; ctx._source['user-tags']['benchmark-name'] = 'tsdb-time-series-synthetic-source'",
    "lang": "painless"
  }}
```
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@charles-dyfis-net @kimchy