PROCTIME()类型的字段血缘关系解析错误

[Mlove9527]

最好将PROCTIME()类型的字段放到最后，不要放到第一个

[HamaWhiteGG]

The solution of PROCTIME() is the same as LOCALTIMESTAMP, it is enhanced in the getColumnOrigins(Calc rel...) method. LOCALTIMESTAMP has been processed, so the lineage of PROCTIME() can be directly parsed out.

But when PROCTIME() is the first field, the obtained blood relationship will be confused. Therefore, add the computeIndexWithOffset method to calculate the correct source table number RelMdColumnOrigins , and this method is called by RelMdColumnOrigins.getColumnOrigins(Calc, RelMetadataQuery, int)

[HamaWhiteGG]

test case:
"CREATE TABLE ST (\n"
+" make_time as PROCTIME(),\n "
+ " a STRING,\n"
+ " b STRING\n"
+ ") WITH (\n"
+ " 'connector' = 'kafka',\n" +
" 'topic' = 'user_behavior',\n" +
" 'properties.bootstrap.servers' = '192.168.24.129:9092',\n" +
" 'properties.group.id' = 'testGroup',\n" +
" 'scan.startup.mode' = 'earliest-offset',\n" +
" 'format' = 'json'"
+ ");\n"
+ "CREATE TABLE TT (\n"
+ " make_time TIMESTAMP(3), \n "
+ " A STRING,\n"
+ " B STRING\n"
+ ") WITH (\n"
+ " 'connector' = 'print'\n"
+ ");\n"
+ "insert into TT(make_time,A,B) select make_time,a,b from ST";