Apache Druid

Granularity Spec from the ingestion task seems to be ignored

When the new day rolled over the ingestion task switched to a DAY granularity.

Please help us congratulate the April #ApacheDruid Community Member of the Month! Jonathon Robinson, Sr. Software Engineer at TripStack, is not only active in this channel but often proactively assists his peers. Thanks for your contributions, <@U03ASFD86P7>!

```"indexSpec": {
        "bitmap": {
          "type": "concise"
        },
        "dimensionCompression": "lz4",
        "metricCompression": "lz4",
        "longEncoding": "longs",
        "segmentLoader": null
      },```
From the ingestion spec, `longEncoding` is set to `longs` so it’s 8 bytes for each value <https://github.com/apache/druid/blob/master/processing/src/main/java/org/apache/druid/segment/data/CompressionFactory.java#L179-L188>

longEncoding in compaction task payload is also `longs` … I cannot believe lz4 is able to compress so many 8 byte longs with such high compession ratio

On the `Configure schema` step enable rollup:

Thanks <@U030W50CNAC>
Whats the meaning of this then
Is it wrt realtime ingestion?

Eg 2: Per dataSource total size -

```❯ curl '<http://localhost:8888/druid/v2/sql>' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: en-GB,en-US;q=0.9,en;q=0.8' \
  -H 'Connection: keep-alive' \
  -H 'Content-Type: application/json' \
  -H 'Origin: <http://localhost:8888>' \
  -H 'Referer: <http://localhost:8888/unified-console.html>' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'Sec-GPC: 1' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.41 Safari/537.36' \
  --data-raw '{"query":"SELECT\ndatasource,\nSUM(\"size\") FILTER (WHERE is_published = 1 AND is_overshadowed = 0) AS total_data_size \nFROM sys.segments\nGROUP BY 1\nORDER BY 1"}' \
  --compressed |json_pp -json_opt pretty,canonical```

when I want to figure out what a native query would look like, I tend to write the SQL query first and then use the `EXPLAIN SQL query` button in the web-console. That will usually show you the native query that is run.