Breaking Change Introduced in v1.2.1.63 (Worked Fine Until v1.2.1.62) #329
Unanswered
GovardhananAlagirisamy
asked this question in
Q&A
Replies: 2 comments 1 reply
-
|
pls try |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Pls use Let me know. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
After upgrading from v1.2.1.48 to v1.2.1.63, I noticed that the following input fails to parse correctly:
Using
|as the delimiter, and focusing only on the field:In v1.2.1.62 and earlier, it worked fine.
In v1.2.1.63 and later, the presence of the
"inside the unquoted field causes issues.Reader Configuration:
Request:
Was this change intentional in v1.2.1.63?
Is there a config option to allow unquoted fields to contain
"like before?@Cinchoo, could you help with this? I appreciate any help you can give me.
Beta Was this translation helpful? Give feedback.
All reactions