Package com.qfs.logging
Class MessagesCSV
java.lang.Object
com.qfs.logging.MessagesCSV
MessagesCSV.
Messages used by the various implementation classes of the messaging-csv project. This includes definitions, log and exception messages.
- Author:
- ActiveViam
-
Field Summary
FieldsModifier and TypeFieldDescriptionstatic final StringBad header in block.static final StringFile prefix is greater than 155 characters.static final StringFile name is greater than 100 characters.static final StringCharset is undefined.static final StringTarBuffer.closeBuffer().static final StringException while translating column {0} with parser {1} in file {2}.static final StringThe parsing of line #{0} failed in source: {1}, text: {2}.static final StringTarBuffer.flushBlock() called.static final StringReadBlock: INCOMPLETE READ.static final StringRecord has length with offset which is less than the record size of.static final StringRecord to write has length which is not the record size of.static final StringSomething went wrong when reading the header.static final StringHeaders are not the same, verify header of file.static final StringThe field parser plugin has no value registered for type {0}.static final String{0}: Processing of workload #{1} completed in {2}.static final StringThe parsing of {0} stopped because channel is closed.static final StringPROCESS_WORKLOAD.static final StringREAD EOF RECORD.static final StringREAD NULL RECORD.static final StringReading (via skip) from an output buffer.static final StringTarInputStream: SET CURRENTRY.static final StringTarInputStream: SKIP currENTRY.static final StringSkipRecord: recIdx and blkIdx.static final StringUnexpected EOF with bytes unread.static final StringWriteRecord: recIdx and blkIdx.static final StringWriting to an input buffer.static final StringWrong Header Configuration : Column order length is not the same as the column order type". -
Constructor Summary
Constructors -
Method Summary
-
Field Details
-
PROCESS_WORKLOAD
PROCESS_WORKLOAD.- See Also:
-
OPERATION_COMPLETE
{0}: Processing of workload #{1} completed in {2}. {3} parsed into {4} lines ({5} records published). Average throughput: {6}/s, {7} lines parsed/s, {8} published records/s.- See Also:
-
CHARSET_UNDEFINED
Charset is undefined. Automatically switching to default Charset ({0}). Available Charset are : {1}.- See Also:
-
EXC_TRANSLATING_COL
Exception while translating column {0} with parser {1} in file {2}. Parsed text was \"{3}\".- See Also:
-
EXC_TRANSLATING_LINE
The parsing of line #{0} failed in source: {1}, text: {2}.- See Also:
-
NO_VALUE_REGISTERED_FOR_TYPE
The field parser plugin has no value registered for type {0}.- See Also:
-
READING_VIA_SKIP
Reading (via skip) from an output buffer.- See Also:
-
SKIP_RECORD
SkipRecord: recIdx and blkIdx.- See Also:
-
INCOMPLETE_READ
ReadBlock: INCOMPLETE READ.- See Also:
-
WRITE_RECORD
WriteRecord: recIdx and blkIdx.- See Also:
-
WRITING_BUFFER
Writing to an input buffer.- See Also:
-
NO_GOOD_SIZE
Record to write has length which is not the record size of.- See Also:
-
LESS_SIZE
Record has length with offset which is less than the record size of.- See Also:
-
FLUSHBLOCK
TarBuffer.flushBlock() called.- See Also:
-
CLOSE_BUFFER
TarBuffer.closeBuffer().- See Also:
-
BIG_NAME_FILE
File name is greater than 100 characters.- See Also:
-
BIG_FILE_PREFIX
File prefix is greater than 155 characters.- See Also:
-
SKIP_PREFIX
TarInputStream: SKIP currENTRY.- See Also:
-
READ_NULL_RECORD
READ NULL RECORD.- See Also:
-
READ_EOF_RECORD
READ EOF RECORD.- See Also:
-
SET_CURR_ENTRY
TarInputStream: SET CURRENTRY.- See Also:
-
BAD_HEADER
Bad header in block.- See Also:
-
UNEXPECTED_EOF
Unexpected EOF with bytes unread.- See Also:
-
NO_HEADER_READ
Something went wrong when reading the header.- See Also:
-
NO_SAME_HEADER
Headers are not the same, verify header of file.- See Also:
-
WRONG_HEADER
Wrong Header Configuration : Column order length is not the same as the column order type".- See Also:
-
PARSER_TASK_CHANNEL_CLOSED
The parsing of {0} stopped because channel is closed. This is most probably due to an earlier error in the parsing pipeline.- See Also:
-
-
Constructor Details
-
MessagesCSV
public MessagesCSV()
-