Ian OLeary
08/28/2024, 7:40 PMError parsing JSON: UTF-16 single low surrogate: 0xdc81
when trying to run my mssql tap. Has anyone encountered this?haleemur_ali
08/28/2024, 8:08 PMIan OLeary
08/29/2024, 2:13 PMIan OLeary
08/29/2024, 2:18 PMIan OLeary
08/29/2024, 7:16 PMhaleemur_ali
08/29/2024, 7:19 PMhaleemur_ali
08/29/2024, 7:19 PMIan OLeary
08/29/2024, 7:19 PMIan OLeary
08/29/2024, 7:23 PMhaleemur_ali
08/29/2024, 8:07 PMutf-8 and utf16 should both be able to represent the same characters (unicode). would you be able to create a bug report documenting this behaviour so the plugin maintainers can reproduce it (sample create table statement with sample data)Copy codea PO number was a bunch of Japanese text for some reason which was too big for UTF-8
Ian OLeary
08/29/2024, 8:45 PMhaleemur_ali
09/03/2024, 2:36 PMIan OLeary
09/03/2024, 2:41 PMhaleemur_ali
09/03/2024, 2:49 PMTo be honest though, I'm not sure how to create an error case.Happy to walk you through this. Essentially, the bug report should mention the following: 1. source system & version 2. sql script with a create table statement & an insert statement (see below) 3. tap version 4. minimal meltano.yml config (be careful not to leak any credentials or sensitive info there) 5. sample command that results in error e.g.
meltano run tap-mssql target-jsonl
6. error output (just the traceback should be fine, again please redact anything sensitive)
sample sql script:
create table test_table (id integer, test_column <MY_TEST_TEXT_TYPE_&_ENCODING_CAUSING_ERROR);
insert into test_table (1, 'text value that will error out'), (2, 'text value that is handled properly');
Ian OLeary
09/03/2024, 4:40 PMhaleemur_ali
09/03/2024, 4:43 PM