can you tell me why ?
# general
a
can you tell me why ?
v
Could possibly be due to task slots not available
a
so I can manually change it by doing into micro quickstart config files right ?
v
Is there some other druid task -- e.g. supervisor -- already running?
a
Yes I guess
I mean I was trying to join two data sources and one was alreayd there like from kafka there was alreayd a stream of data which was there
v
update
druid.worker.capacity
in
conf/druid/single-server/micro-quickstart/middleManager/runtime.properties
a
got it , will do the same and let you know
can I do faster updates in druid ?
like if my table contains lots of updates is druid suitable for it
v
Druid segments are immutable and are designed that way since events follow a similar pattern. One way to "update" data is to overwrite the segment(s) for the time interval corresponding to the older data. Another way is to use lookup tables, where you just store the key in the datasource, and use the lookup table -- which is updatable -- to fetch the latest value.