Elastic App Search beta5 has arrived! Take it for a free test drive.

blog-banner-app-search.png

blog-thumbnail-app-search.png

Elastic App Search Beta 5 released

Elastic App Search has been upgraded to beta4. Come try it out for free while the beta is still open!

Elastic App Search Beta 4 released

Elastic App Search has been upgraded to beta3. Come see what we've cooked up!

Elastic App Search Beta3 Released

Elastic App Search now has a slick Query Suggestions API. Its function is known by many names, but whatever you call it, it helps make great search experiences.

The&nbsp;Query Suggestion API&nbsp;is now available within&nbsp;<a href="https://www.elastic.co/app-search/service">Elastic App Search</a>. "Did you mean autocomplete?"Ah, yes, thanks — we can call it that, or typeahead, or autosuggest. While the name of the technique might differ, the constant is that query suggestions can greatly improve a search experience. Read along to learn more, or&nbsp;<a href="https://swiftype.com/documentation/app-search/api/query-suggestion">visit the documentation</a>&nbsp;to get building.<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blta58798bd58c17fb0/5c98d7ce55e02a1e5a5e9b1e/query-suggestions.gif" data-sys-asset-uid="blta58798bd58c17fb0" alt="query-suggestions.gif"><h2>Suggestive!</h2>As a user types a query, the&nbsp;Query Suggestion API&nbsp;looks for strong queries to suggest. Herein lies the key: the endpoint does not suggest results.&nbsp;A quality search experience, by its nature, will provide the most relevant results.&nbsp;But sometimes users have trouble finding the right words to use when searching, and this endpoint can help them.Imagine we have a search engine full of outdoor parks;&nbsp;we indexed all of our park objects into an Elastic App Search Engine, and they are ready to be searched upon. &nbsp;A document might look like this:<pre class="”prettyprint”" style="font-size: 12.600000381469727px;"> {
 "nps_link": "https://www.nps.gov/zion/index.htm",
 "title": "Zion",
 "date_established": "1919-11-19T06:00:00+00:00",
 "world_heritage_site": "false",
 "states": [ "Utah"],
 "description": "Located at the junction of the Colorado Plateau, Great Basin, and Mojave Desert, this park contains sandstone features such as mesas, rock towers, and canyons, including the Virgin River Narrows. The various sandstone formations and the forks of the Virgin River create a wilderness divided into four ecosystems: desert, riparian, woodland, and coniferous forest.",
 "visitors": 4295127,
 "id": "park_zion",
 "location": "37.3,-113.05",
 "square_km": 595.8,
 "acres": 147237.02
 }
</pre>When a user conducts a search within our application, we have decided to match results based on the&nbsp;state&nbsp;and&nbsp;title&nbsp;fields of the park documents. That way, someone can type the name of the park they want to visit or the state that it is located, and receive relevant results.Now let us put ourselves in the shoes of a searcher...A friend told them about a beautiful park, but they cannot quite remember its name. It's Zion National Park, but they don't know that yet.They want to search for it and book a ticket to visit it.“It started with a Z… Zeyeon, maybe?… Hmm…”And so they attempt a search for “zeyeon”, first without query suggestions:<pre class="”prettyprint”" style="font-size: 12.600000381469727px;"> {
 "meta": {
 "warnings": [],
 "page": {
 "current": 1,
 "total_pages": 0,
 "total_results": 0,
 "size": 10
 },
 "request_id": "85b78b8f32ac81253cc1654e540e0625"
 },
 "results": []
 }
</pre>No surprise, the query returns zero results.Even with accurate relevance, that query is not even close to the&nbsp;matching "Zion"&nbsp;document.&nbsp;We don't want the user to get discouraged and end their search.&nbsp;When using&nbsp;query suggestions,&nbsp;their search experience might go like this:”Hmmm… There was a z”…<pre class="”prettyprint”" style="font-size: 12.600000381469727px;"> curl -X POST 'https://host-2376rb.api.swiftype.com/api/as/v1/engines/sample-engine/query_suggestion' \
 -H 'Content-Type: application/json' \
 -H 'Authorization: Bearer search-7eud55t7ecdmqzcanjsc9cqu' \
 -d '{
 "query": "z",
 "types": {
 "documents": {
 "fields": [
 "title",
 "states"
 ]
 }
 },
 "size": 4
 }'
