AMashenkov commented on code in PR #6553: URL: https://github.com/apache/ignite-3/pull/6553#discussion_r2329974804
########## docs/_docs/developers-guide/clients/overview.adoc: ########## @@ -105,6 +105,60 @@ For each key that needs updating, the client will get the name of the node holdi NOTE: Partition awareness assumes that the cluster is stable. Client receives information about cluster data assignments in the background, and it may be outdated by the time an update is sent. If it is, nodes will automatically redirect requests to correct nodes until data on the client is updated. +=== Limitations + +* Equality on affinity columns required + Partition awareness works only if the SQL query contains an equality condition on all colocated (affinity) columns. This is required for the client to route SQL query to the node where the partition with the data resides. + +* Explicit transactions are not supported Review Comment: Ok. As we discussed, PA can work * for KV case for DML - covered by the next statement "DML query" * select query over single partition - covered by previous statement "Equality on affinity columns" So, I've just dropped this part -- 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: notifications-unsubscr...@ignite.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
