Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.1.0.0-incubating
-
None
Description
In force mode, hawq register error when files in yaml is in disordered. For example, the files order in yaml is as following:
Files: - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/2 size: 250 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/4 size: 250 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/5 size: 258 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/6 size: 270 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/3 size: 258 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW2@/1 size: 228 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW@/2 size: 215 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW@/3 size: 215 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW@/4 size: 220 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_OLD@/1 size: 254 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW@/6 size: 215 - path: /hawq_default/16385/@DATABASE_OID@/@TABLE_OID_NEW@/5 size: 210
After hawq register success, we select data from table and get the error:
ERROR: hdfs file length does not equal to metadata logic length! (cdbdatalocality.c:1102)
Attachments
Issue Links
- relates to
-
HAWQ-991 "HAWQ register" could register tables according to .yml configuration file
- Open
- links to