</pre>”That’s right! Zion National Park! Time to book a ticket!”<pre class="”prettyprint”" style="font-size: 12.600000381469727px;"> {
 "results": {
 "documents": [
 {
 "suggestion": "zion"
 }
 ]
 },
 "meta": {
 "request_id": "8d37831753eb9d5636a761f5fb3d6767"
 }
 }
</pre>The right&nbsp;title&nbsp;value, “zion”, returned as a suggestion. The suggestion can then be used to fuel their actual search.&nbsp;By guiding the searcher through the querying process, we help them assemble the most effective searches.<h2>May We Also Suggest...</h2>The&nbsp;Query Suggestion API&nbsp;is but one tool in a robust, relevance improving search toolbox.Other valuable tools include&nbsp;<a href="https://swiftype.com/documentation/app-search/guides/synonyms">Synonyms</a>, which build groupings of similar search terms.A search for any synonym will return results relevant to the entire set.The prototypical example of a synonym set is for car: car, automobile, vehicle. &nbsp;Or, in the park, consider mountains: mountain, cliff, peak, summit:<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt56e26c8d50b0a8c1/5c57d3cbc545afde0bc7082c/synonym.png" data-sys-asset-uid="blt56e26c8d50b0a8c1" alt="synonym.png">Another tool is&nbsp;<a href="https://swiftype.com/documentation/app-search/guides/relevance-tuning">Relevance Tuning</a>, which can boost the relevance of documents given certain field values, and tune the baseline scoring weight attributed to each field.You can boost results given their proximity to a location coordinate provided by the user:&nbsp;“Find the park nearest to me!”&nbsp;Or tune your&nbsp;title&nbsp;field so its matches reward&nbsp;greater than those of other fields:<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltf5eb29dbd2c87a0a/5c57d3c54c9f4feb0b4c581f/relevence-tuning.png" data-sys-asset-uid="bltf5eb29dbd2c87a0a" alt="relevence-tuning.png">Finally, there are curations: curate the results of certain queries.Perhaps you sell “tea” and you want a certain seasonal tea ranked first &nbsp;for “green tea” queries. Or if something is out of stock or season, and you want to hide it from your result sets.With outdoor parks, we want to promote Rocky Mountain Park for those who query “mountains”:<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt6e57cd17d7347368/5c57d3c0eab90dd80b53ee7e/curations.png" data-sys-asset-uid="blt6e57cd17d7347368" alt="curations.png">All of these tools have refined APIs and matching dashboard UIs, and are informed through fully API-digestible analytics, which can be organized with tags to&nbsp;<a href="https://swiftype.com/documentation/app-search/guides/tags">automate deep relevance tuning</a>&nbsp;of your search experience.<h2>Summary</h2>The&nbsp;Query Suggestion API&nbsp;will help your users find the right words. When paired with the rest of the relevance refining features in Elastic App Search, we think you’ll enjoy seeing people find just the think they are seeking. The API is also available within the&nbsp;<a href="https://github.com/swiftype/swiftype-app-search-javascript">App Search JavaScript</a>&nbsp;client and the <a href="https://swiftype.com/documentation/app-search/guides/reference-ui">Reference UI</a>.You can get started today with a &nbsp;<a href="https://www.elastic.co/app-search/service?elektra=query-suggestion-api-blog">free 14 day trial</a>&nbsp;of our hosted version or &nbsp;<a href="https://elastic.co/downloads/app-search">download the beta</a>&nbsp;of the self-managed version.&nbsp;Each new trial comes preloaded with the National Parks data set, so you can experiment before bringing your own data.

map-full-lego.jpg

park-lego-thumb.jpg

Elastic App Search: Query Suggestion API Now Available

Stroll through some of the world's finest parks within Elastic App Search Sample Engines. Along the way, learn how you can create engaging search experiences.

