Azure / Azure/azure-functions-host
[BUG] function.json, error 500 on "filter": "RowKey eq '{Request.Query.Name}'",
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
# Issue Transfer
This issue has been transferred from the Azure SDK for .NET repository, [#41640](https://github.com/Azure/azure-sdk-for-net/issues/41640).
**Azure Functions Team:** This inquiry appears to be asking the question "can the host inject a placeholder based on the current request into a setting value?" This does not appear directly related to the Table extensions package.
### Please be aware that @slashd is the author of the original issue and include them for any questions or replies.
## Details
### Library name and version
Azure Functions Core Tools 4.0.5455
### Describe the bug
VSCode > Azure Functions > PowerShell 7.2 > httpTrigger
In function.json add a table binding:
this works:
```json
{
"bindings": [
{
"authLevel": "anonymous",
"type": "httpTrigger",
"direction": "in",
"name": "Request",
"methods": [
"get",
"post"
]
},
{
"type": "http",
"direction": "out",
"name": "Response"
},
{
"name": "HeroEntity",
"type": "table",
"tableName": "Hots",
"partitionKey": "Hots",
"filter": "RowKey eq 'Raynor'",
"direction": "in"
}
]
}
```
Error 500 when i change the filter to get the parameter from the querystring:
```json
"filter": "RowKey eq '{Request.Query.Name}'",
```
I tried it with both:
http://localhost:7071/api/GetHots?Name=Raynor
http://localhost:7071/api/GetHots
### Expected behavior
Not getting an error 500...
### Actual behavior
Error 500
### Reproduction Steps
See 'Describe the bug'
### Environment
W11, VSCode, Azure Functions, PowerShell 7.2, Azure Functions Core Tools 4.0.5455
Contributor guide
Research direction
Start with the function.json table binding and the Azure Functions host's handling of binding expressions, then reproduce the request at /api/GetHots with and without the Name query parameter. Determine whether the query-bound filter is supported; done means the behavior is fixed or the limitation and expected configuration are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, powershell
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100