Azure Search
Azure Search is a search-as-a-service solution that allows developers to incorporate a sophisticated search experience into web and mobile applications without having to worry about the complexities of full-text search and without having to deploy, maintain or manage any infrastructure
-
Support for Dictionary DataType
Dictionary datatype is very common. Often, we'd like to store our data as a dictionary. Currently, I serialize and store it as a string. It'd be great if the dictionary type is supported.
274 votes -
Add support for inheritance ($type)
Sometimes we have inheritance in our database tables. In my case, I have inheritance mapped to a table using EF Code First, and the table contains a generated column, [Discriminator], that tells the EF which type should be activated when fetching the entity.
There should be a way for Azure Search (a field transformation function maybe) to map discriminators in the database to fully qualified non-searchable $type fields in the indexes, in order for the SDK to be able to deserialize the types correctly using the TypeNameHandling setting of the Json.net serializer.
40 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Vinod
Azure Search Product Team -
Proper support for DateTimeOffset
Search should ingest and support a true implementation of DateTimeOffset. The current implementation merely converts an incoming DateTimeOffset to a DateTime in UTC, subsequently resulting in the loss of data, as the original offset can no longer be retrieved. The currently implementation necessitates persisting a related sidecar attribute of the original offset and subsequently requires the consumer to convert and rehydrate the property. This is exceptionally tedious, especially for use cases with several dozen DateTimeOffset attributes with varying offsets.
27 votesWe really like this idea. Thank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Mike Carter
Azure Cognitive Search Product Team -
Support Edm.Date type
Azure Search only supports Edm.DateTimeOffset. This is great for timestamps and other point-in-time data. However, it's horrible for things like birthdays, invoice dates, and other whole-date scenarios.
1976-08-27 is very different than 1976-08-27T00:00:00Z.
Edm.Date was added to OData v4 for this exact reason. It should be a primitive type in Azure Search as well.
17 votesThank you for your feedback. We’re considering this for a future release of Azure Search.
Thanks,
Elad
Azure Search Product Team -
Support multi-fields
It would be nice to have one data value analyzed multiple different ways.
https://www.elastic.co/guide/en/elasticsearch/reference/current/multi-fields.html
6 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Vinod
Azure Search Product Team -
Add combo field support
Add ability to combine existing fields in index.
Similar to SQL example below:
ALTER TABLE SearchData ADD
Combo As
[Name] + char(32) +
[Description] + char(32) +
[MetaData] + char(32) +
[OwnerData] + char(32) +
[CategoryData] + char(32) PERSISTEDExample in Azure Search:
e.g.
idx.FirstName = "John" Edm.String
idx.LastName = "Doe" Edm.String
idx.Name = "John Doe"; (Combo, of Firstname and lastname) (Internally could act as Collection(Edm.String) ??)3 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
Thanks,
Liam
Azure Search Product Team -
Support spatial data with flat projections
Today Search supports 2d sphere lat/long spatial data. I would like to see support for flat projections, points, polygons and lines.
3 votesThank you for your feedback. While it is unlikely we’ll address this suggestion in the near future, we’ll reassess based on the number of votes it receives.
With the private preview of complex types (api version 2018-11-11-Preview) you will be able to store a line and leverage it for geospatial queries.
Thanks,
Vinod
Azure Search Product Team -
Support additional file formats
Additional mail formats such as .PST, EDRM, Mbox
AutoCAD
DICOM3 votes -
Support to calculated fields
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
3 votes
- Don't see your idea?