Let's go for a walk in the park. Each new Elastic App Search account now provides access to breathtaking National Parks. But not the outdoor, fresh air kind of park... This kind of park:<pre class="prettyprint">{
 "nps_link": "https://www.nps.gov/wrst/index.htm",
 "title": "Wrangell–St. Elias",
 "date_established": "1980-12-02T06:00:00+00:00",
 "world_heritage_site": "true",
 "states": "Alaska",
 "description": "An over 8 million acres (32,375 km2) plot of mountainous country—the largest National Park in the system—protects the convergence of the Alaska, Chugach, and Wrangell-Saint Elias Ranges, which include many of the continent's tallest mountains and volcanoes, including the 18,008-foot Mount Saint Elias. More than a quarter of the park is covered with glaciers, including the tidewater Hubbard Glacier, piedmont Malaspina Glacier, and valley Nabesna Glacier.",
 "visitors": 79047,
 "id": "park_wrangell–st.-elias",
 "location": "61,-142",
 "square_km": 33682.6,
 "acres": 8323146.48
}
</pre>There are 59 of them included within the National Parks demo Engine, which will appear in your list of Engines once you sign up for an account.<h2>Forests and Fun(gi)</h2>Before today, we would tell you about the features within App Search and require that you bring your own data in order to experience them. Instead, we chose to ... leaf... you with something helpful to guide your trial explorations. The National Park demo Engine is pre-loaded with data on US National Parks. You can use this data set for experimentation. You can run example queries, tune relevance, view analytics, alter the schema, and do whatever else you can think to do. No need to bring any data until you are ready.<h3>Saplings: Documentation Boosts</h3>The <a href="https://swiftype.com/documentation/app-search/api/search">App Search documentation</a> now matches the National Parks dataset. This will help you if you are interested in trying out a feature like <a href="https://swiftype.com/documentation/app-search/api/search/boosts#proximity-boosts">Proximity Boosts</a>. A Boost allows you to boost the relevance score of any documents that relate to a value within a document field. Proximity Boosting makes use of geolocation search. The boost is calculated by a factor and function of your choosing, and is derived by the value within the `center` field. The center might be a location you receive from direct user input or the user’s device — it is the coordinate that represents where a person is or will be. &nbsp;The following example is right from our documentation. Try it out within the command line on your own machine:<pre class="prettyprint">curl -X GET 'https://host-2376rb.api.swiftype.com/api/as/v1/engines/national-parks-demo/search' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer search-soaewu2ye6uc45dr8mcd54v8' \
-d '{
 "boosts": {
 "location": {
 "type": "proximity",
 "function": "linear",
 "center": "25.32, -80.93",
 "factor": 8
 }
 },
 "query": "old growth"
}'
</pre>We want to find old growth National Parks that are close to the Elastic office in Mountain View — the coordinates for the office are: `25.32, -80.93`. When we run the query, our top results appear relative to our center. Now, try the query with your own coordinates — which old growth park is closest to you?This example from the documentation contains pre-populated credentials from our demo account. Replace the credentials and try using your own sample engine — the same results will appear. But not for long.&nbsp;As you apply features like Relevance Tuning, Synonyms and Curations, the results will start to differ from our basic, untuned examples.<h3>Growing Roots: Relevance Tuning</h3>Relevance Tuning provides a list of all of the fields within your Engine’s schema. The raw National Parks schema looks like this:<pre class="prettyprint">{
 "description": "text",
 "nps_link": "text",
 "states": "text",
 "title": "text",
 "visitors": "number",
 "world_heritage_site": "text",
 "location": "geolocation",
 "acres": "number",
 "square_km": "number",
 "date_established": "date"
}
</pre>And so Relevance Tuning within the dashboard then looks like this:<img data-image="jdzmhz4o08m8" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt903f340baf4053f1/5c583a37f967c7fc0b4c69bd/relevance-tuning-empty.png" data-sys-asset-uid="blt903f340baf4053f1" alt="relevance-tuning-empty.png">The Preview search bar on the right side allows you to test queries so that you can see how your tuning is impacting results. Each field can be calibrated to adjust the result set in real time. No re-indexing or re-engineering of any sort is required. Once finished, click save, and the impact is immediate. So what if a user wants to go to a National Park with beautiful mountains?&nbsp;Out of the box, a query for mountains would look like this:<img data-image="ba5duj4ppflz" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltb47dae9cccdbd316/5c583a32bfa899f60ba15d95/relevance-tuning-meh-mountains.png" data-sys-asset-uid="bltb47dae9cccdbd316" alt="relevance-tuning-meh-mountains.png">Hmmm — Great Smoky Mountains is third on the list. Some beautiful mountain ranges are missing. There are other parks which have much better mountain ranges than the desert landscape of Joshua Tree. Perhaps we would see more relevant results if we adjusted the weight of one of our fields?<img data-image="of7r3kstbv90" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltac86d13101bac6a1/5c583a2b516e21cf0b2a1206/relevance-tuning-good-mountains.png" data-sys-asset-uid="bltac86d13101bac6a1" alt="relevance-tuning-good-mountains.png">We boosted the weight of our title field to 3. The results instantly shuffle — annnnd… that looks much better! The first three results are all for the finest of mountain ranges. Click save, and we are on our way.<h3>Seeds: Curations</h3>Tuning search relevance is exciting. But something still doesn’t feel quite right. If one is looking for Mountains, they should find the Rocky Mountains. The majestic range of mountains spans both Canada and the United States and will surely delight anyone looking specifically for mountains.&nbsp;The better the result we can provide, the more the user will trust our search, leading to more valuable interactions for them and a greater likelihood of accomplished business goals for us. To solve this, we look at Curations:<img data-image="olpybcj8j2ro" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt197ca5c79419b697/5c583a2516a7de000c2b3593/curations-query.png" data-sys-asset-uid="blt197ca5c79419b697" alt="curations-query.png">Curations begin with one or more queries. In this case, we want to curate the results for the “mountains” query...<img data-image="b057e1vpgusm" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blte281a17e3d948f31/5c583a20713ebdec0ba0723f/mountains-curation.png" data-sys-asset-uid="blte281a17e3d948f31" alt="mountains-curation.png">We can promote a document, making it appear first within the queries result set. Or, we can hide a document, removing it entirely from the result set. Now, when an individual searches for “mountains”, the first park they will see is the promoted Rocky Mountain National Park.<h3>Growth: Analytics</h3>Our explorations have left a trail. The queries we have been running are recorded as analytic events. When your search experience is live, this data will be invaluable to further tune relevance to best meet the needs of your users.<img data-image="n0ynsmcg00xi" src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt6c0d73aa4bba77dc/5c583a19f967c7fc0b4c69b7/analytics-growth.png" data-sys-asset-uid="blt6c0d73aa4bba77dc" alt="analytics-growth.png">As you start to see queries with no results, you will know whether to tune Synonyms to catch differences in syntax, like path and trail, park or site, mountains or cliffs. Or whether to curate certain popular queries that do not have have results, or tune our field weights to ensure the right fields are being searched.<h2>Summary</h2>The new National Parks demo within each Elastic App Search account will help you tour the product without bringing your data along. It will appear as national-parks-demo, does not count against your total Engine count,&nbsp;and can be deleted at anytime. Whenever you are ready, you can create your own Engine, fill it with your own documents, and deliver relevant search to your visitors. Until then, take a walk through the park and explore App Search through the dashboard or the matching examples within the documentation. You can stroll right into Elastic App Search with a&nbsp;<a href="/app-search/service?elektra=a-walk-in-the-park-with-app-search-blog" target="_blank">14-day free trial</a>&nbsp; — no credit card required. <h4>Attribution</h4>The National Parks data set is licensed under Creative Commons. In exchange for its free use, we must provide attribution. The dataset was found within <a href="https://data.world/">data.world</a> and was authored by <a href="https://data.world/kevinnayar">Kevin Nayar</a>. Thank you, Kevin, for making such interesting and functional datasets.

