Hey friends, we are starting to issue queries in o...
# troubleshooting
l
Hey friends, we are starting to issue queries in our production cluster and we are seeing the following
Failed to find time boundary info for hybrid table
anyone know if this is bad? have more info about it?
m
Yes, this is not good.
A hybrid table internally maintains time boundary and uses it to route a query to offline table for data older than time boundary, and realtime table for data newer than time boundary.
Is your table hybrid, and does it have valid ideal-state/external-view for the OFFLINE and REALTIME counterparts?
If your OFFLINE table is empty, then the error won’t cause a functional issue. But the setup won’t make sense in that case.
l
The OFFLINE table is empty right now because the task that moves segments to offline hasn't kicked yet
m
Ah ok, you can skip the error then
l
Does it mean that once the OFFLINE table starts getting data we shouldn't see the warning anymore yes?
m
Yes