Open mikegking opened 1 year ago
Thank you for your feedback! We will review and update as appropriate.
@mikegking Sorry for the late reply. I was able to reproduce the same as described in your feedback. As the next step, we're proceeding to assign this issue to the content author for further review and any update that may be required.
related: #106724 #70450
+1 i ran into this today
I've been experimenting with the use of route parameters as described on this page (Python tab) and it seems to be out of date?
Table binding:
{ "name": "messageJSON", "type": "table", "tableName": "messages", "partitionKey": "message", "rowKey": "{id}", "connection": "AzureWebJobsStorage", "direction": "in" },
Attributes partitionKey and rowKey do not seem to be used and all Table entities are returned. {id} is ignored as is partitionKey. Using filter works ok:
{ "scriptFile": "__init__.py", "bindings": [ { "type": "http", "direction": "out", "name": "$return" }, { "type": "table", "direction": "in", "name": "messageJSON", "tableName": "messages", "filter": "PartitionKey eq 'Customer' and RowKey eq '{id}'", "connection": "AzureWebJobsStorage" }, { "authLevel": "function", "type": "httpTrigger", "direction": "in", "name": "req", "methods": ["get"], "route": "customer/{id}" } ] }
This has the desired effect (a single Entity is returned) and seems to be equivalent. Could it perhaps be filter has been added since this config was written? I am using this with Azure Table Storage.
Azure Functions Core Tools Core Tools Version: 4.0.5030 Commit hash: N/A (64-bit) Function Runtime Version: 4.15.2.20177
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.