You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am facing issue while parsing the records that has CR in between the fields.
Example:
"18","Agent System Review","To identify the calls where the agents have taken time to research or check information in the system tools or CRM.^M
","b5b553d2-81ab-4ec3-83e0-71ae3cf4afab","1","8.63","9.58","10.49","70","NAEnglish TeleUniversal 8.0.1.91034"
There is a CR (^M) after CRM which causes the serde to consider it as a new record, even though this should one record. Is there a way these kind of input data issue can be handled in this serde?
The text was updated successfully, but these errors were encountered:
same here.
It looks like the issue is due to the InputFormat (TextInputFormat) splitting the text into records everytime a linebreak exist (it doesnt care whether it's between quotes or not)
The serde gets those partial records as input and cannot recreate your original record...
same here.
It looks like the issue is due to the InputFormat (TextInputFormat)
splitting the text into records everytime a linebreak exist (it doesnt care
whether it's between quotes or not)
The serde gets those partial records as input and cannot recreate your
original record...
—
Reply to this email directly or view it on GitHub #18 (comment).
I am facing issue while parsing the records that has CR in between the fields.
Example:
"18","Agent System Review","To identify the calls where the agents have taken time to research or check information in the system tools or CRM.^M
","b5b553d2-81ab-4ec3-83e0-71ae3cf4afab","1","8.63","9.58","10.49","70","NAEnglish TeleUniversal 8.0.1.91034"
There is a CR (^M) after CRM which causes the serde to consider it as a new record, even though this should one record. Is there a way these kind of input data issue can be handled in this serde?
The text was updated successfully, but these errors were encountered: