Greetings,
i would appreciate if you could provide us with feedback regarding the way you
have adopted elasticsearch, and how you have used it with MARC records. I have
already read all previous answers, if someone has something in more detail
(technically) it would be very helpful. I have
Sent: Thursday, March 14, 2013 2:47 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] ElasticSearch
Anyone using it?
Thanks,
Cary
--
Cary Gordon
The Cherry Hill Company
http://chillco.com
Anyone using it?
Thanks,
Cary
--
Cary Gordon
The Cherry Hill Company
http://chillco.com
That's something pretty pricy.
Kun
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of Cary
Gordon
Sent: Thursday, March 14, 2013 2:47 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: [CODE4LIB] ElasticSearch
Anyone using it?
Thanks,
Cary
--
Cary
In context of logstash, more or less from source but not in production.
That's mostly a +1 to the idea though. Interested to hear thoughts.
--
Al Matthews
Software Developer, Digital Services Unit
Atlanta University Center, Robert W. Woodruff Library
email: amatth...@auctr.edu; office: 1 404
On Mar 14, 2013, at 2:46 PM, Cary Gordon listu...@chillco.com wrote:
Anyone using it?
We do, what are you looking to know?
-Ross.
Thanks,
Cary
--
Cary Gordon
The Cherry Hill Company
http://chillco.com
Likewise, I've been using it since mid-2010 (0.6.0). What do you want to know
about it?
MJ
I am trying to decide whether we should evaluate it and possibly do a
Drupal integration.
I know that this is not a trivial question, but, being lazy, I would like
to know in what ways it provides services that I can't get from Solr. I
have looked at the comparo cheatsheet —
On Thu, Mar 14, 2013 at 06:49:28PM +, Lin, Kun wrote:
That's something pretty pricy.
Are you joking? It's free and open-source software:
https://github.com/elasticsearch/elasticsearch
Some of my colleagues at Bielefeld University Library's LibTec department are
using it with LibreCat
So the main advantages to ES over Solr that I can think of offhand are the fact
that you can store and search on complex JSON documents (that is, documents
with nested objects, etc.) making it an effective standalone document database
and the fact that it will automatically replicate and shard
I would add that it generally does better for realtime applications. If
your index is updated often, ES *might* perform much better than Solr.
http://blog.socialcast.com/realtime-search-solr-vs-elasticsearch/
On Thu, Mar 14, 2013 at 12:18 PM, Ross Singer rossfsin...@gmail.com wrote:
So the
This is good info.
I guess I will build out a test Drupal integration, unless I can talk
someone else into doing it.
Cary
On Thu, Mar 14, 2013 at 12:19 PM, Tom Johnson
johnson.tom+code4...@gmail.com wrote:
I would add that it generally does better for realtime applications. If
your index is
@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] ElasticSearch
On Thu, Mar 14, 2013 at 06:49:28PM +, Lin, Kun wrote:
That's something pretty pricy.
Are you joking? It's free and open-source software:
https://github.com/elasticsearch/elasticsearch
Some of my colleagues at Bielefeld University
To these responses, I would also add: extremely easy to install and configure
-- that is, NO configuration is required to get it running out-of-the-box
(including schema definitions, servlet containers, etc.) This alone was what
drew me to ES in lieu of Solr way back, though I don't know if it
We use ES for indexing and searchability of historical textcorpora
(Structure presented in TEI XML) in our dedicated research data
repository in the LAUDATIO project (http://www.laudatio-repository.org).
In my opinion the main advantages from ES are: Schema-free, Real time
and Data in JSON and the
of amazon
cloud). I think it is the same or similar name.
Kun
-Original Message-
From: Code for Libraries [mailto:CODE4LIB@LISTSERV.ND.EDU] On Behalf Of
Christian Pietsch
Sent: Thursday, March 14, 2013 3:13 PM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] ElasticSearch
16 matches
Mail list logo
