You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pinot.apache.org by GitBox <gi...@apache.org> on 2021/12/06 20:58:14 UTC
[GitHub] [pinot] kishoreg commented on pull request #7873: [DO NOT REVIEW] Fix JSON path expressions in SQL queries.
kishoreg commented on pull request #7873:
URL: https://github.com/apache/pinot/pull/7873#issuecomment-987202787
@amrishlal we should reconsider how we are supporting JSON syntax. a.b is a well-known syntax in SQL and it typically refers to tablename.column name. Overloading that to support a nested json path is dangerous and can result in a lot of complications down the road especially when we implement JOIN, UNNEST, etc.
If you really need to support this within LinkedIn, I strongly suggest using some other separator. For e.g. Postgres use "->" and data bricks uses ":"
https://www.postgresql.org/docs/9.3/functions-json.html
--
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: commits-unsubscribe@pinot.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@pinot.apache.org
For additional commands, e-mail: commits-help@pinot.apache.org