Hi Team, we have a requirement to have data model for Pinot for real-time dashboard (superset) use-case. There are multiple tables in data lake of transactional nature for different product lines (fact) and there are some dimensions. dashboard requires to source all transactions (all fact table data in single view segregated by product). 2 questions 1. Which one is preferred way - model the data having all product lines in single schema (merging all columns of N tables - one big table having 150+ columns) ? OR to have each product table separate ? for first option, since the sourcing would be via different streams, is "one-table-fed-by-multiple-source-stream" supported in Pinot ? With second option, additional level of joins would be required and in such case, are joins preferred at application side (superset) or within Pinot ? 2. I could see from docs that joins are not supported (neither subqueries) - https://docs.pinot.apache.org/users/user-guide-query/querying-pinot - but in one of the channels I could see broadcast joins are supported in newer version. However, both fact-to-fact join and broadcast joins are required for different use cases.