1. Do all product lines share the same table schema or have overlap or are mutually exclusive? Also is there a way to segregate tables in a way that reduces number of dimensions and does not require joins? If not, then single table would also work. 2. Joins is being worked on right now, the v2 engine is available as alpha

Thanks @Mayank. Yes, all product lines have overlapping schema (~ 50% common). we can merge them into single schema. but in such case, should all transactions (pertaining to all product lines) be sourced via single Kafka topic ? Or different topics can contribute to single table ? We would try to keep dimensions low in number and volume both. As I could see UDF usage for lookup on dimension is available.

Currently, one Pinot table consumes from a single Kafka topic, so you’ll have to pump all events into a single one

Sure @Mayank, additionally one query on applying updates to the data in Pinot there are updates to transaction (frequent and 3x of insert count) mostly on status and we have 2 approaches 1. to keep Pinot fact table in append-only mode (insert only). This will push down the 'latest' fetch logic onto Pinot. will it impact performance ? How to handle 'latest only' record availability in Pinot which is primary use-case ? 2. to update the table as and when updates arrive. Is Pinot supporting updates ?

Have you looked at upsert capability in Pinot? Apart from that, there is lastWithTime udf or similar name that returns the latest record