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

Teamwork makes the dream work. Elastic App Search is pleased to announce role based access controls for premium plans. With role based access control, you can easily add and remove users, assign one of 6 pre-defined roles, and limit access to only certain Engines. You can keep large teams of up to 100 people&nbsp;organized over many secure&nbsp;projects.<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt3418f0b791391173/5c57d3fc0da9acd10bcc8e2e/pretty-manage-screen-busy.png" data-sys-asset-uid="blt3418f0b791391173" alt="pretty-manage-screen-busy.png"> You can select from six predefined&nbsp;roles: <ol><li>Owner: Full control over the account, from Engine creation, to credentials, to document curation, search settings, user management, and billing.</li><li>Admin: Everything that an owner can do, but lacks edit access to billing.</li><li>Dev: Configure all aspects of an Engine, its credentials, its search settings, and its documents.</li><li>Editor: Manage search settings within the dashboard; adjust Relevance Tuning, build Curations, and arrange Synonyms.</li><li>Analyst: View documents, test queries, and access analytics.</li><li>Finance: Manage billing details.</li></ol> Building your team within App Search is a quick operation. Send an invitation via email to your prospective members, then manage access levels individually from the Users menu: <img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt7a7e64a25ccbd914/5c57d3f602ac90e80ba0a866/tuning-a-user.png" data-sys-asset-uid="blt7a7e64a25ccbd914" alt="tuning-a-user.png"> If you would like a hand getting your roles configured, we have a <a href="https://swiftype.com/documentation/app-search/guides/role-based-access-control">Role Based Access Control Guide</a> available within the documentation. <h2>Sounds Good! But What’s App Search? </h2> If you want to provide search within your applications — to quickly index your data, and then construct an application or product from it — you will be interested in Elastic App Search. It’s a solution built atop the Elastic Stack that provides the tools to build leading search experiences. Calibrate robust search relevance features and view insightful analytics through refined APIs and an intuitive dashboard. You can jump right into App Search with a &nbsp;<a href="https://www.elastic.co/app-search/service?elektra=role-based-access-control-blog" target="_blank">14-day free trial</a> &nbsp;— no credit card required.

rbac-troopers.jpg

rbac-troopers-thumb.jpg

Elastic App Search: Announcing Role Based Access Control

