Hi, compaction shouldn't change the query result in this case.
Are you using stream ingestion method such as Kafka or Kinesis by any
chance? If so, could it be that new data has inserted into the same
interval after compaction?
Jihoon
On Wed, Jul 10, 2019 at 7:44 PM scoffi Michaeal <weitian...@gmail.com>
wrote:
> [druid-user] Why the compact feature meet a bug in new version 0.15.0
>
> 收件箱
> x
> scoffi Michaeal
> 上午10:38 (3分钟前)
> 发送至 Druid 退订
> {
> "type" : "compact",
> "dataSource" : "vehicleParking",
> "interval" : "2019-07-09T00:00:00.000Z/2019-07-10T00:00:00.000Z"
> }
>
>
> I have post the request of compact. i want to merge the segments during
> 2019-07-09. But I have meet a problem.
> I have already issued a query request and wrote down the sum of the
> parkingDuration before compacting.The number is 62881583913. The query spec
> is as follows.
> {
> "queryType": "timeseries",
> "dataSource": "vehicleParking",
> "granularity":"all",
> "aggregations": [
> {"type": "longSum","name": "parkingDuration","fieldName":
> "parkingDuration"}
> ],
> "intervals": [
> "2019-07-09T00:00:00.000Z/2019-07-10T00:00:00.000Z"
> ]
> }
>
>
>
> After compacting the segment,the number was instead of 7971084738 which is
> smaller than the previous. I don't know if it is exists a bug in the latest
> version. Anyone who can help me?
>