forest-bleed.jpg

forest-thumb.jpg

A Walk in the Park with Elastic App Search Sample Engines

Search is useful. The insights gained from search are even more so. Elastic App Search has a robust analytics suite that can turn insight into valuable action.

Elastic App Search now features a robust Analytics API suite. The Analytics API suite can help you gain valuable insight into the <code>clicks</code> and <code>queries</code> generated during a users’ search experience.
Are analytics valuable? How can you use them to further improve search relevance and the overall experience? Is the suite difficult to use? Continue on to explore these questions. Otherwise, feel free to dive right into the <a href="https://swiftype.com/documentation/app-search/api/analytics">Analytics documentation</a> to start weaving helpful search analytics into your applications.
<h2>Express Yourself</h2>Quality search provides two key benefits. The first is clear: you provide an expedient mechanism to connect visitors with the data they seek. Within internet business, there is great value in getting people where they want to go, as fast as possible. Whether they want to find a product, read an article, or investigate the right service, speedy acquisition of desired information is lucrative.
The second benefit is less obvious, but within it lies vast potential. Analyzing search patterns reveals deep insight into not just what, but how your users are searching. How do they form their queries? What language do they use, which common terms? How do user searches impact the achievement of business goals? Upon reflection, what are the unseen barriers that you have placed before your users?
Above all other forms of information discovery, search is unique in that it begins with a free expression. A user sees naught but an empty search bar and into this blank canvas they sail their free flowing ideas.
It is through analyzing this expression that we unveil great insight that can help us get ahead of the searcher, anticipating not only which content they might be seeking but supporting however they might be seeking it.
<h2>Analytical Magic</h2>To wrap our heads around the value of the Analytics API suite, we will put it into context. When a user performs a search, they create a <code>query</code>.
The <code>query</code> informs us of the value — the words, numbers, dates, or coordinates — used during the search. A <code>query</code> will generate <code>results</code> and if the result content is relevant then the user will produce a <code>click</code> upon engagement.
As we head into the realm of the practical, consider that we have an Elastic App Search Engine called <code>book-of-magic</code>. This Engine provides search within our Book of Magic application. We have a full repository of magical spells and various sorceries — for the modern witch or warlock - of today.
We can use the Analytics suite to perform queries at the Engine level. If we wanted to find the top 10 queries over the past 7 days, we can build a simple <code>GET</code> request against the <code>analytics/queries</code> endpoint...
<pre class="prettyprint">curl -X GET 'https://host-2376rb.api.swiftype.com/api/as/v1/engines/book-of-magic/analytics/queries' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer private-xxxxxxxxxxxxxxxxxxxxxxxx'
</pre>In return, we receive an array of our top 10 results and some metadata:
<pre class=" prettyprint=" "="">"results": [
 {
 "term": "fire",
 "clicks": 2204,
 "queries": 24838
 },
 {
 "term": "youth",
 "clicks": 1111,
 "queries": 49489
 },
 ## Truncated!
 ],
 "meta": {
 "page": {
 "size": 10,
 "current": 1
 }
 }
}
</pre>Our results array informs exact queries, as typed by the user. We see that the two most popular queries over the past 7 days are <code>fire</code> and <code>youth</code>. By looking only at these two results, we already see something valuable.
The term <code>youth</code> generated 24,651 more queries than <code>fire</code>, yet generated 50% less clicks. Hmm - perhaps our youth generating spells are not up to par — a potential area of improvement has been revealed.
Let us explore deeper into the <code>youth</code> query to form a better understanding. This time, we will request against the <code>analytics/clicks</code> endpoint and specify just the <code>youth</code> query:
<pre class="prettyprint>
curl -X GET 'https://host-2376rb.api.swiftype.com/api/as/v1/engines/book-of-magic/analytics/clicks' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer private-xxxxxxxxxxxxxxxxxxxxxxxx' \
-d '{
 &quot;filters&quot;: { &quot;query&quot;: &quot;youth&quot; }
}'
</pre>
In response:

