docs: add description for how subtable name is generated

docs/en/14-reference/13-schemaless/13-schemaless.md

@@ -66,6 +66,7 @@ Schemaless writes process row data according to the following principles.
 
 Note that tag_key1, tag_key2 are not the original order of the tags entered by the user but the result of using the tag names in ascending order of the strings. Therefore, tag_key1 is not the first tag entered in the line protocol.
 The string's MD5 hash value "md5_val" is calculated after the ranking is completed. The calculation result is then combined with the string to generate the table name: "t_md5_val". "t*" is a fixed prefix that every table generated by this mapping relationship has.
+Please refer following link for the details of subtable name implementation rules：[subtable name code implementation](https://github.com/taosdata/TDengine/blob/06e05dfdf9c394e8ad5dd2ad4a54de53ea4e93f5/src/client/src/tscParseLineProtocol.c#L153-L188).
 
 2. If the super table obtained by parsing the line protocol does not exist, this super table is created.
 If the subtable obtained by the parse line protocol does not exist, Schemaless creates the sub-table according to the subtable name determined in steps 1 or 2.

docs/zh/14-reference/13-schemaless/13-schemaless.md

@@ -70,6 +70,7 @@ st,t1=3,t2=4,t3=t3 c1=3i64,c3="passit",c2=false,c4=4f64 1626006833639000000
 
 需要注意的是，这里的 tag_key1, tag_key2 并不是用户输入的标签的原始顺序，而是使用了标签名称按照字符串升序排列后的结果。所以，tag_key1 并不是在行协议中输入的第一个标签。
 排列完成以后计算该字符串的 MD5 散列值 "md5_val"。然后将计算的结果与字符串组合生成表名：“t_md5_val”。其中的 “t\*” 是固定的前缀，每个通过该映射关系自动生成的表都具有该前缀。
+子表名具体实现规则可以参考：[子表名生成规则代码实现](https://github.com/taosdata/TDengine/blob/06e05dfdf9c394e8ad5dd2ad4a54de53ea4e93f5/src/client/src/tscParseLineProtocol.c#L153-L188)。
 
 2. 如果解析行协议获得的超级表不存在，则会创建这个超级表。
 3. 如果解析行协议获得子表不存在，则 Schemaless 会按照步骤 1 或 2 确定的子表名来创建子表。