External reviews
External reviews are not included in the AWS star rating for the product.
es as utility to search and index large data
What do you like best about the product?
This utility has a simple Java API and have many documentation
What do you dislike about the product?
When you get an exception it is not very clear what exactly is the error
What problems is the product solving and how is that benefiting you?
Indexing large data
Recommendations to others considering the product:
Try to avoid many indexes if you don't need
- Leave a Comment |
- Mark review as helpful
Powerful search with a simple API
What do you like best about the product?
That would have to be deployment. You have to actually go out of your way to mess up an install.
What do you dislike about the product?
While the API interface is pretty straight forward, having deeply nested hashes can be a little cumbersome.
What problems is the product solving and how is that benefiting you?
I use ElasticSearch for many tasks; geo queries, events, and standard full text searching.
Good open source software
What do you like best about the product?
Very good performance when processing and collecting logs big in size.
Open source with a big community and a lot of plugins available.
Open source with a big community and a lot of plugins available.
What do you dislike about the product?
High memory consumption.
Somewhat hard to setup.
Somewhat hard to setup.
What problems is the product solving and how is that benefiting you?
We needed a way to easily find recurring build system problems that are in our hundreds of logs.
With the implementation of elk(elastisearch, logstash, kibana) we can now easily search all of our logs at once.
With the implementation of elk(elastisearch, logstash, kibana) we can now easily search all of our logs at once.
Elasticsearch, Logstash & Kibana
What do you like best about the product?
Best for large scale application with quantity matters than quality data.
What do you dislike about the product?
Need more examples of successful project implementation and product blogs etc...
What problems is the product solving and how is that benefiting you?
Search against the larger data with lesser time, quick-fast with easy and free open source availability
Recommendations to others considering the product:
Consider quantity matters than quality.
Searching for site content through websites configurations
What do you like best about the product?
10 our of 10 on the basis of searching and researching the site content through parallax and simple site design.
What do you dislike about the product?
The tool is robust but we're still trying to understand the account settings ffeature. Updating the email section can be incredibly difficult to present at a meeting.
What problems is the product solving and how is that benefiting you?
We are using the tool to track the necessary elements of our website back to key business indicators within our instiutional knowledge.
Elastic search is a great tool for searching across a large body of documents.
What do you like best about the product?
ES is easy to get up and get running. Building a multi node farm is also fairly easy. The community around Elastic Search is growing and very helpful if you reach out with questions as your getting setup.
What do you dislike about the product?
There seems to be some inconsistency when it comes to query performance. While initial setup of environments seems easy there are some gotchas that you really need to read through the documentation completely in order to avoid.
What problems is the product solving and how is that benefiting you?
We are utilizing Elastic Search to build our Enterprise Search web application that searches across our internal employees, documents, and social content (blogs, microblogs, videos, etc).
Recommendations to others considering the product:
Pay attention and read through all of the documentation in the starter guide as well as the performance recommendations.
Great tool for search, but only search
What do you like best about the product?
Search is fast and the RESTful API is easy to use, not to mention documentation is great and there is a sizable ElasticSearch community. ElasticSearch should be the go-to tool for anyone looking for a full-text search solution for their application.
What do you dislike about the product?
For anyone that came from a SQL background (like me), getting used to ElasticSearch can take some time. In particular, you need to know what an index, a cluster, nodes and shards are before you can decide the best configuration for your application. ElasticSearch is an open source tool with a paid support function if you'd like, but it's very expensive.
What problems is the product solving and how is that benefiting you?
We need full text search for an integral part of our application, ElasticSearch has been a great tool for that.
Recommendations to others considering the product:
You'll likely spend a while learning ElasticSearch before you become comfortable with it. Depending on the application you use to incorporate ElasticSearch, there may be official libraries that help you get up to speed fast. For example, ElasticSearch has a ruby gem for Ruby on Rails users
Flexible, easy to use and powerful
What do you like best about the product?
Elasticsearch is an amazing search engine. Its architecture is simple and very, believe me, very easy to setup using any configuration management system such as Chef or Puppet.
The "auto discovery" is another strong point. It makes your node cluster much more resilient to failures and make it much more flexible as well. You can easily replace nodes on the fly for maintenance or even for increase / decrease your search infrastructure.
I would also highlight that you don't need any extra software in your ecosystem in order to create a cluster. (in Solr, for example, it's necessary)
The "auto discovery" is another strong point. It makes your node cluster much more resilient to failures and make it much more flexible as well. You can easily replace nodes on the fly for maintenance or even for increase / decrease your search infrastructure.
I would also highlight that you don't need any extra software in your ecosystem in order to create a cluster. (in Solr, for example, it's necessary)
What do you dislike about the product?
It's not directly about the Elasticsearch itself but its miss usage. I've seen people using it directly as a NoSQL databse. The problems in this approach, in my point of view are: Lucene (elastichsearch works upon it) has no transaction concept and if, for some reason (changing mapping config, for example), you need to re-index your data, you will need to copy it and then reindex (such a dirty job).
What problems is the product solving and how is that benefiting you?
We used Elasticsearch to allow the users to search content across many indices, using the multi index search. We had indices for articles, galleries, photos and editorial lists. All of them could be searched at the same time by editors in our Content Management System.
Recommendations to others considering the product:
Combining the easy setup and administration with multi-index search, auto-discovery for the nodes, and the intuitive rest API, you can easily see why Elasticsearch is a good option. But beware, don't add a search engine to your ecosystem just because it's nice, even the best tools will increase your ecosystem's complexity. So it needs to really solve important business problems.
A scalable and easy to use search solution
What do you like best about the product?
It's lightning fast to answer a query, it's distributed by default and has hundreds of plugins and addons to play with, you don't need to be an expert to get it up and running. One of the things I really love is how easy it is to set up replication, it autodiscovers other clusters automatically and mirrors the data.
Also, if used with the "head" plugin, you can monitor the health of your cluster and your indexes in real time and make queries in an easy way through a WYSIWYG interface or a query editor.
Also, if used with the "head" plugin, you can monitor the health of your cluster and your indexes in real time and make queries in an easy way through a WYSIWYG interface or a query editor.
What do you dislike about the product?
The query language is JSON based, which is good but it tends to bee too verbose and queries can get unintuitive, large and ridiculously complex.
What problems is the product solving and how is that benefiting you?
Search within our publications, it's lightning fast and it's the right solution to scale your search service on your website if you have a large traffic. I would recommend to have it since the beginning.
Recommendations to others considering the product:
Don't use it as a main data store as your search index might get corrupted or inconsistent, you'll need a main source of truth and it has to be a persistent database like MySQL, Postgres or MongoDB to rebuild your indexes.
The best search engine
What do you like best about the product?
Easy to setup.
Easy to insert data.
Easy to query data (at the beginning).
Very nice web API.
Easy to insert data.
Easy to query data (at the beginning).
Very nice web API.
What do you dislike about the product?
The documentation is sometimes not very clear to request parameters and perhaps users will re-index their data before obtaining the best search result.
What problems is the product solving and how is that benefiting you?
Problem : get a complete view of all the informations of customers.
The data are scattered across multiple sources (RDBMS, file, ...)
Putting them in a unique system (elasticsearch) and building search-based applications that query this data lake give a large benefit to the employees to rapidly get a complete information about customers.
The data are scattered across multiple sources (RDBMS, file, ...)
Putting them in a unique system (elasticsearch) and building search-based applications that query this data lake give a large benefit to the employees to rapidly get a complete information about customers.
showing 221 - 230