Supporto della community per Azure
Poni domande, ottieni risposte ed entra in contatto con i tecnici Microsoft e gli esperti della community di Azure
Forum MSDN
Risposta di Microsoft alle domande tecniche su Azure
Azure Search scoring with document in different shards
Forum: Azure Search
Azure Search Service for multiple data source
Forum: Azure Search
Azure search indexing null value after adding a column with data in cosmos db
Forum: Azure Search
Search highlighting works differently on fields with special characters
Forum: Azure Search
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
15
Risposte
Forum: Azure Search
13
Risposte
Forum: Azure Search
13
Risposte
Forum: Azure Search
12
Risposte
Highlights == null in search results??
Forum: Azure Search
StackOverflow
Risposte della community alle domande sullo sviluppo
Serverfault
Risposte della community alle domande sull'amministrazione di Sys/Net
Commenti e suggerimenti per Azure
Hai un'idea o un suggerimento basato sulla tua esperienza con Azure?
How to rename index or indexer? once it is created?
Correctly it is not possible to rename index or indexer once it is created. It is difficult to admin or developer to create index or indexer from the scratch. Please provide some option on indexer should be update. Also provide some option to create indexer using existing one.
More descriptive errors for incorrect datatype
We have been getting the following error when indexing The request is invalid. Details: parameters : An unexpected 'PrimitiveValue' node was found when reading from the JSON reader. A 'StartArray' node was expected It would be nice to know what field it failed on in the response and even better which specific object it was trying to work with and the value on that field.
The azure search seems to lack many fundamental features. Ability to rename the index, clone the index are a few to name.
Allow changing of attributes of a field once data has already been indexed
Common attributes users want to change are type (like int to string), doc-values, stored, indexed etc.
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/
1340
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.
1187
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.
730
Voti
Support schema changes with automated reindexing
Azure Search should support safe schema changes, such as deletion of fields, or maybe even safe field type changes (e.g., int -> string, or string -> string collection)
Storage Optimized tier in the Basic tier pricing range (L0)
For a small business with low traffic and data just over the 2GB limit of the Basic tier it´s really hard to justify to upgrade to standard tier for 3.3x more cost. The performance and scaling for Basic tier is more the enough but the 2GB limit is just to low. It would be nice if you could introduce storage optimized layer(L0) for the lower end of the price range where performance and scaling is not important but the storage amount is more than 2GB.
Support correlated search on complex collections
Now that Azure Search supports complex types, it would be useful to be able to combine full-text search and strict Boolean filters when querying over complex collections. Currently this is not possible -- search.ismatch()/ismatchscoring() are not allowed in lambda expressions, and using sub-fields of complex collections in full Lucene queries has uncorrelated semantics. For example, if you want to search for hotels that have deluxe rooms with city views, none of these gives you exactly what you want: search=Rooms/Description:(city views) AND Rooms/Type:(Deluxe Room) search=Rooms/Description:(city views)&$filter=Rooms/any(room: room/Type eq 'Deluxe Room') $filter=search.ismatchscoring('city views') and Rooms/any(room: room/Type eq 'Deluxe Room') Instead, what you'd ideally want is something like this (exact syntax TBD): $filter=Rooms/any(room: search.ismatch('city views', room/Description) and room/Type eq 'Deluxe Room')
MicrosoftLanguageStemmingTokenizer cannot process word 'F#' correctly
'F#' is a well-known programming language, but if you tokenize sentence contains 'F#' with "en.microsoft" analyzer, it will be omitted. However, 'C#' works fine and does not have such issue.
How to rename index or indexer? once it is created?
Correctly it is not possible to rename index or indexer once it is created. It is difficult to admin or developer to create index or indexer from the scratch. Please provide some option on indexer should be update. Also provide some option to create indexer using existing one.
Compila un ticket di supporto
Crea un evento imprevistoInvia un tweet ad @AzureSupport
Connettiti su TwitterAiutaci a migliorare. Questa pagina è utile?