UCAST and mapping options #729
Unanswered
KRTone
asked this question in
OPA and Rego
Replies: 1 comment 2 replies
-
|
Yes, the same options are available, but with different keys. To follow along with the example from the docs: With {
"input": {
"favorite": "pineapple"
},
"options": {
"targetSQLTableMappings": {
"ucast": {
"fruits": {
"$self": "fruit",
"name": "display_name",
"price": "price_tag"
},
"price": {
"$table": "fruits"
}
}
}
}
}And this API call, {
"result": {
"query": {
"operator": "or",
"type": "compound",
"value": [
{
"field": "fruit.display_name",
"operator": "eq",
"type": "field",
"value": "pineapple"
},
{
"field": "fruit.price_tag",
"operator": "eq",
"type": "field",
"value": "free"
}
]
}
}
} |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is here any example or option to use
Mapping Table and Column Nameswith UCAST?relate to: https://github.com/orgs/open-policy-agent/discussions/726
Beta Was this translation helpful? Give feedback.
All reactions