Project: datamanagement
Issue DM-5314: Implement unique query-id generation
There are currently two separate query IDs defined for queries in czar code: - "user query ID" - defined in {{Czar::submitQuery()}}, used for constructing table names for result table and message table - "QMeta query ID" - ID obtained from QMeta after registering the query (by {{UserQuerySelect::_qMetaRegister()}}) Currently user query ID is used by the rest of the czar code to track the processing of this query, QMeta ID is not used yet for anything except QMeta registration and updates. QMeta ID will be used for async query identification and there is no actual reason to keep two IDs around, so we should replace user query ID with the QMeta-generated one everywhere. One minor issue is that currently message table name is built and table is locked before we register query in QMeta. Need to understand it and see if we can reverse that logic.
Story points: 4