id
stringlengths
36
36
question_id
int64
36
27.5M
chunk_index
int32
0
29
embedding_text
stringlengths
37
16.8k
dense_tokens
int32
11
1.02k
sparse_tokens
int32
10
1.02k
languages
listlengths
1
5
tags
listlengths
1
5
payload_json
stringlengths
405
563
dense
list
sparse_indices
listlengths
8
447
sparse_values
listlengths
8
447
72e023a7-51c6-59b7-9789-8c99383281b3
79,970,521
0
Title: Why does CASE with a DOUBLE branch and ELSE NULL fail with unknown vs DOUBLE? I'm cleaning string readings in Apache IoTDB 2.0.8 table model. When txt is not bad, I cast it to DOUBLE; otherwise I return NULL. ELSE null fails with a result-type mismatch, but ELSE CAST(null AS DOUBLE) works for the same logic. ...
480
521
[ "sql" ]
[ "sql", "time-series", "apache-iotdb" ]
{"accepted_answer_id":null,"answer_count":1,"chunk_count":1,"chunk_index":0,"closed_date":null,"creation_date":"2026-06-30T01:14:11.900000+00:00","has_accepted_answer":false,"is_closed":false,"languages":["sql"],"last_activity_date":"2026-06-30T10:07:39.097000+00:00","last_edit_date":"2026-06-30T10:07:39.097000+00:00",...
[ 0.0298614501953125, 0.00782012939453125, -0.0115814208984375, -0.006717681884765625, 0.03533935546875, -0.006000518798828125, -0.012298583984375, 0.01910400390625, 0.0162353515625, -0.0160064697265625, -0.035125732421875, 0.007373809814453125, -0.01218414306640625, -0.00722503662109375, ...
[ 18, 19, 47, 51, 206, 262, 310, 313, 384, 418, 532, 678, 787, 818, 831, 839, 959, 1021, 1062, 1239, 1328, 1430, 1733, 2053, 3299, 4527, 5035, 5701, 6032, 6197, 6483, 6494, 6624, 6746, 6755, 8110, 8557, 8647, 9795, 10644, 12283, 13821, ...
[ 0.00341796875, 0.06591796875, 0.05126953125, 0.06396484375, 0.0810546875, 0.076171875, 0.0625, 0.140625, 0.0869140625, 0.0169677734375, 0.0167236328125, 0.0693359375, 0.0184326171875, 0.006103515625, 0.03076171875, 0.053955078125, 0.055908203125, 0.1689453125, 0.1044921875, 0.0...
1b674d0a-5112-59ae-9d9a-7756f8e34c2d
79,970,522
0
Title: Why doesn't LIMIT return N rows per device after ALIGN BY DEVICE? I wanted the latest two load_amp rows for each device in Apache IoTDB 2.0.8 tree model, so I queried wildcard devices with ALIGN BY DEVICE and added ORDER BY TIME DESC LIMIT 2. The result contains only the latest two rows globally, not two rows p...
567
628
[ "sql" ]
[ "sql", "time-series", "apache-iotdb" ]
{"accepted_answer_id":null,"answer_count":1,"chunk_count":1,"chunk_index":0,"closed_date":null,"creation_date":"2026-06-30T01:25:42.820000+00:00","has_accepted_answer":false,"is_closed":false,"languages":["sql"],"last_activity_date":"2026-07-01T07:00:53.450000+00:00","last_edit_date":"2026-07-01T07:00:53.450000+00:00",...
[ 0.01480865478515625, -0.002780914306640625, -0.01261138916015625, -0.0184326171875, 0.005680084228515625, 0.023193359375, 0.00797271728515625, 0.004489898681640625, 0.04022216796875, -0.0273590087890625, -0.026885986328125, 0.0170135498046875, 0.00029921531677246094, 0.00734710693359375, ...
[ 7, 13, 18, 41, 116, 117, 177, 201, 224, 309, 310, 418, 441, 541, 571, 590, 787, 1328, 1430, 1733, 1746, 2663, 3299, 3871, 4068, 4734, 5423, 6032, 6626, 6746, 7103, 7964, 8557, 9688, 9795, 9804, 10484, 12638, 12989, 13538, 13821, 14105...
[ 0.0174560546875, 0.134765625, 0.087890625, 0.0625, 0.1201171875, 0.08740234375, 0.0126953125, 0.021484375, 0.0546875, 0.01220703125, 0.010498046875, 0.024169921875, 0.00732421875, 0.12109375, 0.04248046875, 0.0244140625, 0.0966796875, 0.0184326171875, 0.083984375, 0.1025390625,...