Sorry, Michael. I am having some issues to share any code right now. It
seems we need to go through an internal verification of anything we want to
share. BTW, the curator script I mentioned is very simple and nothing
special. It doesn't worth to waste any time on waiting for it.
Cheers,
Ali
On
It's a worthy mention. Our existing pruner wouldn't be able to handle Solr
without modification, so we'd either need something native to Solr or
something custom.
Mike
On Mon, Nov 27, 2017 at 3:46 PM, James Sirota wrote:
> One thing to keep in mind, as we will be
One thing to keep in mind, as we will be introducing Solr shortly, is to find
if something similar to curator exists for Solr. But we'll cross that bridge
when we get there
22.11.2017, 22:58, "Ali Nazemian" :
> Sure. I will have a chat internally and come back to you
Sure. I will have a chat internally and come back to you shortly. It was a
quick and dirty work actually just to fix this temporarily. However, it
might be a good starting point.
On Thu, Nov 23, 2017 at 3:31 PM, Michael Miklavcic <
michael.miklav...@gmail.com> wrote:
> Thanks Ali, that's good
Thanks Ali, that's good feedback. Would you be willing to share any of your
Curator calls/config and use cases with the community? I'd love to add it
to a document around ES pruning in the short term, and maybe we could look
at how to build this into indexing at some point.
Cheers,
Mike
On Nov
We tried to use it, but we had the same issue. It was not documented. We
tried to use it, and we had some issues. It also was not exactly what we
wanted, so we decided to create something from scratch by using
Elasticsearch Curator. We wanted to have an ability to manage different
prune mechanism