String data points are read wrong.
See original GitHub issueQuerying string data points returns ByteBuffer#toString
instead of converting the bytes to a UTF8 string. The write operation is done with the DataOutput#writeUTF
so the read should be done with DataInput#readUTF
these methods generate bytes in a custom format. So using the String constructor would not work. I think fixing the read instead of the write makes more sense because of backwards compatability?
The read operation is done wrongly here. And you can see the write operation here.
Example:
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
java - Wrong numbers or errors when reading rows of ...
I'm trying to read a data file and take the 3 rows of numbers and store them into an array. I'm so confused...
Read more >How to Fix Data Reading Errors in R - Dummies.com
Probably the most common mistakes in R are made while reading in data from text files using read.table() or read.csv() .
Read more >How to Fix R Error: Unexpected String Constant - Statology
This tutorial explains how to fix the "unexpected string constant" error in R, including several examples.
Read more >Data Types and Formats – Data Analysis and Visualization in ...
If we have a column that contains both integers and floating point numbers, ... Text data type is known as Strings in Python,...
Read more >Troubleshooting Data Types - Visual Basic - Microsoft Learn
When you work with floating-point numbers (Single Data Type and Double Data Type), remember that they are stored as binary fractions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Now I got it.
Schema was wrong and didn’t match the thrift schema. I just fixed it and checked it into develop.