This message was deleted.
# general
s
This message was deleted.
g
where are you reading your data from, what format is it in, & are you using batch or stream ingest?
v
Can you post a screenshot of where you are setting the unreadable data?
m
The ingestion is of type index parallel and here's copy paste of the ioConfig. It can "read" the file, but its definitely not in a human-readable format. (The file itself is fine for sure). I also tried changing the suffix of the file to just json and hoping that druid would recognize the compression. Same thing happens with zst compressed orc file (tried suffixing the file with zst and orc). "type": "index_parallel", "inputSource": { "type": "s3", "objects": [ { "bucket": "bucket", "path": "path/to/file.json.snappy" } ] }, "inputFormat": { "type": "json", "compression": "snappy" }
g
for batch ingest, Druid uses the suffix of the file to determine how to decompress
for snappy framing format (https://github.com/google/snappy/blob/main/framing_format.txt) Druid expects
.sz
so try naming it
<http://file.json.sz|file.json.sz>
note that there are multiple snappy compression formats out there. Druid supports just this one ☝️ so if it doesn't work for you, it's possible you are using one of the other formats. The most common are unframed (raw) compression, and the snappy frame format defined by Hadoop, neither of which Druid supports reading directly
m
Thanks for the info. I'll try tomorrow and hopefully get it to work.
For file.orc.zst I get Error: Failed to sample data: java.io.IOException: Decompression error: Unknown frame descriptor And for file.json.sz I get Error: Failed to sample data: java.io.IOException: Not a framed Snappy stream So I guess the snappy compression is one of the not supported group. However, with the zstd I'd like the guess the same, but this error is different. Any ideas?
The file is for sure zst compressed, but there are maybe also some subsets of zst that druid supports?
Same compression is used for CSV and we can successfully read those. I've checked and I did include orc-extension for Druid
g
hmm i'm not super familiar with zst so i am not sure if there are multiple formats
i wonder if it's a zst problem or orc problem
https://github.com/luben/zstd-jni/issues/103 seems to indicate it's a zst problem
https://github.com/luben/zstd-jni/ is what we're using btw