<pre class=" prettyprint=" ">{
 "results": [
 {
 "document_id": "41384",
 "clicks": 50
 },
 {
 "document_id": "49109",
 "clicks": 40
 },
 {
 "document_id": "44343",
 "clicks": 21
 },
 {
 "document_id": "321",
 "clicks": 0
 }
 ],
 "meta": {
 "page": {
 "size": 4,
 "current": 1
 }
 }
}
</pre>We can see each document that would appear for that query, defined by <code>document_id</code>. A curio: document #321 is one of our best and most effective spells, yet it has 0 clicks — that should not be! We have identified an issue. Luckily, Elastic App Search can help you transform realization into useful action.
The Analytics suite is ideal for revealing issues of this nature. You know that people searching for <code>youth</code> would benefit from document #321. But they are not finding it. To fix this and improve your clicks, we could consider altering the title and subtitle of the document to make it more appealing. Or, we could apply a <a href="https://swiftype.com/documentation/app-search/guides/curations">Curation</a> through the API or the dashboard to promote document #321 as the first result for the <code>youth</code> query.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt0ba59e988f7aec63/5c6c47ef2b22f9f161d6d356/image1.png" data-sys-asset-uid="blt0ba59e988f7aec63" alt="image1.png" style="display: block; margin: auto;">
A final Analytics angle involves <code>counts</code>. The <code>anaytics/queries</code> and <code>analytic/cicks</code> endpoints provide specific values. Requesting against <code>analytics/counts</code> will instead give us a window into the general performance of search:
<pre class="prettyprint>
curl -X GET 'https://host-2376rb.api.swiftype.com/api/as/v1/engines/book-of-magic/analytics/counts' \
-H 'Content-Type: application/json' \
-H 'Authorization: Bearer private-xxxxxxxxxxxxxxxxxxxxxxxx'
</pre>
Our results will include <code>clicks</code> and <code>queries</code> — the default time frame is 7 days:

