Title
#users-public
Newskooler

Newskooler

11/03/2022, 11:37 AM
Hi, I get the following error: Could not process line data. Writer is in error. Could not parse measurement. May be mangled due to partial parsing. Do you know how can I debug this and what may be the cause of this?
Jaromir Hamala

Jaromir Hamala

11/03/2022, 12:00 PM
line (may be mangled due to partial parsing):
there should be some ILP text data right after this sentence. isnt there anything at all?
Newskooler

Newskooler

11/03/2022, 12:00 PM
Yes there is
12:00 PM
But the ILP looks fine
Jaromir Hamala

Jaromir Hamala

11/03/2022, 12:01 PM
can you share it? do you use an official ILP client or are you forming ILP messages yourself?
Newskooler

Newskooler

11/03/2022, 12:02 PM
I don’t use the official and for it myself. I can’t copy /paste otherwise I would have shared the full message. I’ll try
Jaromir Hamala

Jaromir Hamala

11/03/2022, 12:02 PM
it’s usually caused by missing escaping.
Newskooler

Newskooler

11/03/2022, 12:02 PM
What is that?
Jaromir Hamala

Jaromir Hamala

11/03/2022, 12:09 PM
the simplest way to form an ILP message is to concatenate strings. but this breaks e.g. when data you are sending containts a character which has a meaning. think of a double-quotes or a comma. they need to be handled specially. see e.g. the go client: https://github.com/questdb/go-questdb-client/blob/fa4d7bd7b59ecc935e0e6867dc7c46f5c7e3f9c8/sender.go#L625-L657
12:13 PM
that’s one big advantage of the official clients: you do not have to deal with this. the client will escape special chars for you.
12:13 PM
obviously, we still do not have any evidence that lack of escaping is the issue. that should be confirmed first.
Newskooler

Newskooler

11/03/2022, 12:14 PM
Got it! I will switch to the official asap😃 thank you!
Jaromir Hamala

Jaromir Hamala

11/03/2022, 12:24 PM
you are very welcome