It sucks that if I have more than 3 indexes I have to create a paid tier for development. We do not need performance or size. Just more index to simulate the production environment which contains more indexes.770 votes
Beeing able to utilize LINQ in order to search in indexes just like LINQ2SQL looks like. The codebase would be simple to write, simple to read and analogous to LINQ2SQL query. Linq2Lucene project (https://github.com/themotleyfool/Lucene.Net.Linq) defines a very nice interface for fast time to market.
The Database context would be replaced with a Azure Search context that would wrap all REST based and JSON making the developer only focusing on the most important, Search.
Similar, delete and updates would be handled the same way a Linq2SQL handles it in the codebase.
Time2Market for Azure Searchbased inventions would be furious.344 votes
For the same reason that it's good to have the script options in SSMS, it would be great to have a REST and/or PowerShell equivalent for options in the Azure portal. (It would be REALLY good to have that right across the portal but your team could take the lead on it :-))49 votes
Management API is documented here: https://msdn.microsoft.com/en-us/library/azure/dn832684.aspx
We haven’t started working on PowerShell CmdLets and it isn’t on our roadmap yet. If you’d like to provision and manage Search services using PowerShell, it is possible using Azure Resource Manager PowerShell CmdLets. We’ve documented how to with this document https://azure.microsoft.com/en-us/documentation/articles/search-manage-powershell/
If native Azure Search PowerShell CmdLets are important to you, please let us know in the comments and keep the votes coming. Thanks!
Provide a Ruby SDK for Azure Search that covers the same functionality as the .NET SDK.14 votes
Provide a PHP SDK for Azure Search that covers the same functionality as the .NET SDK.8 votes
- Don't see your idea?