[ https://issues.apache.org/jira/browse/IGNITE-10160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yury Gerzhedovich updated IGNITE-10160: --------------------------------------- Description: Each of execution query should have unique identifier for whole cluster. It should be \{node_order_id}{X}\{node_qry_cntr} where node_order_id - node order id where query was started. X - letter 'X' used as separator. node_qry_cntr - local node query counter. both node_order_id and node_qry_cntr encoded to HEX. Example of such id - a1fXbc71d was:Each of execution query should have unique identifier for whole cluster. It could be an initial node UUID + sequentially growing number of an executing queries on the node. As example: *b3c0624a-122c-46ea-9d65-67b56df00001* and *341*. This query id should be used for all of the query parts executed on other nodes. > Add unique identifier for all SQL queries > ----------------------------------------- > > Key: IGNITE-10160 > URL: https://issues.apache.org/jira/browse/IGNITE-10160 > Project: Ignite > Issue Type: Task > Components: sql > Reporter: Yury Gerzhedovich > Assignee: Yury Gerzhedovich > Priority: Major > Labels: iep-29 > Fix For: 2.8 > > > Each of execution query should have unique identifier for whole cluster. It > should be \{node_order_id}{X}\{node_qry_cntr} > where > node_order_id - node order id where query was started. > X - letter 'X' used as separator. > node_qry_cntr - local node query counter. > > both node_order_id and node_qry_cntr encoded to HEX. > > Example of such id - a1fXbc71d -- This message was sent by Atlassian JIRA (v7.6.3#76005)