18 Matching Annotations
  1. May 2021
    1. The second optimization we used was to replicate large portions of our Datastore data into ElasticSearch. ElasticSearch is a fundamentally different storage technology to Datastore, and is not a managed service, so it was a big leap for us.
  2. Oct 2019
  3. Sep 2019
    1. Deep Learning for Search - teaches you how to leverage neural networks, NLP, and deep learning techniques to improve search performance. (2019) Relevant Search: with applications for Solr and Elasticsearch - demystifies relevance work. Using Elasticsearch, it teaches you how to return engaging search results to your users, helping you understand and leverage the internals of Lucene-based search engines. (2016)
    2. Elasticsearch with Machine Learning (English translation) by Kunihiko Kido Recommender System with Mahout and Elasticsearch
  4. Mar 2019
  5. Jan 2019
    1. When a document is deleted or updated (= delete + add), Apache Lucene simply marks a bit in a per-segment bitset to record that the document is deleted. All subsequent searches simply skip any deleted documents.

      Meaning any deleted documents do not show up in search. Assuming that change has been propagated to all shards.

  6. Oct 2018
  7. Jul 2018
    1. Will ich ein Feld abfragen, das sich nicht auf der obersten Ebene der geschachtelten JSON-Daten befindet, muss ich es über den Pfad identifizieren, das heißt ich gebe die Felder an, in denen das Feld eingebettet ist. Beispielsweise professionOrOccupation.label in folgenden Daten

      Wodurch ist diese hierarchische Feldsuche möglich? bzw. Wie habt Ihr die hierarchischen JSON-Daten indexiert? So weit ich weiß, sind in den meisten Fällen die Daten in einem Lucene basierten Index flach, das scheint bei Euch nicht der Fall zu sein. Mich würden die Details der Indexierung interessieren, die die hierarchische Feldsuche ermöglichen. Dies ist möglicherweise auch für viele Anwendungsfälle in den DH interessant, wo hierarchische TEI-Strukturen vorhanden sind.

  8. Jan 2018
  9. Nov 2017
    1. Running these queries on a field with many unique terms can be resource intensive indeed. Avoid using a pattern that starts with a wildcard (for example, *foo or, as a regexp, .*foo).
  10. Apr 2017
    1. Sense is a Kibana app that provides an interactive console for submitting requests to Elasticsearch directly from your browser.

      From Kibana 4, Sense is renamed Console and integrated in Kibana core.

      source: https://stackoverflow.com/questions/40635566/cant-install-sense-plugin-for-kibana

  11. Jan 2017
  12. Dec 2016
  13. Jan 2016
    1. UI components for ElasticsearchThe easiest way to build a great search experience with Elasticsearch.

      UI components for Elasticsearch

  14. Nov 2015
    1. Useful background on ElasticSearch's Percolator functionality. Includes some useful notes on the implementation and factors such as performance impact and memory usage.