How can we improve Azure Search?

Allow custom defined Field Mapping Function

Currently when defining the indexers, one can specify the field mappings from source to target fields. Only a limited set of functions such as Extract token at position etc are supported. It would be desirable to support Func syntax such that each row is passed onto the func which then decide the target field value based on developer defined logic in func.

Eg: we have a cosmo db source and a azure table storage data source. The partition key for cosmo db collection is combination of tenantId:studentId for efficient read/writes across partitions based on our data. The azure table storage partition key is tenant id and student id is the row key. Some business function specific details about the student are stored in table storage and are managed by different microservice that is NOT responsible for the central student service (uses cosmo db).

There is a special field 'Key' that ATS Data source provides in azure search which is PKRK combination. But as in cosmo db we have : in those we need some way to make sure the index row that is updated is same so that search on combined set of fields from multiple sources can be performed.

6 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Ramandeep AroraRamandeep Arora shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base