Action
| The last action dispatched on the history stack. |
-| [block](./kibana-plugin-core-public.scopedhistory.block.md) | | (prompt?: string | boolean | History.TransitionPromptHook<HistoryLocationState> | undefined) => UnregisterCallback
| Not supported. Use [AppMountParameters.onAppLeave](./kibana-plugin-core-public.appmountparameters.onappleave.md). |
+| [block](./kibana-plugin-core-public.scopedhistory.block.md) | | (prompt?: string | boolean | History.TransitionPromptHook<HistoryLocationState> | undefined) => UnregisterCallback
| Add a block prompt requesting user confirmation when navigating away from the current page. |
| [createHref](./kibana-plugin-core-public.scopedhistory.createhref.md) | | (location: LocationDescriptorObject<HistoryLocationState>, { prependBasePath }?: {
prependBasePath?: boolean | undefined;
}) => Href
| Creates an href (string) to the location. If prependBasePath
is true (default), it will prepend the location's path with the scoped history basePath. |
| [createSubHistory](./kibana-plugin-core-public.scopedhistory.createsubhistory.md) | | <SubHistoryLocationState = unknown>(basePath: string) => ScopedHistory<SubHistoryLocationState>
| Creates a ScopedHistory
for a subpath of this ScopedHistory
. Useful for applications that may have sub-apps that do not need access to the containing application's history. |
| [go](./kibana-plugin-core-public.scopedhistory.go.md) | | (n: number) => void
| Send the user forward or backwards in the history stack. |
diff --git a/docs/setup/docker.asciidoc b/docs/setup/docker.asciidoc
index 75a9799d70fbdb..25883307e69f0d 100644
--- a/docs/setup/docker.asciidoc
+++ b/docs/setup/docker.asciidoc
@@ -120,7 +120,6 @@ The following settings have different default values when using the Docker
images:
[horizontal]
-`server.name`:: `kibana`
`server.host`:: `"0.0.0.0"`
`elasticsearch.hosts`:: `http://elasticsearch:9200`
`monitoring.ui.container.elasticsearch.enabled`:: `true`
diff --git a/examples/search_examples/kibana.json b/examples/search_examples/kibana.json
index 07bb6a0b750e30..83996c20343811 100644
--- a/examples/search_examples/kibana.json
+++ b/examples/search_examples/kibana.json
@@ -4,7 +4,7 @@
"kibanaVersion": "kibana",
"server": true,
"ui": true,
- "requiredPlugins": ["navigation", "data", "developerExamples", "kibanaUtils"],
+ "requiredPlugins": ["navigation", "data", "developerExamples", "kibanaUtils", "share"],
"optionalPlugins": [],
- "requiredBundles": []
+ "requiredBundles": ["kibanaReact"]
}
diff --git a/examples/search_examples/public/application.tsx b/examples/search_examples/public/application.tsx
index 7d3b585ba48526..1920cdbe5c697c 100644
--- a/examples/search_examples/public/application.tsx
+++ b/examples/search_examples/public/application.tsx
@@ -8,26 +8,67 @@
import React from 'react';
import ReactDOM from 'react-dom';
+import { Router, Route, Redirect } from 'react-router-dom';
+import { I18nProvider } from '@kbn/i18n/react';
import { AppMountParameters, CoreStart } from '../../../src/core/public';
import { AppPluginStartDependencies } from './types';
-import { SearchExamplesApp } from './components/app';
+import { SearchExamplePage, ExampleLink } from './common/example_page';
+import { SearchExamplesApp } from './search/app';
+import { SearchSessionsExampleApp } from './search_sessions/app';
+import { RedirectAppLinks } from '../../../src/plugins/kibana_react/public';
+
+const LINKS: ExampleLink[] = [
+ {
+ path: '/search',
+ title: 'Search',
+ },
+ {
+ path: '/search-sessions',
+ title: 'Search Sessions',
+ },
+ {
+ path: 'https://github.com/elastic/kibana/blob/master/src/plugins/data/README.mdx',
+ title: 'README (GitHub)',
+ },
+];
export const renderApp = (
- { notifications, savedObjects, http }: CoreStart,
- { navigation, data }: AppPluginStartDependencies,
- { appBasePath, element }: AppMountParameters
+ { notifications, savedObjects, http, application }: CoreStart,
+ { data, navigation }: AppPluginStartDependencies,
+ { element, history }: AppMountParameters
) => {
ReactDOM.render(
-
+ This example shows how you can use
+ Start a long-running search, save the session and then restore it. See how fast search
+ is completed when restoring the session comparing to when doing initial search.
+
+ Follow this demo step-by-step:{' '}
+ configure the query, start the search and then save your session. You can save
+ your session both when search is still in progress or when it is completed. After you
+ save the session and when initial search is completed you can{' '}
+ restore the session: the search will re-run reusing previous results. It will
+ finish a lot faster then the initial search. You can also{' '}
+ go to search sessions management and get back to the stored results from
+ there.
+
+ This demo works best with
+ We recommend to enable it in your