terrymanu commented on issue #28167:
URL:
https://github.com/apache/shardingsphere/issues/28167#issuecomment-3640756552
## Understanding
- You want ShardingSphere (Proxy or JDBC) to work correctly with the
PostgreSQL jsonb containment operator @>, and it’s unclear whether the issue is
in parsing, routing, or execution.
## Root Cause
- The issue currently lacks reproduction details, so we can’t tell if it’s
a usage/configuration gap or a product defect. The PostgreSQL grammar already
includes @>, but correct routing/rewriting depends on the actual SQL, sharding
rules, and parameters; without those,
the root cause cannot be pinned down.
## Analysis
- Syntax support: PostgreSQL’s @> jsonb containment operator is standard
(official doc: https://www.postgresql.org/docs/current/functions-json.html).
ShardingSphere’s PostgreSQL grammar includes this symbol, so pure parsing
should generally succeed.
- Possible factors (need specifics to confirm):
- Deployment: Proxy vs JDBC, ShardingSphere version, PostgreSQL
version.
- SQL shape: whether @> is applied to a sharding key,
parameterization, casts, or JSON literals.
- Sharding config: table DDL (jsonb column) and sharding rule; if @>
involves the sharding key, the rule must derive routing correctly.
- Symptom type: parse error, empty routing, rewrite anomaly, or
execution mismatch versus direct PostgreSQL.
- If direct PostgreSQL works but ShardingSphere fails, we need the above
context to decide if this is a feature gap or a usage/config issue.
## Conclusion
- More info is needed to determine whether this is a usage issue or a
defect. Please share:
1. ShardingSphere version and deployment mode (Proxy/JDBC);
2. PostgreSQL version;
3. Table DDL (including the jsonb column) and sharding rule
configuration;
4. The exact SQL you run (with parameters/JSON content) and the result
when run directly against PostgreSQL;
5. The specific error/abnormal behavior in ShardingSphere
(parse/routing/rewrite/execute logs or messages).
- With these details, I can help pinpoint the cause and provide a concrete
recommendation.
--
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]