Elastic App Search provides you with a robust set of API endpoints to build any type of search experience. While modern tools and a blank canvas can be inspiring, we want you to craft functional and valuable things as quickly as possible. And so, we bring you the App Search Reference UI. 
<h2>Open Sourcery
</h2>The <a href="https://github.com/swiftype/app-search-reference-ui-react">Elastic App Search Reference UI</a> is written in&nbsp;React. It is an open source developer tool that has been woven into the App Search dashboard. Its goal is twofold:
<ol>
<li>Provide a clean and dynamic search preview to experiment with features like facets, pagination, and sorting.</li>
<li>Generate a quality design and developmental foundation for new search experiences. &nbsp;
</li>
</ol>You can see a live Reference UI by visiting: <a href="https://parks.swiftype.info">https://parks.swiftype.info</a>.
<h2>Field Day
</h2>Before we dig deeper into the Reference UI, we should consider a key goal of App Search: provide relevant search. Relevance is the key to the value of search, for both your end-user and your business goals. But what does it mean, to be relevant?
Relevance is how well a result can fulfill the needs of the user or system that requested it. In technical terms, a query is analyzed against document fields and the most relevant document is returned given how well the field values match the query.
Code and national parks feel like a nice pair, and so we will take a practical look at the Reference UI through the eyes of the national parks data set. It has a schema containing the following fields:
<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>Within this data set, a park is less vast and wood-y, like this…
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt5594e4870938fc30/5c304c8fc0508d076e1712e1/mosquito-creek.jpg" data-sys-asset-uid="blt5594e4870938fc30" alt="" "="">
… And more concise and document-y, like this…
<pre class="prettyprint">{
 "nps_link": "https://www.nps.gov/cong/index.htm",
 "title": "Congaree",
 "date_established": "2003-11-10T06:00:00+00:00",
 "world_heritage_site": "false",
 "states": "South Carolina",
 "description": "On the Congaree River, this park is the largest portion of old-growth floodplain forest left in North America. Some of the trees are the tallest in the eastern United States. An elevated walkway called the Boardwalk Loop guides visitors through the swamp.",
 "visitors": 143843,
 "id": "park_congaree",
 "location": "33.78,-80.78",
 "square_km": 106.3,
 "acres": 26275.82
}
</pre>While not nearly as lush, the JSON-ified version is more searchable. We want to match queries against field values with great accuracy, which is why we need structure.
If we search for “old growth” within our search engine, Congaree National Park will be our first result. The text “old-growth” is included as part of the value of the `description` field. But we also return 10 other parks which describe themselves as “old-growth”: Yellowstone, Yosemite, Petrified Forest...
The results are relevant&nbsp;—&nbsp;we searched for “old growth” and we returned 10 parks which contain old-growth forests. But, what now? We have 10 results and we would like 1.Relevance can be fine tuned by the search provider or by the search user.
A search provider can leverage a feature like App Search Curations to promote, rearrange, and hide documents for a given query. If Yellowstone park would make a better first result for “old growth” forests, then we can curate the result set to place it on top. If Congaree were to close its doors to visitors, we could hide it from our results.
A search user can use the interactive tools provided within the search experience. Two such tools are present within the Reference UI: facets and sorting. A user can choose to narrow down the parks by state and whether or not they are a world heritage site. They can sort by the number of acres or the number of visitors.
An excellent search experience will not just provide relevant and tuned results by default, but allow searchers to further explore into the result data.
<h2>Back to the Lab </h2>After our trip to the woods, we are now back within the App Search dashboard. We have an Engine filled with national parks and we have clicked the Reference UI button within Engine navigation.
Configuring the Reference UI is a matter of defining fields...
<ul>
	<li>Title Field: The prominent name or title to display within search results. We will use the <code>title</code> field.</li>
	<li>Facet Field: A facet is a count based on a field. It is a way to refine search results using a shared field value as a grouping point. We will facet using the <code>state</code> and <code>world_heritage_site</code> fields.</li>
	<li>Sort Field: Ascending, or descending? And based on which field? We will choose the <code>acres</code> and <code>visitors</code> fields, so that people can find parks which are large or small, busy or quiet.</li>
	<li>URL Field: Search results will often link back to something else within your website or application: a product, an article, whatever it may be. We have the <code>nps_link</code> field.</li>
</ul>As we fill in these fields, the image to the left will illuminate which function you are tuning. Give it a try using your own Engine, or your national parks demo Engine.
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt85998fee2ed05d5e/5c304c8825a401fc6fe4f49b/reference-ui-with-fields.png" data-sys-asset-uid="blt85998fee2ed05d5e" alt="" "="">
When we click Generate a Preview, it appears just like our sample application. And when we search for “old growth"...
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltbbd9c245556d3fe8/5c304c84ebb7714d66027022/reference-ui-search-demo.png" data-sys-asset-uid="bltbbd9c245556d3fe8" alt="" "="">
We get parks. Old growth parks! Our search term is highlighted, we have a Relevance dropdown to change our sort order and field, a Show dropdown to change the size of our result set, and a sidebar with our faceting parameters: states and world heritage sites. But we still have 10 parks… No problem, the user will use the faceting, sorting, and pagination tools available and pick the best one.
<h2>Growing the Seed </h2>If you were just looking to experiment with relevance tuning or seeking inspiration, then we might be finished. If we want to start building, then we can click Download.
Clicking download retrieves a .zip file containing the Reference UI repository pre-populated with your configuration data. The repository will also contain a unique <code>config/engine.json</code> generated by App Search based on your account and field information.
It looks like this:
<pre class="prettyprint">{
 "engineName": "sample-engine",
 "hostIdentifier": "host-2376rb",
 "searchKey": "search-soaewu2ye6uc45dr8mcd54v8", 
 "fields": [
 "description",
 "nps_link",
 "location",
 "states",
 "title",
 "visitors",
 "world_heritage_site",
 "acres",
 "square_km",
 "date_established"
 ],
 "sortFields": [
 "visitors",
 "acres"
 ],
 "facets": [
 "states",
 "world_heritage_site"
 ],
 "titleField": "title",
 "urlField": "nps_link"
}
</pre>Now, within the unzipped Reference UI repository…
<pre class="prettyprint">npm install && npm start
</pre>Your Reference UI will run locally and provide search out of the box. The UI is yours to fork, customize, and build upon however you wish. The repository is maintained should you want to report issues or contribute changes upstream.
The Reference UI is not far from a viable search implementation. Styling can be changed within <code>src/styles</code> and the HTML structure can be altered within <code>src/components</code>. The README included within the repository will guide you through the relationship between the React components and the App Search APIs which perform the heavy lifting of search.
As with any open source initiative, we are excited to see what sort of UIs the community will create. Perhaps your next search experience will not only provide relevant and valuable search to your users, but inspire others to push the state of search to exciting new places.
<h2>Summary </h2>The Elastic App Search Reference UI is a foundation to help you build or test great search experiences. Whether you are looking to explore your relevance tuning in a closer-to-production sandbox or you are building a brand new experience, you have the tools you need and the seed to get started. You can read the Reference UI guide in the <a href="https://swiftype.com/documentation/app-search/guides/reference-ui">App Search documentation</a> for more information.
Enjoy the Reference UI and Elastic App Search with a <a href="/cloud/app-search-service">14-day free trial</a> — no credit card required.

