Supporto della community per Azure
Poni domande, ottieni risposte ed entra in contatto con i tecnici Microsoft e gli esperti della community di Azure
Introduzione di Azure on Q&A
Trova le risposte alle tue domande tecniche sui prodotti e i servizi di Azure. Interagisci con gli esperti di Microsoft e della community, condividi feedback e impara dagli altri utenti. Azure on Q&A, nel sito Microsoft Q&A, sostituirà il forum MSDN. Puoi ancora esplorare gli archivi del forum.
Archivio del forum MSDN
Risposte di Microsoft e della community a domande tecniche precedenti su Azure
9
Voti
Forum: Azure Search
6
Voti
Unable to Install SDK 2.9 from Web Platform Installer and VS2015
Forum: Azure Search
6
Voti
Handling scoring and priority with search across multiple indexes
Forum: Azure Search
4
Voti
Best way to diagnose data quantity mismatch
Forum: Azure Search
StackOverflow
Risposte della community alle domande sullo sviluppo
Serverfault
Risposte della community alle domande sull'amministrazione di Sys/Net
Feedback su Azure
Pubblica idee o suggerimenti basati sulla tua esperienza con Azure
This is a user suggestion to allow for metadata that disappeared from the original document to be also removed from the indexed document:[Azure Search] Remove field value from index when not present in data source · Issue #6761 · Azure/azure-sdk-for-net (github.com)https://github.com/Azure/azure-sdk-for-net/issues/6761Currently we always do updates in mergeOrUpload mode:Add, Update or Delete Documents (Azure Cognitive Search REST API) | Microsoft Docshttps://docs.microsoft.com/en-us/rest/api/searchservice/addupdate-or-delete-documents
Hi there,It would be important to have a way to use calculated fields that we could use basic functions to it and also use existing fields' values to calculate the value of the new field. So, we could reside the logic at the index level, instead of the code + SDK and import clients.Thank you
Constant score operator ^=1.0 or similar
As described here:https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html#TheStandardQueryParser-ConstantScorewith_So if you search for:"my term"^=1.0The score is going to be either 1.0 or 0.
1735
Voti
Allow to upgrade the pricing tier
Everywhere in the portal, we can increase/decrease the pricing tier based on our needs.With the introduction of Azure Search Basic, we need a way to upgrade to the next level (Standard) when we are close to reach the service limits.The only way today to go around this is to bring the index down and create another one.
1421
Voti
Provide a local emulator or increase the number of indexes on the free tier for development use
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.
1344
Voti
Modelling Complex Types in Indexes
When modelling an index the data types are restrictive. There are simple types and collections. There is nothing that allows us to model complex types e.g...."name": {"first": "Ericka","last": "Banks"},......The oData spec allows for complex types http://www.odata.org/documentation/odata-version-2-0/overview/
930
Voti
Support case-insensitive comparison in filters
Searching with text= performs a case-insensitive search. However, testing string fields in filters is case-sensitive. There should be a way to do a case-insensitive string comparison in filter expressions.
Constant score operator ^=1.0 or similar
As described here:https://lucene.apache.org/solr/guide/6_6/the-standard-query-parser.html#TheStandardQueryParser-ConstantScorewith_So if you search for:"my term"^=1.0The score is going to be either 1.0 or 0.
Return tag matched on along with asset
We would like to implement UI to be more transparent to users about the tag which the search term matched on. This is important to avoid PR risks with inferences on content and search term with fuzzy search.Currently, to enable this scenario, we would need to do a lot more processing that Azure Search is already doing. Additionally, ours solution would not be as intelligent and prone to error. Requesting the ability for Azure Search to also return the matched tag with the asset.
Auto-indexing of Power BI datasets
there is some integration of Power BI and Cognitive Services already: https://docs.microsoft.com/en-us/azure/cognitive-services/Text-Analytics/Tutorials/tutorial-power-bi-key-phrases. looking to extend this further. there are A TON of use cases for better text search / cog search in Power BI
Hi,I would like to create index so that I will be able to search on csv/non-csv blob content. For csv blob the content is coming as empty always. Can anyone help.