Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[QUERY] Azure Search Indexers #32942

Closed
ssghoda opened this issue Dec 7, 2022 · 8 comments
Closed

[QUERY] Azure Search Indexers #32942

ssghoda opened this issue Dec 7, 2022 · 8 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Search

Comments

@ssghoda
Copy link

ssghoda commented Dec 7, 2022

Library name and version

Azure.Search.Documents 11.3.0

Query/Question

Can we have following two changes in Azure Search Service environment?

  1. Can we separate Indexer's "Docs Succeeded" column into two separate columns: Docs Updated and Docs Deleted so that we are also able to know how many docs were deleted by Soft Delete policy?
  2. Can we set up a way and register an email address or a distribution list for a Search Service environment so that whenever any Indexer's LastResult gets any Failed docs and/or gets errors, then that email address/distribution list will get an email of Indexer name, Search service name, other Indexer information such as linked Index/Data Source, FailedItemCount and all Error Messages?

Would like to hear thoughts.

Environment

No response

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Dec 7, 2022
@azure-sdk azure-sdk added Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. Search labels Dec 7, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Dec 7, 2022
@jsquire jsquire added needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team and removed needs-team-triage Workflow: This issue needs the team to triage. labels Dec 7, 2022
@jsquire
Copy link
Member

jsquire commented Dec 7, 2022

Thank you for your feedback. Tagging and routing to the team member best able to assist.

@ShivangiReja
Copy link
Member

ShivangiReja commented Dec 7, 2022

This seems like Search portal queries.

Adding @gmndrg from the Search Service team best able to assist you.

@ssghoda
Copy link
Author

ssghoda commented Dec 9, 2022

Regarding point 1 above, my only curiosity was to see the number of docs updated and number of docs deleted (using soft delete policy) separately somehow.

@ssghoda
Copy link
Author

ssghoda commented Dec 21, 2022

Hi @gmndrg @ShivangiReja Any update on this one?

@gmndrg
Copy link

gmndrg commented Dec 26, 2022

Hello @ssghoda Thank you so much for raising the above and apologies for the delay in the response. Most of our team is out on Holidays. Since these are requests for new additions to the current functionality or changes in the way it is deployed today, I have added this to our internal database of new functionality for consideration in future updates. This can't be tracked externally since this is not an issue of the current functionality, but instead a request to be able to support something different. New ideas/requests are discussed periodically based on customer demand and other projects' priority, so we are not able to provide further information regarding the feasibility of implementation at this time.

For request #2 specifically the consideration would be to add indexer errors as part of the indexers Monitoring->Create alert options in the portal so it is a separate signal.

We really appreciate your feedback and your help to make our product better. If you have any other question or concern in the meantime, please let us know. Otherwise, we'll wait a few weeks to close the GitHub issue, since tracked separately. Thanks!

@ssghoda
Copy link
Author

ssghoda commented Aug 3, 2023

Hi @gmndrg I was just following up with you if there was any update on #1 item. It would be great to see how many docs were updated and how many docs were deleted using Soft Delete policy.

@gmndrg
Copy link

gmndrg commented Aug 4, 2023

Hello @ssghoda there is no ETA for this functionality and not planned for this calendar year, unfortunately, due to very high priority projects at this time. We do have it in our backlog to consider in the future if there is more demand for this. I'm sorry there is no other update.

@ShivangiReja
Copy link
Member

This feature request is specifically for the service team, and the SDK can only incorporate features that are supported by the service. If you have any questions related to the search service, please raise an issue at Azure Search · Community. For any SDK-related questions, feel free to create issues on Azure SDK for .NET Github.

@github-actions github-actions bot locked and limited conversation to collaborators Mar 11, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Search
Projects
None yet
Development

No branches or pull requests

5 participants