Page MenuHomePhabricator

Create a More General Solution for Metadata Merging
Open, MediumPublic

Description

Description

If a function in the orchestrator receives a Z22 and then returns another Z22, it should not discard the metadata associated with the received Z22. Instead, it should intelligently merge that metadata with any metadata that will be produced in the current function.

Desired behavior/Acceptance criteria (returned value, expected error, performance expectations, etc.)

  • ensure that metadata is always merged instead of being discarded

Completion checklist

Details

TitleReferenceAuthorSource BranchDest Branch
Draft: Add ZEnvelopeWrapper with specialized metadata property.repos/abstract-wiki/wikifunctions/function-orchestrator!170apineapine-metadata-2main
Add ZWrapperBase so that setMetadata* functions can handle ZWrappers in addition to bare Z22s.repos/abstract-wiki/wikifunctions/function-schemata!118apineapine-metadata-utilsmain
Customize query in GitLab

Event Timeline

Jdforrester-WMF moved this task from To triage to Backlog on the Abstract Wikipedia team board.

To add to this; a specific example of why this will be helpful can be seen when we are testing out an implementation of a function. E.g. https://www.wikifunctions.org/view/en/Z13453, we click on 'details', we do not see which implementations were run to gather test results; when for this function there is both a JS and Py implementation. As a user, I would want to know which implementation(s) was used

Screenshot 2024-03-19 at 10.25.25 PM.png (470×1 px, 46 KB)
.