Azure / Azure/azure-kusto-trender
SearchTagsAtPath not working
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 18
- Avg merge
- 6d 15h
- Merged PRs (30d)
- 2
Description
In ADXTrenderClient there's a function searchTagsAtPath which does a query to ADX with a function called SearchTagsAtPath_Henning, which is not found in the trender-schema.kql which is supposed to create all the necessary functions in the ADX. It seems to me that I can just redirect those calls to getChildrenTags function in ADXTrenderClient instead, which is identical except for the function it uses in ADX. Why are these two in separate logic paths in the HierarchyDelegate? More over there's identical "else if" branches there that call the searchTagsAtPath.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing searchTagsAtPath and getChildrenTags in ADXTrenderClient, then inspect the corresponding branches in HierarchyDelegate and the function definitions in trender-schema.kql. Confirm whether SearchTagsAtPath_Henning is intentionally distinct or missing, and make the ADX query paths consistent with the schema before verifying the affected hierarchy behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- backend-api-design, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100