[KYLIN-5603] After the V2 dictionary is automatically upgraded to the V3 dictionary, the dictionary data is abnormal, resulting in incorrect query results

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0-alpha
• Fix Version/s: 5.0-beta
• Component/s: Job Engine
• Assignee: huangsheng
• Reporter: huangsheng
• Created: 03/Jul/23 07:00
• Updated: 06/Jul/23 06:18
• Resolved: 06/Jul/23 06:18

Description

After v2 upgrades the v3 dictionary, if v2 and v3 are mixed, the query result is incorrect

Root Cause

The project opens the v3 dictionary construction, but when the v3 dictionary construction reads the v2 dictionary, the db name is not included in the path, so the v2 dictionary will not be read, causing the v2 upgrade and the v3 dictionary conversion step to be skipped directly, and v3 is equivalent to recoding. Therefore, the v2 upgrade v3 dictionary must not be available, and the encoding is disordered.