Summary of Changes

Hello@wangmm0220, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical race condition within the TMQ snapshot mechanism during data transformation. The changes primarily focus on enhancing thread safety by introducing metadata read locks, standardizing error handling with robust resource cleanup, and removing a function (tqReaderSetVtableInfo) that was likely contributing to the instability or was no longer required in the new, more robust design. These modifications aim to improve the reliability and stability of TMQ snapshot operations.

Highlights

• Race Condition Fix: Implemented read locks (metaRLock/metaULock) for metadata operations during TMQ snapshot creation and retrieval to prevent race conditions, ensuring data consistency in concurrent environments.
• Enhanced Error Handling and Resource Management: Standardized error checking and resource cleanup across several functions usingTSDB_CHECK_NULL,TSDB_CHECK_CODE, andTSDB_CHECK_CONDITION macros, coupled withgoto END blocks. This ensures consistent resource deallocation (e.g.,tDecoderClear,tdbTbcClose,taosArrayDestroy) on all execution paths, improving robustness and preventing memory leaks.
• Removed Obsolete Virtual Table Functionality: Eliminated thetqReaderSetVtableInfo function, its declaration, and its function pointer from theSStoreTqReader struct, along with thecreateStreamVtableBlock function. This streamlines the TMQ snapshot process by removing a component that was likely either problematic or no longer necessary.
• Clarified Resource Ownership: Explicitly transferred ownership of the snapshot context (sContext) increateTmqRawScanOperatorInfo by setting the original handle's context toNULL, preventing potential double-free or use-after-free issues.