Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elasticsearch 1.0.0 released

elasticsearch.org

Post reply on HN
Print view View original

81–90 of 139 posts

Re: Elasticsearch 1.0.0 released

#81

Post by rch »

troels wrote: post #72
rch wrote: post #41

Earlier quoted context omitted.

You might also take a look at the search functionality in Riak. I've run both Solr and ES, the latter at significant scale, and I'm leaning more towards Riak going forward. The difference is mainly convenience, so not a reason to switch off something that's working already.

Hadn't considered Riak, but I can see that it has some full-text search capabilities. Any idea about its features and how it compares in performance, as a raw search index?

I don't know of any publicly available relative raw performance benchmarks, and haven't done any myself. My guess is that the compelling features would be more in the realm of node operations and recovery from node failures.

Edit: Apparently my Riak knowledge is dated now anyway. It looks like I have some research to do myself, but it's pretty exciting stuff.

Re: Elasticsearch 1.0.0 released

#82

Post by ddorian43 »

alecco wrote: post #66

Why is it awesome? Why "it just works"? Is it just a mongodb-kind document store over Hadoop+Lucene? What makes it so special to have hundreds of votes and tweets all around within 2 hours? I don't understand. A DB engine engineer.

distributed/full-text-search(many-many-options)/highlighter/compressed/geo-queries/searching on multiple indexes(databases)|types(tables)/distributed-aggregation/distributed faceting/very-fast-in-memory-suggester/inverse-query(percolator)where you register queries(like rows), and then test documents if they match queries

and many other stuff

Re: Elasticsearch 1.0.0 released

#84

Post by biscarch »

troels wrote: post #72
rch wrote: post #41

Earlier quoted context omitted.

You might also take a look at the search functionality in Riak. I've run both Solr and ES, the latter at significant scale, and I'm leaning more towards Riak going forward. The difference is mainly convenience, so not a reason to switch off something that's working already.

Hadn't considered Riak, but I can see that it has some full-text search capabilities. Any idea about its features and how it compares in performance, as a raw search index?

Riak 2.x uses Solr to index values from K/V with AAE. If you're interested in how using it looks, I wrote a post using geospatial data here[1].

[1]: http://www.christopherbiscardi.com/2014/02/07/geospatial-ind...

Re: Elasticsearch 1.0.0 released

#85

Post by axionike »

ES has performed very well for us as the backbone for the solution we deployed for a large government-sector customer. Had some GC issues initially, and were worried about user concurrency, especially since we were not restricting queries (i.e. users can do full-scale wildcard searches against the entire data set of 1BN+ records). But ES continues to shine.

Congrats to the ElasticSearch team, and all the supporters around it. Once I get back into more of a coding role, I'll definitely be contributing back to the ES project.

Re: Elasticsearch 1.0.0 released

#87

Post by berkay »

nzadrozny wrote: post #48
RyanZAG wrote: post #36

Earlier quoted context omitted.

Complexity. Having two copies of the data means more dev time, more resources required to shift the data around, etc. Having just 1 data store that can also handle all your searching is like the holy grail. As you say, not sure if Solr/ES/Lucene are there yet - but they're definitely very very close. There is no theoretical barrier either - it just comes down to closing bugs, and the ES/Lucene team are very good at c…

Sure, that's a fair point. Data consistency reliability in ES and Lucene will only get better over time. But I personally suspect Lucene won't ever get away from the dreaded "just reindex." And to the larger point, I think recent resurgent interest in data stores and distributed systems have shown pretty clearly that there is no holy grail. No single data store can provide all the semantics necessary for all use case…

I think the distinction made it this comment is valuable, and echoes our experience. ES is not (at least so far) suitable as a general purpose data store, but it is suitable (and very good) for more than search. For some use cases, it's the best available.

Re: Elasticsearch 1.0.0 released

#88

Post by rch »

biscarch wrote: post #84
troels wrote: post #72

Earlier quoted context omitted.

Hadn't considered Riak, but I can see that it has some full-text search capabilities. Any idea about its features and how it compares in performance, as a raw search index?

Riak 2.x uses Solr to index values from K/V with AAE. If you're interested in how using it looks, I wrote a post using geospatial data here[1]. [1]: http://www.christopherbiscardi.com/2014/02/07/geospatial-ind...

If it's just Solr underneath, then why is the pesudo-Solr API implementation not a complete implementation? Something to do with each node being an isolated Solr instance maybe?

Re: Elasticsearch 1.0.0 released

#89

Post by biscarch »

rch wrote: post #88
biscarch wrote: post #84

Earlier quoted context omitted.

Riak 2.x uses Solr to index values from K/V with AAE. If you're interested in how using it looks, I wrote a post using geospatial data here[1]. [1]: http://www.christopherbiscardi.com/2014/02/07/geospatial-ind...

If it's just Solr underneath, then why is the pesudo-Solr API implementation not a complete implementation? Something to do with each node being an isolated Solr instance maybe?

There is backward compatibility with the old Riak Search (which wasn't Solr based) intended to not break old applications, but you can query with any currently implemented Solr client afaik.

Re: Elasticsearch 1.0.0 released

#90

Post by rch »

rch wrote: post #88
biscarch wrote: post #84

Earlier quoted context omitted.

Riak 2.x uses Solr to index values from K/V with AAE. If you're interested in how using it looks, I wrote a post using geospatial data here[1]. [1]: http://www.christopherbiscardi.com/2014/02/07/geospatial-ind...

If it's just Solr underneath, then why is the pesudo-Solr API implementation not a complete implementation? Something to do with each node being an isolated Solr instance maybe?

I see now - interesting. Big shift from 2010 to now. Thanks!

http://www.slideshare.net/rklophaus/riak-search-erlang-facto...

http://basho.com/ricon-west-videos-riak-search-2-0/

Post reply on HN