https://github.com/heaths/azure-sdk-search-migration
Migration from track 1 to track 2
https://github.com/heaths/azure-sdk-search-migration
Last synced: 8 months ago
JSON representation
Migration from track 1 to track 2
- Host: GitHub
- URL: https://github.com/heaths/azure-sdk-search-migration
- Owner: heaths
- License: mit
- Created: 2020-10-09T02:38:19.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2020-10-09T02:45:25.000Z (over 5 years ago)
- Last Synced: 2025-01-01T10:16:44.624Z (over 1 year ago)
- Language: C#
- Size: 9.77 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE.txt
Awesome Lists containing this project
README
# Azure Cognitive Search Migration Sample
This is a simple sample designed to create indexes, ingest documents, and query documents in Microsoft.Azure.Search,
and query those same documents in Azure.Search.Documents using the following support packages:
* [Microsoft.Azure.Core.NewtonsoftJson](https://www.nuget.org/packages/Microsoft.Azure.Core.NewtonsoftJson)
* [Microsoft.Azure.Core.Spatial](https://www.nuget.org/packages/Microsoft.Azure.Core.Spatial)
* [Microsoft.Azure.Core.Spatial.NewtonsoftJson](https://www.nuget.org/packages/Microsoft.Azure.Core.Spatial.NewtonsoftJson)
## Getting started
To begin, create a new resource group and deployment:
```bash
# Assumes you're already connected
az group create -g my-resourceGroup-name -l westus2
az group deployment create -g my-resourceGroup-name --template-file deployment.json --parameters serviceName=mySearchService
```
That will dump the Search endpoint, admin key, and query key you'll need below (you can also use the `` in both invocations):
```bash
dotnet run -p src/Track1/Track1.csproj -- --endpoint https://mySearchService.search.windows.net --key
dotnet run -p src/Track2/Track2.csproj -- --endpoint https://mySearchService.search.windows.net --key
```
In both invocations you should see output like the following:
```text
https://www.bing.com/maps?cp=46.85287~-121.76044&sp=point.46.85287_-121.76044_Mount%20Rainier
```
It's possible in the first invocation you will not if indexing takes longer than the `--wait` specified (default of 2 seconds), but if you run it again the index won't be created again and you should see the output.
When you're finished, you can simply delete the whole resource group:
```bash
az group delete -g my-resourceGroup-name
# You'll be prompted for confirmation
```