diogobaeder opened a new issue, #8586: URL: https://github.com/apache/pinot/issues/8586
Hi folks, There's a few issues in the documentation for handling JSON columns. In the documentation for handling JSON columns with JSON indexing, the configuration there is missing a top-level `ingestionConfig` configuration on the table config, and only inside `ingestionConfig` is where we should put `transformConfigs`. Also, that configuration part in the docs could be better formatted to have more consistent indentation. And I also think the documentation should be using the `JSON` column type, not `STRING`; Even though both might work, using `JSON` is more consistent and is actually the type being used in the file that contains the "full spec": https://github.com/apache/pinot/blob/master/pinot-tools/src/main/resources/examples/stream/meetupRsvp/json_meetupRsvp_schema.json One more thing that would be worth mentioning in the documentation is that the column name in the source data that is used for ingestion has to be different from the destination column name; For example, if I want column `foo` in Pinot as JSON, then in my source I should use something different like `foo_source`. Ideally though, it would be awesome if Pinot could just take care of such fields without us having to have different names and having to define a transformation function - Pinot could use `jsonFormat` by default on the fields that use `JSON` type, just to reduce configuration boilerplate. Thanks! Diogo -- 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-unsubscr...@pinot.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@pinot.apache.org For additional commands, e-mail: commits-h...@pinot.apache.org