plants-growin-nicely.jpg

plant-yaaaas.jpg

Kickstart Search with the Elastic App Search Reference UI

Elastic App Search now supports multiple users. Each account can now invite up to 100&nbsp;team members. Now your whole team can engage with&nbsp;the Elastic App Search&nbsp;dashboard.
<h2>Collaboration Station</h2>Elastic App Search is flexible. It is a powerful, well-documented, and accessible tool that a developer can use to craft cohesive and enjoyable search experience. You can build search around your ecommerce store, your administrative dashboard filled with customer logs, the objects within your mobile game — anything you can imagine, anywhere you can program it.
While it is flexible in its ability to provide search in many places, it is most flexible in who can use it to generate value. Whether you are a developer or not, the Elastic App Search dashboard can provide you with useful tools and insights.
Such as Analytics, for example:
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt3079b67afc9d7f3c/5c57dbf865ace9e30b3162b1/analytics.png" data-sys-asset-uid="blt3079b67afc9d7f3c" alt="analytics.png">
Within the Analytics view, anyone can see what users are searching for, finding, and not finding. Search data, unlike any other form of data, begins with a free expression. Search expressions provide organic data in a way that only search can provide. With it, you can recalibrate your search results to match the thoughts people use when they navigate through search.
You can build synonym sets to capture overlapping terms, like “car”, “automobile”, and “vehicle” — you can curate results, promoting or hiding results for a particular query, and even get deep into fine grained relevance tuning:<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt164fa0b5d31d7d2e/5c57dbf052256ff20b4afae3/relevance-tuning.png" data-sys-asset-uid="blt164fa0b5d31d7d2e" alt="relevance-tuning.png">
All of this can be done within the dashboard. Once you have built Elastic App Search into your applications, any stakeholder has the potential to generate a significant return. And so, we bring you multi-user support.
<h2>Multiply</h2>You can invite users on any subscription plan. To do so, click the Users option within the sidebar. You will appear here:
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt88de2e9d8a5a8346/5c57dbed893c9ee20b66f50a/first-users-screen.png" data-sys-asset-uid="blt88de2e9d8a5a8346" alt="first-users-screen.png">
Next, click the green Add Users button. You will then be able to invite up to 100&nbsp;users via email, comma separated...<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltd6f74800a1dfd6ff/5c57dbdfc545afde0bc70854/add-team-mates.png" data-sys-asset-uid="bltd6f74800a1dfd6ff" alt="add-team-mates.png">
Once you click Invite, an email will appear within each inbox. Each user must then accept the invitation. Once they have done so, they will create their account or sign-in with Google. After that, the dashboard is theirs to explore.
You can also revoke invites, should you decide that someone is to miss out…<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/blt0ecd1989192427ec/5c57dbd68d25f6030ca04331/revoke-invite.png" data-sys-asset-uid="blt0ecd1989192427ec" alt="revoke-invite.png" "="">
And with that, you have your team
<img src="https://images.contentstack.io/v3/assets/bltefdd0b53724fa2ce/bltc212aa4302c053ef/5c57dbca22d96be10bcca35b/users-added.png" data-sys-asset-uid="bltc212aa4302c053ef" alt="users-added.png" "="">
By default, the original account owner is considered the Owner. Each other person is considered an Admin. An Owner is the only individual capable of managing billing and account level settings, such as the account name. Should you need multiple owners, our support team can help you.
<h2>Summary</h2>Elastic App Search aims to drastically reduce the friction when building search within any website or application. Whether you are threading multiple streams of data together and looking to parse it intelligently, building an ecommerce platform, or building the knowledge base of your wildest dreams, why not bring the whole team along for the ride? Multi-user Elastic App Search accounts will help you do just that.
You can jump right into Elastic App Search with a <a href="/cloud/app-search-service?ultron=app-search-multi-user&elektra=blog">14-day free trial</a> — no credit card required.

