snleee opened a new issue, #10039: URL: https://github.com/apache/pinot/issues/10039
We added the upsert primary key can be composite (https://docs.pinot.apache.org/basics/data-import/upsert#define-the-primary-key-in-the-schema). This means that the user will partition data on `hash(colA, colB)`. Pinot's current custom partition based segment assignment & pruning can only be configured per column basis. There's no way to specify the partition based on a composite key. This means that if the upsert is being used and the primary key is defined as composite, there's no way for us to prune the segments on the broker level and this would cause all queries to be routed to all servers. However, we can answer the query by hitting 1 server when there's a filter on the composite primary key. -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
