This message was deleted.
# generals
Slackbot
02/13/2023, 4:44 PMThis message was deleted.
s
Sergio Ferragut
02/13/2023, 6:47 PMCan you paste your resulting ingestion spec?
b
Ben Krug
02/15/2023, 9:23 PMYou mean it shows as INT in the console or somewhere? If so, it's probably because the schema is being infested from older existing segments. If so, you can reindex (in the console) and change to double. If they're no old segments left, you might need to restart coordinators (I think), so they can pick up the new schema.
👀 1
❤️ 1
c
Caner Kürtür
02/21/2023, 2:43 PMHey Ben thank you so much for your reply and really sorry for my late reply , a lot was going on recently 😕
Caner Kürtür
02/21/2023, 2:49 PMyes, it was showing in the console in the UI. what do you exactly mean by reindexing actually? so I just submitted another supervisor which is reading from the same kafka topic (the one I added more columns) and referring to same data source in Druid. In this case, after I submit it, what will happen to previous segments which have no new columns? Is Druid updating the data in previous segments with the new columns added after I submit it? or will I have 2 segment versions in that data source and thats why I was not able to see newly added column's type as double because the console was showing me previous segment's column type?
Caner Kürtür
02/21/2023, 2:51 PMI would like to run my changes in Production soon, and dont know what to do with segments which we already have currently. I dont want to delete data and re-ingest again as well because it is production. Thats why I wonder how in best way I can deploy my changes again to Prod.
Caner Kürtür
02/21/2023, 2:51 PMIf I just re-ingest , those v1 old segments gonna remain there in data source? how to get rid of those?
Caner Kürtür
02/21/2023, 2:54 PMIt was showing me finally "double" btw, after I drop and kill the segments from the data source and re-submit a new ingestion. That is what I would not like to apply for Prod tbh.
s
Sergio Ferragut
02/21/2023, 4:31 PMThe old segments to not NEED to be reingested; new columns will have a null value in the prior timeframe if you do not reingest them. But also, as Ben mentioned, there will be the data type side effect if you do not reingest while the older segments are still present.
g
Gian Merlino
02/22/2023, 12:55 PM@Caner Kürtür the way it works with mixed types is that the latest (highest-timestamped) data for any given column is what determines what we consider the type to be
So if you have some doubles from Jan 1 and some longs from Jan 2 then it will be long (BIGINT). If you have longs from Jan 1 and doubles from Jan 2 it will be DOUBLE.
Gian Merlino
02/22/2023, 12:55 PMthe important timestamp is the one in the data itself (
__timeGian Merlino
02/22/2023, 12:55 PMIf you see something different from this, let us know so we can help you figure out what is going on