sheepers-creepers.jpg

sheepers-creepers-thumb.jpg

Team Tuning with Multi-User Support in Elastic App Search

Start free trial

Blog Footer CTA

Sign up for Elastic Cloud free trial

headshot-brain-stevenson-300x300.jpg

Principal Software Engineer

Brian Stevenson

Надсилаючи цю форму ви погоджуєтеся з <a href="/legal/terms-of-use">Умовами надання послуг Elastic</a>. Ваші особисті дані будуть опрацьовані відповідно з <a href="/legal/privacy-statement">Положеннями про конфіденційність Elastic</a>.

Newsletter GDPR Text - Ukrainian

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_self">Terms of Service</a>, and you agree to receive the <a href="/legal/privacy-statement#how-we-use-the-information" target="_self">selected communications</a> at the contact details you provided above. See <a href="/legal/privacy-statement/" target="_self">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Communication Preferences - ONLY for /communication-preferences

By submitting you agree to <a href="/agreements/global/cloud-services-monthly" rel="nofollow">Elastic Cloud Terms of Service</a>. Your personal data will be processed in accordance with <a href="/legal/privacy-statement">Elastic's Privacy Statement</a>.

Cloud Trial GDPR Text

Intentionally Blank

By submitting you acknowledge that you've read and agree to our <a href="/legal/serverless-preview-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Serverless GDPR Text

提交即表示您確認已詳閱並同意我們的<a href="/legal/elastic-cloud-account-terms" target="_blank">服務條款</a>，且同意 Elastic 使用您在上方提供的個人資料<a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">與您聯絡</a>，為您提供相關產品和服務的資訊。如需詳細說明或隨時想停止收到產品和服務資訊，請參閱 <a href="/legal/privacy-statement/" target="_blank">Elastic 的隱私聲明</a>。

Newsletter GDPR Text - TW

By submitting you acknowledge that you've read and agree to our <a href="/legal/elastic-cloud-account-terms" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.By submitting this form, I agree to Elastic sharing my contact information with Google Cloud. I also agree to Elastic giving my information to the vendor for the purpose of shipping my food package.

GDPR Text + Google Cloud

Inviando la registrazione (1) esprimi il consenso ai <a href="/legal/terms-of-use">termini e condizioni di Elastic</a> e <a href="/legal/privacy-statement">all’informativa sulla privacy</a>, nonché (2) a ricevere saltuarie e-mail.

Newsletter GDPR Text - Italian

By submitting you acknowledge that you've read and agree to our <a href="/legal/terms-of-use" target="_blank">Terms of Service</a>, and that Elastic may <a href="/legal/privacy-statement#how-we-use-the-information" target="_blank">contact you</a> about our related products and services, using the details you provide above. See <a href="/legal/privacy-statement/" target="_blank">Elastic’s Privacy Statement</a> for more details or to opt-out at any time.

Newsletter GDPR Text

Load more

Overview

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content

Can't make it? Register and we'll send you the recording. You'll also receive an email with related content.

You'll also receive an email with related content.

You'll also receive an email with related content

Speakers

Close

See more insights

The content on this page is not available in the selected language. As Elastic grows globally, we continue to support content in multiple languages.

Author

Articles by Brian Stevenson

Principal Software Engineer, Elastic

Elastic App Search: Query Suggestion API Now Available

Elastic App Search: Announcing Role Based Access Control

Kickstart Search with the Elastic App Search Reference UI

Team Tuning with Multi-User Support in Elastic App Search