{"id":32312,"date":"2019-10-31T21:46:17","date_gmt":"2019-10-31T18:46:17","guid":{"rendered":"https:\/\/prohoster.info\/blog\/znakomstvo-s-elasticsearch-step-by-step\/"},"modified":"2019-10-31T21:46:17","modified_gmt":"2019-10-31T18:46:17","slug":"znakomstvo-s-elasticsearch-step-by-step","status":"publish","type":"post","link":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/znakomstvo-s-elasticsearch-step-by-step","title":{"rendered":"Getting acquainted with Elasticsearch step by step","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Hei!
\nI dag skal vi snakke om s\u00f8kemotoren Elasticsearch (heretter ES), som
\nbrukes av plattformen Docsvision 5.5.<\/p>\n

\"Getting
\n
\n<\/a><\/noindex><\/p>\n

1. Installasjon<\/h3>\n

\nDen nyeste versjonen kan lastes ned fra linken: www.elastic.co\/downloads\/elasticsearch<\/a><\/noindex>
\nSkjermbilde av installasjonsprogrammet nedenfor:
\n \"Getting
\n<\/p>\n

2. Sjekker drift<\/h3>\n

\nEtter at installasjonen er fullf\u00f8rt, g\u00e5r du til adressen
\nhttp:\/\/localhost:9200\/<\/noindex>
\nDet skal vises en side med status for ES, eksempel nedenfor:
\n\"Getting<\/p>\n

Hvis siden ikke \u00e5pnes, kontroller at Elasticsearch-tjenesten er startet. P\u00e5 Windows er dette
\ntjenesten Elasticsearch.
\n\"Getting
\n<\/p>\n

3. Koble til Docsvision<\/h3>\n

\nKoblingen til Elasticsearch konfigureres p\u00e5 siden for fulltekst
\nindeksering.
\n\"Getting
\n
\nHer m\u00e5 du spesifisere:
\n1. Adressen til Elasticsearch-serveren (angitt ved installasjon).
\n2. Tilkoblingsstrengen til DB.
\n3. Adressen til Docsvision (i formatet ConnectAddress=http:\/\/SERVER\/DocsVision\/StorageServer\/StorageServerService.
\nasmx<\/noindex>)
\n4. I fanen \u00abKort\u00bb og \u00abKataloger\u00bb m\u00e5 du konfigurere de dataene som
\nm\u00e5 indekseres.
\nDu m\u00e5 ogs\u00e5 s\u00f8rge for at kontoen som kj\u00f8rer tjenesten Docsvision
\nFulltext Indexing service, har tilgang til DB Docsvision p\u00e5 MS SQL.
\nEtter tilkoblingen m\u00e5 du sikre deg at det er opprettet oppgaver i MS SQL med prefikset:
\n\u00abDV:FullText_<DATABASE_NAME>_CardWithFilesPrepareRange\u00bb
\n \"Getting
\n
\nN\u00e5r konfigurasjonen er fullf\u00f8rt, vil s\u00f8kefeltet bli aktivert i Windows-klienten.<\/p>\n

4. REST API Elastic<\/h3>\n

\nAdministrator kan f\u00e5 variert informasjon om driften av Elasticsearch via
\ndet tilgjengelige REST API.
\nI de f\u00f8lgende eksemplene vil vi bruke Insomnia Rest Client.<\/p>\n

Henting av generell informasjon<\/h4>\n

\nS\u00e5 snart tjenesten har startet og fungerer (http:\/\/localhost:9200\/ i nettleseren), kan du
\nutf\u00f8re foresp\u00f8rsel:
\nhttp:\/\/localhost:9200\/_cat\/health?v<\/noindex><\/p>\n

Vi vil f\u00e5 svar om statusen for Elasticsearch-tjenesten (i nettleseren):
\n \"Getting
\nStatussvaret i Insomnia:
\n \"Getting
\nLa oss merke oss Status \u2014 Gr\u00f8nn, Gul, R\u00f8d. Den offisielle dokumentasjonen sier om statusene f\u00f8lgende:
\n\u2022 Gr\u00f8nn \u2014 Alt er bra (Klyngen fungerer som den skal)
\n\u2022 Gul \u2014 Alle data er tilgjengelige, men noen replikaer i klyngen er forel\u00f8pig ikke tildelt
\n\u2022 R\u00f8d \u2014 En del data er utilgjengelige av ulike \u00e5rsaker (klyngen fungerer normalt)
\nHenting av tilstander for noder i klyngen og deres status (jeg har 1 node):
\nhttp:\/\/localhost:9200\/_cat\/nodes?v<\/noindex>
\n\"Getting
\n
\nAlle indekser (indices) ES:
\nhttp:\/\/localhost:9200\/_cat\/indices?v<\/noindex>
\n\"Getting
\n
\nI tillegg til indeksene fra Docsvision, kan det ogs\u00e5 finnes indekser fra andre applikasjoner \u2014 heartbeat,
\nkibana \u2014 hvis du bruker dem. Det n\u00f8dvendige kan sorteres fra det un\u00f8dvendige. For eksempel,
\nla oss ta bare indekser med rd% i navnet:
\nhttp:\/\/localhost:9200\/_cat\/indices\/*card*?v&s=index<\/noindex>
\n \"Getting
\n<\/p>\n

Konfigurasjon av Elasticsearch <\/h4>\n

\nHenting av innstillinger for Elasticsearch:
\nhttp:\/\/localhost:9200\/_nodes<\/noindex>
\nResultatet vil v\u00e6re ganske omfattende, inkludert stier til loggene:
\n \"Getting
\n
\nHvordan kjenne igjen indekser, vi vet allerede at Docsvision gj\u00f8r dette automatisk, gir indeksen et navn i formatet:
\n<\u0438\u043c\u044f\u0431\u0434+\u0432\u0438\u0434\u0418\u043d\u0434\u0435\u043a\u0441\u0438\u0440\u0443\u0435\u043c\u043e\u0439\u041a\u0430\u0440\u0442\u043e\u0447\u043a\u0438>
\nDet er ogs\u00e5 mulig \u00e5 opprette en egen uavhengig indeks:
\nhttp:\/\/localhost:9200\/customer?pretty<\/noindex>
\nBare at dette vil v\u00e6re en PUT-request, ikke GET:
\n \"Getting
\n
\nResultat:
\n \"Getting
\n
\nDen neste foresp\u00f8rselen viser alle indekser, inkludert de nye (kunde):
\nhttp:\/\/localhost:9200\/_cat\/indices?v<\/noindex>
\n \"Getting
\n<\/p>\n

5. F\u00e5 informasjon om indekserte data<\/h3>\n

<\/p>\n

Status for Elasticsearch-indekser<\/h4>\n

\nEtter at den innledende konfigurasjonen fra Docsvision er gjort, b\u00f8r tjenesten v\u00e6re klar til \u00e5 arbeide og starte indeksering av data.
\nF\u00f8rst m\u00e5 vi sjekke at indeksene fylles opp og at st\u00f8rrelsen er st\u00f8rre enn standard 'bytes' med den kjente foresp\u00f8rselen:
\nhttp:\/\/localhost:9200\/_cat\/indices?v<\/noindex>
\nsom et resultat ser vi: indeksert 87 'oppgaver' og 72 'dokumenter' om vi snakker i termer av v\u00e5rt system:
\n \"Getting
\n
\nEtter en tid er resultatene slik (som standard kj\u00f8rer indekseringsjobben hvert 5. minutt):
\n\"Getting
\n
\nVi ser at antallet dokumenter har \u00f8kt.<\/p>\n

Hvordan forst\u00e5 at det n\u00f8dvendige kortet er indeksert?<\/h4>\n

\u2022 For det f\u00f8rste, m\u00e5 vi s\u00f8rge for at typen kort i Docsvision samsvarer med de angitte dataene i Elasticsearch-innstillingene.
\n\u2022 For det andre, vente p\u00e5 indekseringen av kortmassen - n\u00e5r det kommer til Docsvision, m\u00e5 det g\u00e5 litt tid f\u00f8r dataene vises i lagringen.
\n\u2022 For det tredje, kan vi s\u00f8ke etter kortet ved hjelp av CardID. Dette kan gj\u00f8res med foresp\u00f8rselen: <\/p>\n

http:\/\/localhost:9200\/_search?q=_id=2116C498-9D34-44C9-99B0-CE89465637C9<\/noindex><\/p>\n

Hvis kortet er i lagringen, vil vi se dens 'r\u00e5' data, hvis ikke, vil vi se omtrent et slikt svar:
\n\"Getting
\n<\/p>\n

S\u00f8ke etter kortet i Elasticsearch-noden<\/h4>\n

\nFinne dokumentet etter n\u00f8yaktig samsvar med feltet Beskrivelse:
\nhttp:\/\/localhost:9200\/_search?q=description: Utg\u00e5ende tv1<\/noindex>
\nResultat:
\n \"Getting
\n
\ns\u00f8k etter dokumentet som har 'Inng\u00e5ende' i beskrivelsen
\nhttp:\/\/localhost:9200\/_search?q=description like Inng\u00e5ende<\/noindex>
\nResultat:
\n \"Getting
\n
\nS\u00f8ke etter kortet basert p\u00e5 innholdet i vedlagt fil
\nhttp:\/\/localhost:9200\/_search?q=innhold lik 'AGILE'<\/noindex>
\n resultat:
\n \"Getting
\n
\nLa oss finne alle kort av typen dokument:
\nhttp:\/\/localhost:9200\/_search?q=_type:CardDocument<\/noindex><\/p>\n

eller alle kort av typen oppgave:
\nhttp:\/\/localhost:9200\/_search?q=_type:CardTask<\/noindex><\/p>\n

Ved \u00e5 bruke konstruksjoner og<\/b> og parametere som Elasticsearch gir i JSON, kan vi samle en slik foresp\u00f8rsel:
\nhttp:\/\/localhost:9200\/_search?q=_type:CardTask and Employee_RoomNumber: \u00d8rlandet kontor and Employee_FirstName:Konstantin<\/noindex><\/p>\n

Det vil vise alle kort av typen oppgave, blant brukerne hvis FirstName = Konstantin, og som befinner seg i \u00d8rlandet kontor.
\nI tillegg til LIKE<\/b> det er ogs\u00e5 andre dokumenterte parametere:
\n unlike, fields, docs, content, etc.
\nAlle er beskrevet here<\/a><\/noindex>. <\/p>\n

Det er alt for i dag! <\/p>\n

#<\/b>docsvision #<\/b>docsvisionECM<\/p>\n

Nyttige lenker:<\/p>\n

    \n
  1. Insomnia Rest klient https:\/\/insomnia.rest\/download\/#windows<\/a><\/noindex> <\/li>\n
  2. https:\/\/www.elastic.co\/guide\/en\/elasticsearch\/reference\/current\/docs-get.html<\/a><\/noindex><\/li>\n
  3. https:\/\/www.elastic.co\/guide\/en\/elasticsearch\/reference\/1.4\/_exploring_your_data.html <\/a><\/noindex><\/li>\n
  4. https:\/\/stackoverflow.com\/questions\/50278255\/elasticsearch-backup-on-windows-and-restore-on-linux<\/a><\/noindex> <\/li>\n
  5. https:\/\/z0z0.me\/how-to-create-snapshot-and-restore-snapshot-with-elasticsearch\/<\/a><\/noindex><\/li>\n
  6. https:\/\/www.elastic.co\/guide\/en\/elasticsearch\/reference\/current\/query-dsl-mlt-query.html#_document_input_parameters <\/a><\/noindex><\/li>\n
  7. http:\/\/qaru.site\/questions\/15663281\/elasticsearch-backup-on-windows-and-restore-on-linux<\/a><\/noindex><\/li>\n<\/ol>\n

    Kilde: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    \u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435! \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0434\u0432\u0438\u0436\u043a\u0435 \u043f\u043e\u043b\u043d\u043e\u0442\u0435\u043a\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u043f\u043e\u0438\u0441\u043a\u0430 Elasticsearch (\u0434\u0430\u043b\u0435\u0435 ES), \u0441 \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 Docsvision 5.5. 1. \u0423\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0430 \u0421\u043a\u0430\u0447\u0430\u0442\u044c \u0430\u043a\u0442\u0443\u0430\u043b\u044c\u043d\u0443\u044e \u0432\u0435\u0440\u0441\u0438\u044e \u043c\u043e\u0436\u043d\u043e \u043f\u043e \u0441\u0441\u044b\u043b\u043a\u0435: www.elastic.co\/downloads\/elasticsearch \u0421\u043a\u0440\u0438\u043d\u0448\u043e\u0442 \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u0449\u0438\u043a\u0430 \u043d\u0438\u0436\u0435: 2. \u041f\u0440\u043e\u0432\u0435\u0440\u043a\u0430 \u0440\u0430\u0431\u043e\u0442\u043e\u0441\u043f\u043e\u0441\u043e\u0431\u043d\u043e\u0441\u0442\u0438 \u041f\u043e\u0441\u043b\u0435 \u0437\u0430\u0432\u0435\u0440\u0448\u0435\u043d\u0438\u044f \u0443\u0441\u0442\u0430\u043d\u043e\u0432\u043a\u0438 \u043f\u0435\u0440\u0435\u0439\u0434\u0438\u0442\u0435 \u043f\u043e \u0430\u0434\u0440\u0435\u0441\u0443 http:\/\/localhost:9200\/ \u0414\u043e\u043b\u0436\u043d\u0430 \u043e\u0442\u043e\u0431\u0440\u0430\u0437\u0438\u0442\u044c\u0441\u044f \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0430 \u0441 \u0441\u043e\u0441\u0442\u043e\u044f\u043d\u0438\u0435\u043c ES, \u043f\u0440\u0438\u043c\u0435\u0440 \u043d\u0438\u0436\u0435: \u0415\u0441\u043b\u0438 \u0441\u0442\u0440\u0430\u043d\u0438\u0446\u0430 \u043d\u0435 \u043e\u0442\u043a\u0440\u044b\u043b\u0430\u0441\u044c, \u0443\u0431\u0435\u0434\u0438\u0442\u0435\u0441\u044c, \u0447\u0442\u043e \u0441\u0435\u0440\u0432\u0438\u0441 Elasticsearch […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":24129,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-32312","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47Bli kjent med Elasticsearch steg for steg | ProHoster","description":"Hei! I dag skal vi snakke om fullteksts\u00f8kemotoren Elasticsearch (heretter ES), som plattformen Docsvision 5.5 arbeider med.","canonical_url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/znakomstvo-s-elasticsearch-step-by-step","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"nn_NO","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u0417\u043d\u0430\u043a\u043e\u043c\u0441\u0442\u0432\u043e \u0441 Elasticsearch step by step | ProHoster","og:description":"\u0417\u0434\u0440\u0430\u0432\u0441\u0442\u0432\u0443\u0439\u0442\u0435! \u0421\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u043e\u0433\u043e\u0432\u043e\u0440\u0438\u043c \u043e \u0434\u0432\u0438\u0436\u043a\u0435 \u043f\u043e\u043b\u043d\u043e\u0442\u0435\u043a\u0441\u0442\u043e\u0432\u043e\u0433\u043e \u043f\u043e\u0438\u0441\u043a\u0430 Elasticsearch (\u0434\u0430\u043b\u0435\u0435 ES), \u0441 \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u0440\u0430\u0431\u043e\u0442\u0430\u0435\u0442 \u043f\u043b\u0430\u0442\u0444\u043e\u0440\u043c\u0430 Docsvision 5.5.","og:url":"https:\/\/prohoster.info\/no\/blog\/administrirovanie\/znakomstvo-s-elasticsearch-step-by-step","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-10-31T18:46:17+00:00","article:modified_time":"2019-10-31T18:46:17+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"32312","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-21 10:15:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:02:05","updated":"2026-01-21 10:15:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/32312","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/comments?post=32312"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/posts\/32312\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media\/24129"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/media?parent=32312"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/categories?post=32312"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/no\/wp-json\/wp\/v2\/tags?post=32312"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}