Merge pull request #104937 from HeidiSteen/heidist-monitor

[Azure Cognitive Search] Added links

Author: PRMerger8

articles/search/cognitive-search-custom-skill-interface.md

@@ -8,7 +8,7 @@ author: luiscabrer
 ms.author: luisca
 ms.service: cognitive-search
 ms.topic: conceptual
-ms.date: 11/04/2019
+ms.date: 02/20/2020
 ---
 
 # How to add a custom skill to an Azure Cognitive Search enrichment pipeline
@@ -30,6 +30,8 @@ Custom WebAPI skill endpoints by default timeout if they don't return a response
         "timeout": "PT230S",
 ```
 
+Make sure the URI is secure (HTTPS).
+
 Currently, the only mechanism for interacting with a custom skill is through a Web API interface. The Web API needs must meet the requirements described in this section.
 
 ### 1.  Web API Input Format

articles/search/search-howto-reindex.md

@@ -29,7 +29,7 @@ Drop and recreate an index if any of the following conditions are true.
 | Assign an analyzer to a field | [Analyzers](search-analyzers.md) are defined in an index and then assigned to fields. You can add a new analyzer definition to an index at any time, but you can only *assign* an analyzer when the field is created. This is true for both the **analyzer** and **indexAnalyzer** properties. The **searchAnalyzer** property is an exception (you can assign this property to an existing field). |
 | Update or delete an analyzer definition in an index | You cannot delete or change an existing analyzer configuration (analyzer, tokenizer, token filter, or char filter) in the index unless you rebuild the entire index. |
 | Add a field to a suggester | If a field already exists and you want to add it to a [Suggesters](index-add-suggesters.md) construct, you must rebuild the index. |
-| Delete a field | To physically remove all traces of a field, you have to rebuild the index. When an immediate rebuild is not practical, you can modify application code to disable access to the "deleted" field. Physically, the field definition and contents remain in the index until the next rebuild, when you apply a schema that omits the field in question. |
+| Delete a field | To physically remove all traces of a field, you have to rebuild the index. When an immediate rebuild is not practical, you can modify application code to disable access to the "deleted" field or use the [$select query parameter](search-query-odata-select.md) to choose which fields are represented in the result set. Physically, the field definition and contents remain in the index until the next rebuild, when you apply a schema that omits the field in question. |
 | Switch tiers | If you require more capacity, there is no in-place upgrade in the Azure portal. A new service must be created, and indexes must be built from scratch on the new service. To help automate this process, you can use the **index-backup-restore** sample code in this [Azure Cognitive Search .NET sample repo](https://github.com/Azure-Samples/azure-search-dotnet-samples). This app will back up your index to a series of JSON files, and then recreate the index in a search service you specify.|
 
 ## Update conditions
@@ -48,10 +48,12 @@ When you add a new field, existing indexed documents are given a null value for
 
 ## How to rebuild an index
 
-During development, the index schema changes frequently. You can plan for it by creating indexes that can be deleted, recreated, and reloaded quickly with a small representative data set. 
+During development, the index schema changes frequently. You can plan for it by creating indexes that can be deleted, recreated, and reloaded quickly with a small representative data set.
 
 For applications already in production, we recommend creating a new index that runs side by side an existing index to avoid query downtime. Your application code provides redirection to the new index.
 
+Indexing does not run in the background and the service will balance the additional indexing against ongoing queries. During indexing, you can [monitor query requests](search-monitor-queries.md) in the portal to ensure queries are completing in a timely manner.
+
 1. Determine whether a rebuild is required. If you are just adding fields, or changing some part of the index that is unrelated to fields, you might be able to simply [update the definition](https://docs.microsoft.com/rest/api/searchservice/update-index) without deleting, recreating, and fully reloading it.
 
 1. [Get an index definition](https://docs.microsoft.com/rest/api/searchservice/get-index) in case you need it for future reference.
@@ -75,6 +77,10 @@ When you load the index, each field's inverted index is populated with all of th
 
 You can begin querying an index as soon as the first document is loaded. If you know a document's ID, the [Lookup Document REST API](https://docs.microsoft.com/rest/api/searchservice/lookup-document) returns the specific document. For broader testing, you should wait until the index is fully loaded, and then use queries to verify the context you expect to see.
 
+You can use [Search Explorer](search-explorer.md) or a Web testing tool like [Postman](search-get-started-postman.md) to check for updated content.
+
+If you added or renamed a field, use [$select](search-query-odata-select.md) to return that field: `search=*&$select=document-id,my-new-field,some-old-field&$count=true`
+
 ## See also
 
 + [Indexer overview](search-indexer-overview.md)