Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
8.4.x
-
None
Description
The following error’s being thrown on line 518 of BinaryRecordReader
2021-10-14 16:20:53 ERROR GenericQuery:103 - LocalId:GNhBnBbb1qJDrLFfG7Z2Fn ERROR(120) Exception:Failed to acquire file access or retrieve meta info for: 'thor_data400::key::insuranceheader_xlink::20210723_java::did::word::fname' with error: PartitionProcessor: Error while attempting to read TLK: Fatal read error: Failed to parse next record: Error while parsing field: initialchar of type: STRING: : Failure to read hpcc file>thor_data400::key::insuranceheader_xlink::20210723_java::did::word::fname
org.hpccsystems.commons.errors.HpccFileException: Failed to acquire file access or retrieve meta info for: 'thor_data400::key::insuranceheader_xlink::20210723_java::did::word::fname' with error: PartitionProcessor: Error while attempting to read TLK: Fatal read error: Failed to parse next record: Error while parsing field: initialchar of type: STRING:
at org.hpccsystems.dfs.client.HPCCFile.createDataParts(HPCCFile.java:438) ~[dfsclient-8.4.0-2.jar:?]
at org.hpccsystems.dfs.client.HPCCFile.getRecordDefinition(HPCCFile.java:483) ~[dfsclient-8.4.0-2.jar:?]
You can recreate it with the following java code:
HPCCFile file = new HPCCFile("thor_data400::key::insuranceheader_xlink::20210723_java::did::word::fname",
https://alpha_dev_thor_esp.risk.regn.net:18010/ , "userame","password!");
FieldDef rm=file.getRecordDefinition();
The problem occurs when parsing the second field (initialchar) of the 401^st^ record, consistently. When I debug into it, the first field (fname) for this record is showing up bizarrely as “ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ”.
This issue is impacting the MCI product's development which depends on streaming these indexes out of alpha-dev; they will need it resolved before they can continue work.