Is there a simple way to address the custom end-point exposed by my plugin
(e.g. /_myplugin/ping) using the java API? The plugin installs correctly
and I can test it using curl, but I would like to be able to do this in
java so I can build some tests.
--
Please update your bookmarks! We have m
I am aware that cross data-center clusters are not recommended, since they
violate one of the core assumptions of ES, namely that all nodes are equal.
But what *specifically* (apart from obvious problems associated with
network failure) can this lead too: is it just high or "irregular" latency
Hallo,
I have 6 types that I would like to keep in the same time-series index. 5
of these types are very similar and so I have defined the common fields in
the _default_ mapping. The 6th is very different and shares very few fields
with the other types: but since the _default_ mapping applies
t.
>
> HTH
>
> --
>
> Itamar Syn-Hershko
> http://code972.com | @synhershko <https://twitter.com/synhershko>
> Freelance Developer & Consultant
> Lucene.NET committer and PMC member
>
> On Tue, Feb 3, 2015 at 11:21 AM, AndrewK
> > wrote:
>
>> I
I've not yet used the aggregations framework, but one question that has
come up recently with contacts and prospective clients is how best to
persist aggregations in ElasticSearch for repeated use.
If I have understood the documentation correctly, the aggregation framework
does a pretty good jo
Hallo Adrien,
Many thanks for the clarification.
But won't the query cache (1.4.0-Beta)
http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-shard-query-cache.html
partially "close the gap" in performance? The cache won't be as lightweight
as the filter cache (a
I have a question regarding filters and queries.
I understand that filters are used in conjunction with routing and aliases,
but it also seems that they can often be used interchangeably with queries.
Is there a technical difference, e.g. with regard to caching mechanisms, to
how they are imple
non-existent distributed architecture of the fetch phase.
> So, a river instance soon becomes a bottleneck or a single point of
> failure, a design which does not fit to the well-designed architecture of
> the rest of the ES system.
>
> Jörg
>
>
> On Tue, Dec 23, 2014
A while ago I used a plugin on a project to control the migration to, and
the maintenance of, a secondary data source/index in ElasticSearch. It
worked really well and avoided lots of messy dependency management in the
host application, as all the logic was "hidden" behind an ES rest end-point.
Thank you for the feedback!
--
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
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
At the core training I attended last year there was a side note on SSD and
write amplification: roughly along the lines of: write amplification can be
a big problem with SSD (as writes can be around 4KB but deletes are often
in blocks of around 512KB, and that the problem gets worse the smaller
11 matches
Mail list logo
