microsoft / microsoft/onnxruntime
OrtCustomOp does not support all types of attributes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 21.9k
- Forks
- 4.2k
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 184
Description
**Is your feature request related to a problem? Please describe.**
Custom operator cannot be defined with any type of attribute. string is supported and we could serialize every parameter into a string but it make the API more complicated.
**System information**
- ONNX Runtime version: 1.6.0
**Describe the solution you'd like**
Support vector attributes in OrtCustomOp.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the OrtCustomOp implementation and the existing handling for string attributes. Compare that path with the supported ONNX attribute types and identify the custom-operator tests that cover attribute serialization. Done means vector attributes can be passed without converting every parameter to a string and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100