From c000a39d3dc489dca0eb35607ccc44308948997d Mon Sep 17 00:00:00 2001 From: Jeff Zemerick Date: Tue, 13 Apr 2021 14:42:13 -0400 Subject: [PATCH] Fixing delete url. (#361) --- docs/building-features.rst | 2 +- docs/feature-engineering.rst | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/building-features.rst b/docs/building-features.rst index bf020afc..193c2182 100644 --- a/docs/building-features.rst +++ b/docs/building-features.rst @@ -171,7 +171,7 @@ Or filter by prefix in case you have many feature sets:: You can also delete a featureset to start over:: - DELETE _ltr/_featurset/more_movie_features + DELETE _ltr/_featureset/more_movie_features =================== diff --git a/docs/feature-engineering.rst b/docs/feature-engineering.rst index feea53e6..01b46c5e 100644 --- a/docs/feature-engineering.rst +++ b/docs/feature-engineering.rst @@ -7,7 +7,7 @@ You've seen how to add features to feature sets. We want to show you how to addr Getting Raw Term Statistics ====================== -Many learning to rank solutions use raw term statistics in training. For example, the total term frequency for a term, the document frequency, and other statistics. Luckily, Elasticsearch LTR comes with a query primitive, :code:`match_explorer`, that extracts these statistics for you for a set of terms. In it's simplest form, :code:`match_explorer` you specify a statistic you're interested in and a match you'd like to explore. For example:: +Many learning to rank solutions use raw term statistics in training. For example, the total term frequency for a term, the document frequency, and other statistics. Luckily, Elasticsearch LTR comes with a query primitive, :code:`match_explorer`, that extracts these statistics for you for a set of terms. In its simplest form, :code:`match_explorer` lets you specify a statistic you're interested in and a match you'd like to explore. For example:: POST tmdb/_search {