<pre class=" prettyprint=" ">{
 "results": [
 {
 "clicks": 55383,
 "queries": 98409,
 "from": "2018-09-01",
 "to": "2018-09-02"
 },
 {
 "clicks": 53822,
 "queries": 87489,
 "from": "2018-07-02",
 "to": "2018-07-03"
 },
 {
 "clicks": 59098,
 "queries": 91487,
 "from": "2018-07-03",
 "to": "2018-07-04"
 },
 ## Truncated!
 ]
}
</pre>Ah... it seems that roughly ~60% of queries result in clicks. While the large number of queries indicates that the hunt for magic is alive and well, we can surely improve the likelihood that a user will click on a search result — and thus help us achieve our business goals.
<h2>Summary: Conjuring Clicks</h2>The Analytics suite is packed full of filters and parameters that enable valuable and flexible insight into what is happening within your Elastic App Search Engine. By refining your knowledge of user search patterns, you can apply <a href="https://swiftype.com/documentation/app-search/guides/curations">Curations</a>, <a href="https://swiftype.com/documentation/app-search/guides/synonyms">Synonyms</a>, and <a href="https://swiftype.com/documentation/app-search/guides/search-customizations#relevance-tuning">Weights and Boosts</a> to fine-tune what is a already an optimized search experience.
To get even deeper into analytics, there are two other key features you can use to enrich data collection. The <a href="https://swiftype.com/documentation/app-search/api/clickthrough">Clickthrough API</a> can supplement the data that you receive when a user clicks on a result. In conjunction with <a href="https://swiftype.com/documentation/app-search/api/search#analytics">Tags</a>, which can be included within search and analytics queries, important questions can be answered about each click: Which browser is being used? Is the user on mobile? Does the user have an account?
You can jump right into Elastic App Search with a <a href="/app-search/service?elektra=introducing-analytics-api-suite-blog">free 14-day trial</a>&nbsp;— no credit card required. Providing a relevant, fluid, and dynamic search experience is just the beginning. Learning about your users, then adapting to and pre-empting their habits, is when search can truly help your applications take off.

questionable-image.jpg

questionable-thumbnail.jpg

Introducing the Analytics API Suite in Elastic App Search

Elastic App Search now supports multi-language Engines. See how you can improve already optimized search relevance within your choice of 13 languages.

Articles by Ioana Tagirta

Elastic App Search Beta 5 released

Elastic App Search Beta 4 released

Elastic App Search Beta3 Released

Elastic App Search: Query Suggestion API Now Available

A Walk in the Park with Elastic App Search Sample Engines

Introducing the Analytics API Suite in Elastic App Search

Introducing Multi-Language Engines in Elastic App Search

Products & Solutions

Company

Resources

Featured topics

News

Articles by Ioana Tagirta

Elastic App Search Beta 5 released

Elastic App Search Beta 4 released

Elastic App Search Beta3 Released

Elastic App Search: Query Suggestion API Now Available

A Walk in the Park with Elastic App Search Sample Engines

Introducing the Analytics API Suite in Elastic App Search

Introducing Multi-Language Engines in Elastic App Search