IgGusev commented on code in PR #6553: URL: https://github.com/apache/ignite-3/pull/6553#discussion_r2343269963
########## docs/_docs/developers-guide/clients/overview.adoc: ########## @@ -105,6 +105,89 @@ 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 condition on colocation columns is required. + +Partition awareness optimization can be applied only if the SQL query contains an equality condition on all colocated columns. The mandatory requirement allows the client to route SQL query to the node where the partition with the data resides. + + +* DML query, which can **not** be rewritten to key-value operation, are not supported yet. + +This statement is more stronger comparing to previous one and require equality condition on all key columns. +Partition awareness work for DML query only if it could be rewritten to a single key-value operation. The explain plan will contains `KeyValueGet` or `KeyValueModify` node in that case. Review Comment: ```suggestion Partition awareness will only work for DML queries if the query can be rewritten to a single key-value operation. The explain plan will contains `KeyValueGet` or `KeyValueModify` node in that case. ``` -- 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]
