oscerd commented on PR #16732:
URL: https://github.com/apache/camel/pull/16732#issuecomment-2575286400
> > Looks good, it would be nice if the filter could be a simple string to
be transformed on the POJO while using it, that way it would be easier to use
inline in the endpoint.
>
> @oscerd Sounds like a better option. However, 'filter' is many things.
>
> Example of a JSON format filter
>
> ```
> "filter": {
> "must": [
> {
> "key": "category",
> "match": { "value": "laptop" }
> },
> {
> "key": "price",
> "range": {
> "gt": null,
> "gte": null,
> "lt": null,
> "lte": 1000
> }
> }
> ]
> },
> ```
>
> This is what I can think of:
>
> * Add a simple key/value strings in case we want to use only a single
match.
> * Add two headers, to deal with multiple matches and numeric values: one
expecting a map for the keys/values, and one expecting a range for the values
that are numeric.
>
> WDYT ?
Probably it makes less sense, it's too complex to inline in the endpoint.
Better to stick with the POJO. Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
