This is the sql labs interface showing the schema. it shows the __time as timestamp. but the charts that are timeseries don't work. I guess there's a bug, i'll look into it. Perhaps in pydruid? [image: image.png]
On Wed, 6 Feb 2019 at 20:41, Don Bowman <d...@agilicus.com> wrote: > its from master. > > > > On Wed, 6 Feb 2019 at 20:26, Maxime Beauchemin <maximebeauche...@gmail.com> > wrote: > >> Which version of Superset are you using? >> >> On Tue, Feb 5, 2019 at 7:38 PM Don Bowman <d...@agilicus.com> wrote: >> >> > I'm using druid 0.13 w/ superset (master). >> > If i add the druid cluster using its 'native' and then also add it as >> 'sql' >> > i can experiment w/ the variance in the interface. >> > >> > If i use a 'lbig number with trendline' chart, in the 'native' >> interface, >> > it works. >> > But in the sql interface it does not discover there is a timestamp >> column >> > (__time) so it doesn't work. >> > >> > I don't think(?) that i'm supposed to add time as a 'dimension' in druid >> > (its implicit). >> > >> > in the sql labs interface it works, e.g. I do: >> > select * from "l3-agent" order by __time limit 5; >> > >> > and this returns my columns including a __time one. >> > >> > But in the chart for 'big number with trendline' there is 'no results >> > found' for time column. >> > (t says Datetime column not provided as part table configuration and is >> > required by this type of chart) >> > >> > Am I using this incorrectly? Or its a bug? >> > >> >
