I'm trying to use an open data portal which is CKAN . However its search platform uses solr , but i want to use elasticsearch to index my data . Is this a way to use elasticsearch with CKAN ?
Thanks.
The short answer is no.
ES is probably more popular now, but I can't think of any really good reason to switch from SOLR. They are both just wrappers around Lucene. Please do say what your reasoning is.
It's certainly doable, since the coupling with SOLR is reasonably loose. There was some work towards this here: https://github.com/ckan/ckan/pull/3118 which no doubt you'd be welcome to help resource.
Related
I'm new to using elastic search, and I'm trying to find a datastore for our application where we can also add a front end for analytics, in this case Kibana. I'm planning to use them as a datastore for dr/cr transactions on our billing system.
Most use case I read is towards data analytics and searching related. I don't see a use case wherein it is used as a regular datastore for an application. So I'm worried I might use it on a wrong use case.
I was hoping if anyone can add their insights on this. Like why or why not use Elastic Search as authoritative/primary datastore for applications.
You should read a official blog of elasticsearch, where they clearly mentioned that databases must be robust and should not stop working unless you tell to do it.
From the robustness section of same blog
A database should be robust, especially if it is your authoritative
system of record. Ideally, a costly query should be possible to
cancel, and you certainly don't want the database to stop working
unless you tell it to.
Unfortunately, Elasticsearch (and the components it's made of) does
not currently handle OutOfMemory-errors very well. We cover this in
more depth in Elasticsearch in Production, OutOfMemory-Caused Crashes.
It is very important to provide Elasticsearch with enough memory and
be careful before running searches with unknown memory requirements on
a production cluster.
In short, you shouldn't use Elasticsearch as a primary data-store where you can't afford to loose the data.
I have an app on cloudant :
How can i plug an elastic search online version, for making full text queries ?
I want to use the river plug in because the new one is too complex .
For now, the only way for me is to do it on localhost, and install elastic 1.6 on localhost, but i'd like to be able to make queries directly online.
Maybe I should use a LUCENT javascript library for couchDb instead ?
Thank you.
What is the problem you're solving here? Cloudant has sophisticated built-in full-text indexing capabilities on top of Lucene:
https://console.bluemix.net/docs/services/Cloudant/api/search.html#search
Whilst it's possible to hook ES onto the Cloudant changes feed, it seems like an overly complex solution that gains little advantage compared with Cloudant's built-in Lucene.
I understand that generally speaking Elastic search is better to use in most cases but i would like to know specifically for Umbraco, whether it is as good to use or not? Or if lucene is better
I've not use elastic search before, but I use Umbraco a lot and I use lucene, mainly via Examine which uses lucene.
Read about Examine here https://our.umbraco.org/documentation/reference/searching/examine/
See an example of some advanced search I set up in Umbraco using Examine here
http://www.codeshare.co.uk/blog/how-to-search-by-document-type-and-property-in-umbraco/
I am trying to make an scalable app using Parse with a search function provided by ElasticSearch.
It seems like I will have to host my own ElasticSearch server which connects to Parse via the ES MongoDB river.
Is this true? Or will Parse handle hosting ES.
I am new to both these solutions.
I recently had the same question. Googling site:parse.com elasticsearch currently only returns 2 results neither of which actually give us an answer. Exploring Parse's discussion forum doesn't provide much help either - the four posts even slightly related to elasticsearch hint at the possibility that Parse wont host ES.
So the answer is... drum roll... maybe :(
Ok, so, I'm developing an app and I'm using Cassandra as the database.
Everything going good so far, but now I need to do a query using the LIKE clause.
I know Cassandra doesn't support that, and that's why after looking for a workaround I was thinking in maintaining this single table that I need to query using the LIKE clause in another database, other than Cassandra - was even considering a relational database, even though there wouldn't exist any relations.
Then I started looking to see if this is really the right approach, and came into stuff like Spark, Sorl and ElasticSearch.
Just to make it clear: I have little to no knowledge about those frameworks. Really. I only have heard about them and that's all.
So, I'm not here to ask you guys 'hey, how to do that using this framework?'. I just want to know, before I dig into any of those: Would any of those satisfy my needs? - Since I have no idea exactly how they work, and what exactly they are for.
If it is the case, them I'll study the framework properly - I just don't want to spend the time to figure out it has nothing to do with my problem.
Thanks!
Both elasticsearch and solr fits your needs. They use lucene library to perform reverse indexing and much more -- Datastax enterprise (commercial distribution of Cassandra) offer this solution integrating solr natively. One more solution (little different but working) is to integrate infinispan which offers both integration with Cassandra repository and reverse indexing ...
HTH,
Carlo