Hey guys,
I have a request time, in which the documents the request_time, the ip and
other data which are not relevant right now.
I need to get the visitors over time. Getting the visits over time is easy
with a histogram aggregation, so is getting the unique visitors with a terms
aggregation, b
read it and try to reply, but can't look
into anything or do anything about it.
Regards,
Attila Bukor
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
27;ve observed so far...
Like doing anything else this new, IMO it would be prudent to plan for
incremental steps in the whole process which can be back-tracked if you
run into something unexpected.
Tony
On Thursday, February 20, 2014 4:42:11 AM UTC-8, Attila Bukor wrote:
Hi,
I've read t
reak things and this situation is not really
explained in the docs.
Cheers,
Attila
On 02/20/2014 01:14 PM, Yann Barraud wrote:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-snapshots.html#_restore
:-)
Cordialement,
Yann Barraud
2014-02-20 12:03 GMT+01:00 Attila
much data is being backed up, probably within reason)
If your chosen path requires upgrading the existing cluster to 1.0
anyway, why migrate to the new cluster?
Tony
On Wednesday, February 19, 2014 8:16:02 AM UTC-8, Attila Bukor wrote:
Hi Yann,
Thank you for your response, you sav
balanced). One way to do that
> is setting the following to be the same as the total nodes in the cluster
> gateway.recovery_after_nodes
> HTH,
> Tony
>
> On Wednesday, February 19, 2014 7:01:03 AM UTC-8, Attila Bukor wrote:
>
> Hey everybody,
>
> I have a questio
mercredi 19 février 2014 16:01:03 UTC+1, Attila Bukor a écrit :
Hey everybody,
I have a question regarding the migration of the indices to a
new cluster
seamlessly. Let me first describe the situation:
I have a project which uses Elasticsearch since a few weeks
ago. This i
Hey everybody,
I have a question regarding the migration of the indices to a new cluster
seamlessly. Let me first describe the situation:
I have a project which uses Elasticsearch since a few weeks ago. This is our
first Elasticsearch project, and as we are satisfied with it, we decided to
dedic
